> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ada.cx/mcp/introduction/getting-started/other-mcp-clients/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ada.cx/_mcp/server.

# Other MCP clients

Ada's MCP server is compatible with any AI assistant or tool that supports the Model Context Protocol. The [Claude](/mcp/introduction/getting-started/claude), [ChatGPT](/mcp/introduction/getting-started/chat-gpt), [Codex CLI](/mcp/introduction/getting-started/codex-cli), [Gemini CLI](/mcp/introduction/getting-started/gemini-cli), and [Google ADK](/mcp/introduction/getting-started/google-adk) walk-throughs cover the most common clients, but the same connection URLs work with other MCP-compatible tools.

## Connection endpoints

| Method  | URL                                                |
| ------- | -------------------------------------------------- |
| OAuth   | `https://<your-ada-instance-domain>/api/mcp/oauth` |
| API key | `https://<your-ada-instance-domain>/api/mcp`       |

See [Authentication](/mcp/introduction/authentication) for details.

## Clients known to work

* **Cursor** — configure through Cursor's MCP settings. Both OAuth and API key work.
* **VS Code** — configure through MCP extensions that support remote MCP servers.
* **Custom integrations** — any MCP client implementation can point at the connection URLs above.

## Microsoft Copilot

The MCP tools are also available within Microsoft Copilot. Unlike the clients above, this does not use the connection URLs directly—the Ada agent is packaged and imported into Microsoft Copilot Studio, then connected to your Ada instance. Setup is coordinated with Ada. Contact your Ada representative to get started.

## Transport

Ada's MCP server uses the **Streamable HTTP** transport at the `/api/mcp` endpoint. Requests are JSON-RPC 2.0 over HTTP POST. Responses are JSON. Server-Sent Events (SSE) streaming is not currently supported. In a client that asks for a transport type, select **Streamable HTTP**. Claude Desktop should use a [custom connector](/mcp/introduction/getting-started/claude). Clients that require a local process can use the `mcp-remote` helper via `npx`. Pin the helper version. See [Authentication](/mcp/introduction/authentication#pin-the-local-helper-version).