MCP server

This reference is also an MCP server. Install it once and your coding agent can look an endpoint up while it writes the integration, instead of being handed the whole page and asked to remember it.

Cursor

One click

Add to Cursor

VS Code

One click

Add to VS Code

Claude Code

No install link — run this

terminal

claude mcp add --transport http store-api-docs https://rollroyce.store/api/mcp

Codex CLI

No install link — run this

terminal

codex mcp add store-api-docs --url https://rollroyce.store/api/mcp

Any other client

It speaks Streamable HTTP, so the URL goes straight into an MCP config file:

mcp config

{
  "mcpServers": {
    "store-api-docs": {
      "type": "http",
      "url": "https://rollroyce.store/api/mcp"
    }
  }
}

For a client that only speaks stdio, bridge it with npx -y mcp-remote https://rollroyce.store/api/mcp.

What the agent gets

Five read-only tools:

Tool	Answers
`list_guides`	The sections that explain how the API works as a whole.
`get_guide`	One of them in full — authentication, getting a key, abilities, rate limits, errors.
`list_endpoints`	Every endpoint, with method, path, ability and a one-line summary.
`get_endpoint`	One endpoint in full: parameters, a runnable example, response shapes, error codes.
`search_api_docs`	Keyword search across endpoints, abilities and error codes.

An agent that only ever reads endpoint pages writes a client that authenticates with the wrong header and retries a 403 forever, which is why the guide tools come first and the server's own instructions tell it to start there.

The server does not call the API. It describes it, and nothing more. That is a deliberate limit rather than an unfinished feature: the endpoint carries no authentication because everything it returns is already public on this site, and a tool that made requests would turn an unauthenticated URL into a proxy into a service that is otherwise unreachable from the internet. Making a real request needs your key — use your own client, or the playground.

Prefer plain text?

Two files carry the same reference with no protocol at all:

/docs/api/llms.txt — a short index of what exists.
/docs/api/llms-full.txt — the complete reference as Markdown, in the order the page reads.

Both are generated from the same source as the page, so neither can fall behind it.