Project connection
Use when a trusted dealership project needs a shared server definition. Keep the token in each developer’s environment, never in the project file.
Claude Code automotive MCP
Connect Claude Code to a remote, read-only AutoFire toolset with an authorization header and a credential that expires automatically.
export AUTOFIRE_MCP_TOKEN="your-key-from-autofire"
claude mcp add --transport http autofire \
https://mcp.goautofire.com/mcp \
--header "Authorization: Bearer ${AUTOFIRE_MCP_TOKEN}"Use when a trusted dealership project needs a shared server definition. Keep the token in each developer’s environment, never in the project file.
Use for personal workstation access. Create a separately named key so it can be rotated without disrupting another client.
“List available SUVs under $25,000 from AutoFire. Do not include VINs or customer data.”
“Summarize lead status counts using the masked lead workflow records.”
“Show the next seven days of test-drive workflow records without customer identity.”
“Read the latest dealership insight report and identify inventory follow-up questions.”
Use claude mcp list to confirm the server definition. For authorization failures, verify the shell running Claude Code inherited the environment variable, then check the key’s expiration and revocation status in AutoFire.
Start with a 30-day, read-only key and only the scopes your client needs.