MCP Server

AutoRev exposes Megan (AutoRev's AI employee) as a Model Context Protocol (MCP) server at /api/mcp. Add this URL plus your API key as a Claude.ai Custom Connector to message Megan from the Claude mobile or desktop app.

Protocol

Property	Value
Endpoint	POST https://app.autorev.ai/api/mcp
Transport	MCP 2025-03-26 Streamable HTTP
Envelope	JSON-RPC 2.0
Supported methods	initialize, tools/list, tools/call, ping
Auth	Bearer token via the Authorization header

Example: list tools

curl -X POST https://app.autorev.ai/api/mcp \
  -H "Authorization: Bearer ar_live_..." \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The tools returned are filtered by your key's scopes; each tool declares a required scope, and keys lacking the scope get a 403 with a clear error. The same tools are also available as plain function-calling schemas via the tool manifest.

Unlike the direct REST endpoints, cold outbound via the MCP tool layer rejects numbers with no prior relationship to the tenant. See TCPA rules for agents.

Claude.ai Custom Connector setup

1. Mint an API key (see below for which kind).
2. In Claude.ai, add a Custom Connector pointing at https://app.autorev.ai/api/mcp.
3. Provide your API key as the Bearer token.
4. Claude discovers the available tools automatically via tools/list; no tool wiring is needed.

Megan connector keys

Dashboard users mint dedicated Megan MCP keys from the Settings > AI Employee page in the AutoRev dashboard. These keys are scoped to ["read"] only and are distinct from the general AutoRev API keys minted at Settings > Integrations.

Dashboard-only endpoints

The two /api/megan/keys endpoints below use dashboard session authentication (browser cookie), not Bearer API keys. They are documented for completeness; call them from the AutoRev dashboard, not from your integration.

GET /api/megan/keys returns metadata for the user's latest active Megan MCP key, or {"exists": false} if none exists:

{
  "exists": true,
  "keyId": "uuid",
  "prefix": "ar_live_abcd",
  "createdAt": "2026-04-20T10:30:00Z"
}

POST /api/megan/keys mints a new Megan MCP key. The full key is returned once; store it securely, it cannot be retrieved later:

{
  "key": "ar_live_abcd1234...",
  "keyId": "uuid",
  "prefix": "ar_live_abcd",
  "createdAt": "2026-04-20T10:30:00Z"
}