> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goautofire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Generic and cloud MCP clients

> Connect any compatible Streamable HTTP client to the AutoFire MCP endpoint.

## Connection values

| Setting        | Value                            |
| -------------- | -------------------------------- |
| Transport      | Streamable HTTP                  |
| URL            | `https://mcp.goautofire.com/mcp` |
| Authentication | HTTP bearer token                |
| Header         | `Authorization: Bearer <key>`    |

AutoFire also accepts the legacy stateless HTTP flow for compatibility. New integrations should use Streamable HTTP.

## Client checklist

1. Confirm the client supports a remote HTTP MCP server and custom bearer authentication.
2. Store the key in the client's encrypted secret store, not a prompt or shared config file.
3. Disable tools the workflow does not require.
4. Keep interactive approval enabled during validation.
5. Test with inventory before considering lead permissions.
6. Review where the client stores prompts, tool arguments, and tool results.

## Hosted cloud clients

A hosted client may transmit dealership data outside AutoFire's infrastructure. Confirm the provider's subprocessor list, region, retention period, model-training controls, incident response, and deletion process before connecting it.

## OAuth-only clients

AutoFire's public OAuth flow is not enabled yet. A client that requires OAuth discovery and cannot accept a bearer token cannot connect at this time. Do not work around this by exposing a key in a public URL or browser script.

## Desktop extensions

The former DXT packaging format is now commonly called an MCP Bundle (MCPB). AutoFire is a hosted server and does not require a local MCPB installation; configure the remote URL and bearer key instead.