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 being prepared for an invitation-only private pilot, but connections are not enabled yet. It has not been approved or published in the OpenAI Plugins Directory or the Claude Connector Directory.

#Availability

Status
Pre-release private pilot; connection access is not enabled yet.
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.

  • 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.
graphql_query
Runs a read through the selected dealership and each resolver's existing authorization checks.
graphql_mutation_propose
Creates a durable proposal for one GraphQL mutation and returns a Driverseat review link. It does not execute the change remotely.
agent_action_status
Checks the proposal or action state. Only a SUCCEEDED status means the confirmed change actually ran.

#How changes work

  1. 1The AI client discovers the relevant schema and prepares exactly one mutation.
  2. 2Driverseat validates authorization and saves a proposal without applying the change.
  3. 3An authorized human opens the Driverseat review link and confirms or rejects the proposal in the dashboard.
  4. 4The 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 cross the Driverseat confirmation boundary, even if the AI client describes the request as complete.

#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.

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 stops future connector sessions from that client. Changing a Driverseat role separately changes what the user can access across Driverseat, including through the connector.