# 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).

## 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.

## Auth Header

MCP uses API Access Token auth just like the REST API.

- MCP requires an API Access Token in `Authorization: Bearer <rho_api_access_token>`.


## 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.