# MCP

The service exposes MCP over Streamable HTTP. The MCP endpoint is separate from the REST API routes:

| REST endpoint | MCP endpoint |
|  --- | --- |
| `/api/v1` | `/mcp/v1` |


MCP uses the same API contract, authentication model, scopes, and error behavior as the REST API. The `/mcp/v1` tool schemas follow the same stability policy as the REST contracts - see [Versioning and compatibility](/docs/v1/versioning).

## Protocol Versions

The MCP endpoint advertises and supports protocol versions `2026-07-28`, `2025-11-25`, and `2025-06-18`. Clients can negotiate the current sessionless protocol through `server/discover`. Every non-`initialize` request must include the selected version in the `MCP-Protocol-Version` header. Versions older than `2025-06-18` and JSON-RPC batches are rejected.

## Claude Code

Add the Rho API MCP server:

```sh
claude mcp add --scope project --transport http rho-api \
  https://rhoapi.rho.co/mcp/v1 \
  --header "Authorization: Bearer <rho_api_access_token>"
```

Use `/mcp` inside Claude Code to confirm the server is connected.

## Authentication

Rho supports two MCP authentication paths:

- **Direct connections** require an API Access Token in `Authorization: Bearer <rho_api_access_token>`.
- **Linked apps** use the OAuth connection provided by the MCP client, without requiring users to configure an API Access Token manually. Linked-app availability depends on the client.


## Tools and Prompts

The MCP server exposes Rho API tools, prompts, and resources. You can use your MCP client like Claude Code or
[MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector) to inspect all available capabilities.