Dealership profile
Public business profile, verified website, hours, and location.
Purpose-built access
What AutoFire MCP lets your dealership do
Use dealership data inside coding agents and other MCP clients for inventory lookups, operational summaries, and carefully scoped lead follow-up context. The client sees only tools allowed by its credential.
Inventory search
Search up to 50 dealership-owned vehicles per request without exposing VINs.
Lead workflow
Review lead statuses and linked vehicles without contact details by default.
Scoped lead details
Return a single lead’s contact data only with the explicit leads:pii scope.
Test drives
Read scheduling workflow and vehicle context without customer identity or notes.
Aggregate insights
Retrieve recent dealership reports without customer-level records.
More MCP features are rolling out soon. Have something specific in mind? Contact us.
Connect dealership inventory and leads to AI tools
AutoFire exposes focused operations instead of a general SQL or table API. Queries are parameterized, paginated, size-limited, and filtered to the dealership encoded in the credential.
- 1Choose the dealership in the AutoFire dashboard.
- 2Create a named 30-, 60-, or 90-day key with least-privilege scopes.
- 3Store the key in the client’s secret or environment-variable manager.
- 4Connect to the Streamable HTTP endpoint and verify the advertised tools.
Security first
Secure access with expiring, scoped keys
Personal access keys are available for headless and local clients. The OAuth 2.1 resource-server path is implemented behind a feature gate and will be advertised only after AutoFire’s production Supabase OAuth and asymmetric signing rollout is verified.
✓ One dealership per credential
✓ Raw key displayed once
✓ Immediate server-side revocation
✓ Per-source, key, dealer, and tool limits
✓ Security activity logged without copying customer details
✓ 128 KiB request ceiling and strict schemas
✓ No arbitrary URLs or database queries
✓ Read-only launch toolset
Works with Codex, Claude Code, and cloud-compatible clients
Use the same HTTPS endpoint with a separate credential per client. Each guide includes client-specific configuration and verification steps.
Automotive MCP FAQ
Can one key access several dealerships?
No. Every key is permanently bound to one dealership. Create a separate key for each dealership connection.
Does AutoFire store the raw MCP key?
No. The dashboard shows it once, then stores only an HMAC-SHA-256 digest.
Can an AI client change inventory or lead records?
Not in the initial release. Every published tool is read-only and annotated as non-destructive.
How long can a key remain active?
Owners and admins choose 30, 60, or 90 days. Keys cannot be extended and can be revoked immediately.