AI connectorOverview

Driverseat connector

Use an AI client with the dealership accounts you already have permission to access in Driverseat. One shared, authenticated MCP connection is designed to work with ChatGPT, Codex, and Claude.

The connector is available as a pre-release direct connection for active linked Driverseat users. It has not been approved or published in the OpenAI Plugins Directory or the Claude Connector Directory.

#Availability

Status
Pre-release direct connection enabled; not yet approved or publicly listed in either directory.
MCP endpoint
https://mcp.driverseat.io/mcp
AI clients
ChatGPT and Codex through an OpenAI plugin, and Claude through a connector. All clients use the same Driverseat MCP service.
Directories
Not yet approved or publicly listed by OpenAI or Anthropic. A private pilot connection is not a directory endorsement.

#Identity and access

You sign in to Driverseat during connection. Connector activity is performed by a Driverseat agent identity on behalf of your verified user. Agent runs and proposed actions record both identities, while existing records and activity feeds may continue to show you in fields such as createdBy.

  • Any active human linked from the verified sign-in identity may connect; there is no connector-specific email allowlist.
  • Your current dealership and dealership-group roles determine which accounts and operations are available.
  • The connector does not create a separate permission-grant system or elevate your access.
  • Remote connector requests never receive Driverseat global or operator privileges, including when the signed-in user is a Driverseat employee.
  • Driverseat checks your role again when a tool runs, so a role change applies to future requests.
  • The connected AI client never receives your Driverseat password.
The broad connector scope allows the AI client to ask Driverseat for available tools. It may discover operations you cannot run; schema visibility is not permission. Every GraphQL resolver retains its normal public or selected-dealership authorization checks.

#Available tools

dealership_accounts
Lists the dealership accounts the signed-in user can access, including access inherited through a dealership group.
graphql_schema
Discovers the broad GraphQL schema, including operations the selected dealership or user may not be authorized to run. Each call writes internal audit metadata but does not change dealership data.
graphql_query
Runs a read through the selected dealership and each resolver's existing authorization checks. Each call writes internal audit metadata, and a resolver may read from an external service.
graphql_mutation_propose
Creates a durable proposal for one GraphQL mutation and returns its exact action details plus a Driverseat review link. It does not execute the change. Exact retries reuse the action, while each attempt still writes audit metadata.
agent_action_decide
Confirms or rejects an exact proposal after the signed-in human clearly authorizes it in chat. A direct request or a later response such as "yeah, do that" is sufficient; confirmation can change public dealership data or contact external services, while rejection cannot. Repeating the exact confirmation cannot execute it twice.
agent_action_status
Checks the proposal or action state. Only a SUCCEEDED status means the confirmed change actually ran.

#How changes work

  1. 1You give the AI client a clear instruction. A direct request authorizes ordinary related edits within the scope you described.
  2. 2The client discovers the relevant schema and prepares exactly one mutation/action containing the whole in-scope payload, rather than asking for approval field by field.
  3. 3Driverseat validates authorization and saves a proposal without applying the change by itself.
  4. 4If the exact proposal stays within your instruction, the client immediately submits that authorization in the same turn without asking you to repeat it. If material ambiguity makes the client pause on a preview, a response such as "yeah, do that" is sufficient. It asks again only if the proposal materially expands the requested scope.
  5. 5The client submits that decision with the dealership, action ID, and payload hash. Driverseat rechecks the human's current access and executes a confirmed action at most once. The Driverseat review link remains available as a fallback.
  6. 6The client checks the action status. A proposal, approval, or queued state is not proof of completion; only SUCCEEDED is.
Reads can return data immediately. Writes always stay within the human's explicit request, but that authorization can be the original direct instruction and uses the existing signed-in connector session—there is no separate approval screen, OAuth authorization, or permission grant.

#Data and privacy

Tool requests and responses may pass through the AI client you connect. That provider handles the conversation under its own account settings, terms, and data controls. Driverseat applies existing GraphQL resolver permissions, suppresses remote operator privilege, and keeps agent runs and write proposals attributable in its audit trail.

Driverseat removes detailed stored tool arguments and results after 90 days. It retains the remaining run, tool-call, authorization, action, and result-receipt records as part of dealership activity and audit history. Exact action payloads are encrypted at rest. Disconnecting or revoking the connection blocks new access tokens and refreshes, but an access token already issued may remain usable until it expires. Historical activity is not erased.

The connector intentionally exposes the broad GraphQL surface. If an existing resolver permits it, a response can include credentials, integration configuration, or control-plane values, and that selected output is sent through the connected AI provider. Request only the data needed. This policy may also affect eligibility for public OpenAI or Anthropic directory review.

#Disconnect or revoke access

  1. 1Remove or disconnect Driverseat from the connected-app settings in ChatGPT, Codex, or Claude.
  2. 2For pilot-level account revocation, contact Driverseat support and identify the user and connected client.
  3. 3If dealership access itself should end, a dealership administrator must remove or change the user's existing Driverseat role.

Disconnecting or revoking blocks new access tokens and refreshes, but an access token already issued may remain usable until it expires. Changing a Driverseat role separately changes what the user can access across Driverseat, including through the connector.