MCP clients
Automata serves remote MCP over HTTP and supports both bearer-header and path-token authentication.
Choose an endpoint format
Prefer the bearer-header endpoint when the client supports custom headers:
Endpoint: https://automata.example.com/mcp
Authorization: Bearer <connector-token>
Use a path token only for clients that cannot attach an authorization header:
https://automata.example.com/mcp/<connector-token>
URLs are commonly logged by clients and proxies. Automata redacts path tokens from its own logs, but header authentication still reduces accidental exposure across the rest of the request path.
Claude.ai
In Claude.ai, open Settings → Connectors → Add custom connector. Enter the name and connector URL shown in the Automata connection dashboard. Use the endpoint format supported by the current connector form.
Claude Code
For a path-token endpoint:
claude mcp add --transport http automata \
https://automata.example.com/mcp/<connector-token>
Use a distinct connector name for each Automata connection, such as support-whatsapp or reporting-db.
Bearer-header clients
Configure the MCP URL as /mcp and add:
Authorization: Bearer <connector-token>
Automata does not use a browser cookie for MCP authentication. Missing, invalid, expired, or revoked connector tokens receive 401.
MCP Inspector
Launch the official inspector from the source repository:
pnpm dlx @modelcontextprotocol/inspector
Point it to http://localhost:3000/mcp/<connector-token>, or use http://localhost:3000/mcp with the bearer header. Begin with a read-only status tool before testing write access.