# AutomotiveMCP

> A profile of the Model Context Protocol for retail automotive. It defines how a dealership
> system exposes its data and actions to AI agents: stable tool names, versioned object
> schemas, and an auth profile, so any conformant agent works with any conformant server.

Version: v0.1 (RFC). This is a draft for public comment, not a ratified standard.
Base protocol: Model Context Protocol, current revision 2026-07-28 (https://modelcontextprotocol.io).
This profile targets 2026-07-28 for transport and auth mechanics: a stateless core with a
server/discover RPC, per-request protocolVersion, and the Extensions framework. This profile is
published as the MCP Extension io.automotivemcp/profile; federation and delegated
identity are being drafted as io.automotivemcp/federation and
io.automotivemcp/agent-identity. MCP is an LF Projects / Agentic AI Foundation project;
naming constraints on "MCP" follow the LF Projects trademark policy.
License: specification and schemas Apache-2.0, documentation CC BY 4.0.

## Start here if you are building a server

1. Fetch https://automotivemcp.ai/tools.json for the tool catalog: 63 tools across
   9 namespaces, each with its conformance level and the schema of
   the object it returns.
2. Fetch https://automotivemcp.ai/schemas/index.json for the 27 object schemas. Each is
   served at the $id it declares, as application/schema+json with open CORS, so a validator
   that follows the identifier resolves it.
3. Implement Level 1 (read) for one domain before anything else. Conformance is declared per
   domain, not for the whole server, so a server exposing only inventory reads is conformant.
4. Name tools domain.verb_object in lower_snake_case. Names are normative: see
   https://automotivemcp.ai/spec/naming.

## Hard rules an implementation must not get wrong

- Every resource is dealership-scoped. One dealership MUST NOT be able to read or act on
  another's data.
- Monetary amounts are a minor-unit integer plus an ISO 4217 currency, never a float.
- Per-unit prices that can be smaller than one minor unit (per message, per minute) are a unit_rate: a decimal string in major units plus currency and per, never a float.
- Timestamps are RFC 3339 with an explicit offset.
- Enumerated values come from the vocabulary defined per field. An unknown state maps to the
  defined unknown member, never a freeform string.
- Fields marked "x-pii": true in a schema carry personal data and are governed by the auth
  and security profile at https://automotivemcp.ai/spec/auth-security.
- Consumers MUST tolerate unknown enum members: adding one is a MINOR change.

## Machine-readable artifacts

- Tool catalog: https://automotivemcp.ai/tools.json
- Schema index: https://automotivemcp.ai/schemas/index.json
- Individual schema: https://automotivemcp.ai/schemas/<namespace>/<entity>.json
- Example instance: https://automotivemcp.ai/schemas/<namespace>/<entity>.example.json
- Security contact: https://automotivemcp.ai/.well-known/security.txt

## Specification sections

- §1 Scope, Goals & Non-Goals: https://automotivemcp.ai/spec/scope
- §2 Conformance & Versioning: https://automotivemcp.ai/spec/conformance
- §3 Core Concepts: https://automotivemcp.ai/spec/core-concepts
- §4 Canonical Domains: https://automotivemcp.ai/spec/domains
- §5 Naming Conventions: https://automotivemcp.ai/spec/naming
- §6 Auth & Security Profile: https://automotivemcp.ai/spec/auth-security
- §7 Reference Material: https://automotivemcp.ai/spec/reference
- §8 The Reference Flow: https://automotivemcp.ai/spec/flow
- §9 Consent Portability: https://automotivemcp.ai/spec/consent-portability
- §11 Federation (DRAFT, not yet normative): https://automotivemcp.ai/spec/federation
- §12 Delegated Identity (DRAFT, not yet normative): https://automotivemcp.ai/spec/delegated-identity

## Domains

- R01 inventory: New, used and in-transit vehicles, VIN, trim, options, media, status and price.
- R02 leads: Up records, contacts, communications, ownership and lead lifecycle state.
- R03 deals: Quotes, payments, trade valuations, incentives and desking scenarios.
- R04 service: Repair orders, appointments, technician time and service history.
- R05 parts: Catalog, availability, pricing, supersessions and ordering.
- R06 fni: Finance & insurance products, lender programs, menus and compliance artifacts.
- R07 signals: Audiences, attribution, and the engagement/sale/service event stream exposed for agent reasoning.
- R08 consent: Communication consent records, status, channel, source and method, for TCPA and privacy compliance.
- R09 core: The cross-cutting records every other domain points to: the dealer itself, its employees, outside vendors, and documents.

## Known gaps, so you do not waste time looking for them

The following are not yet specified. If your implementation needs them, you are ahead of the
standard and the working group wants to hear from you at https://automotivemcp.ai/contact.

- Federation across multiple rooftops (location identifier, namespacing, provenance,
  partial failure, token exchange) is DRAFT in §11 (https://automotivemcp.ai/spec/federation): published for
  comment, not yet normative. Do not claim conformance with it.
- The auth network layer (agent identity, delegation, step-up, revocation, audit record) is
  DRAFT in §12 (https://automotivemcp.ai/spec/delegated-identity). Section 6 remains the normative single-server profile.
- Freshness and staleness contracts for inventory.
- Machine-readable substantiation of quoted monetary figures.
- Eventing (Level 3) declares a conformance level with no mechanism defined.


## Contributing

Every spec section and schema page carries a Propose a change link that arrives prefilled with
the section and version. No contributor agreement to sign, no copyright assignment.
Report security issues via https://automotivemcp.ai/security, not a public issue.