Dealership profile
Public business profile, verified website, hours, and location.
AutoFire™ automotive MCP
Give approved AI clients read-only access to one dealership’s inventory and workflows. AutoFire never gives the client a database password or service-role key.
https://mcp.goautofire.com/mcp
# Sign in with your AutoFire account when the browser opens,
# pick the dealership and permissions, and select Allow.New · Claude and ChatGPT directories
Find AutoFire in the Claude connector directory or as an official ChatGPT plugin, sign in, and ask about your lot. Both call the same read-only tools listed below, scoped to the one dealership you pick.
Available tools
Search inventory, review lead statuses, check test-drive records, and read recent dealership reports from an MCP client. Each key exposes only the tools and data permissions selected when the key is created or the app is connected.
Want to see the day-to-day dealership workflows first? Read how dealership owners use AutoFire MCP.
Public business profile, verified website, hours, and location.
Search up to 50 dealership-owned vehicles per request without exposing VINs.
Review lead statuses and linked vehicles without contact details by default.
Return a single lead’s contact data only with the explicit leads:pii scope.
Read scheduling workflow and vehicle context without customer identity or notes.
Retrieve recent dealership reports without customer-level records.
More MCP features are rolling out soon. Have something specific in mind? Contact us.
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.
Access controls
Apps sign in with OAuth 2.1 and PKCE, and you approve exactly what they can read on AutoFire’s consent screen. Scripts and clients that only take a token use expiring, scoped keys. Every dealership also has a monthly tool-call allowance set by its plan.
Use the same HTTPS endpoint with a separate sign-in or credential per client. Each guide includes client-specific setup and verification steps.
Now in the Claude connector directory. Connect on the web, desktop, or mobile and sign in.
Install the official AutoFire plugin in ChatGPT, or sign in from the Codex CLI.
Add a custom connector at grok.com/connectors, or install the Grok Build plugin.
Sign in from the terminal, or use an authorization header from your environment.
Bearer-key configuration for Codex CLI, the IDE extension, and the desktop app.
Compare connection methods for local, hosted, and generic MCP clients.
No. Every key is permanently bound to one dealership. Create a separate key for each dealership connection.
Not for Claude, ChatGPT, Codex, or Grok: add the server URL and sign in with your AutoFire account. Keys remain available for scripts and clients that only take a token.
No. The dashboard shows it once, then stores only an HMAC-SHA-256 digest.
Not in the initial release. Every published tool is read-only and annotated as non-destructive.
500 a month on Free, 2,000 a month on Starter, 10,000 a month on Pro, 25,000 a month on Growth, contract-defined on Ultra, shared by all of a dealership’s keys and connected apps.
You choose 30, 60, or 90 days. Keys cannot be extended and can be revoked immediately.
Start with a 30-day, read-only key and only the scopes your client needs.