> For the complete documentation index, see [llms.txt](https://docs-core.allbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-core.allbridge.io/ai/allbridge-mcp/http-and-auth.md).

# HTTP and Auth

Allbridge MCP supports two connection shapes.

### `stdio`

Use `stdio` when the client can launch a local process.

This is the default for:

* Claude Desktop
* Claude Code
* Cursor
* other local MCP clients

### `streamable-http`

Use `streamable-http` when the client needs a URL.

This is the right choice for:

* hosted agents
* remote connectors
* deployments behind a trusted proxy or tunnel

### Authentication

Hosted deployments can expose MCP discovery and auth endpoints so remote clients can authenticate.

Point the client at the server URL for the deployment you actually want to use. A local process and a hosted endpoint are different connection targets.

### Security

Allbridge MCP should stay read-only for docs, route planning, and balance checks.

It should not need private keys to answer those requests.