RFC / v0.1Draft for public comment
The Automotive MCP Specification
A single, conformant way for dealership systems to expose their data and actions to AI agents over the Model Context Protocol — defined as stable resources to read and tools to act on, so any compliant agent works with any compliant server.
This is a draft (RFC), not a finished decree. The council exists to ratify it with its partners. Sections will firm up as the working groups and founding partners review them — expect change.
LicenseThis specification is published under Creative Commons Attribution 4.0 (CC BY 4.0) — you may share and adapt it, including commercially, with attribution.
- 1Scope, Goals & Non-GoalsWhat this specification covers — the retail dealership data and tool layer for AI agents — and the adjacent territory it deliberately leaves to others.
- 2Conformance & VersioningLevels of conformance, how versions are numbered, and the lifecycle a release moves through from draft to ratified.
- 3Core ConceptsThe building blocks every conformant server shares: resources, tools, errors, pagination, and eventing — expressed in MCP terms.
- 4Canonical DomainsThe operational domains of the dealership, each a stable resource and tool namespace that a conformant server implements.
- 5Naming ConventionsStable, predictable names for resources, tools, and fields — the mechanism that makes any conformant server interchangeable.
- 6Auth & Security ProfileHow agents authenticate, how access is scoped, and how PII is handled. Automotive data carries real compliance weight; this section is normative.
- 7Reference MaterialNon-normative examples: a conformant server manifest and a representative tool schema, to anchor the prose in concrete shapes.