# MCP tool surface

> How the MCP transport at `/mcp` relates to the HTTP API. Linked from
> `/llms.txt`.

## Is there a real MCP transport, or just an HTTP API?

A real MCP server is live at this origin, mounted at `/mcp` -- not a
REST API with MCP bolted on afterward. Every route in the API surface is
also exposed as a generated MCP tool, built directly from the same
OpenAPI contract the HTTP routes are generated from, so the two surfaces
cannot drift from each other. Prefer the MCP transport when calling from
an MCP-capable client; tool names and schemas match the operation IDs in
the spec at `/docs/`.

## Registry listings

raccha.ai is listed in partner MCP directories, including
[mcp.so/servers/raccha-ai](https://mcp.so/servers/raccha-ai). These are
independent indexes; the canonical endpoint and docs always live here at
`https://raccha.ai`.