# Set up Reytd with an AI assistant

> Connect Claude Code, Cursor or VS Code to Reytd's MCP server, so your AI assistant can search these docs, read the guides and look up API endpoints as it codes.

If you build your store's integration with an AI assistant, such as Claude Code, Cursor or GitHub Copilot in VS Code, connect it to Reytd's MCP server. Your assistant can then search these docs, read a guide, look up an API endpoint's fields and explain an error code while it writes your code, instead of guessing with great confidence.

## What it does

The server is at `https://reytd.com/mcp`, with four tools:

- **search-docs** finds a topic in the guides, the FAQ and the API reference.
- **read-guide** reads a whole guide, such as [Product reviews for headless and custom stores](https://reytd.com/docs/integrations/custom-store.md).
- **api-endpoint** gives one endpoint's parameters, fields, examples and errors, from the same OpenAPI document as the [API reference](https://reytd.com/docs/api.json); asked without an endpoint, it lists them all.
- **explain-error** says what an error code means and what to do about it, for a response's `errors.code` or a failed item in a batch.

It reads Reytd's public docs only. It doesn't sign in and can't see or change your store's data, so there's nothing to set up in Reytd and no token to give it.

## Add it to your assistant

### Claude Code

```bash
claude mcp add --transport http reytd https://reytd.com/mcp
```

Add `--scope project` to share it with your team in the project's `.mcp.json`. Check that it's connected with `/mcp` in Claude Code.

### Cursor

Add this to `.cursor/mcp.json` in your project, or to `~/.cursor/mcp.json` for every project:

```json
{
    "mcpServers": {
        "reytd": {
            "url": "https://reytd.com/mcp"
        }
    }
}
```

### VS Code

Add this to `.vscode/mcp.json` in your project, or to your user configuration (**MCP: Open User Configuration**) for every project:

```json
{
    "servers": {
        "reytd": {
            "type": "http",
            "url": "https://reytd.com/mcp"
        }
    }
}
```

### Other assistants

Any assistant that connects to remote MCP servers over Streamable HTTP works the same way: give it `https://reytd.com/mcp`, with no sign-in. (Older clients that only speak SSE won't connect.) An assistant without MCP can start from [llms.txt](https://reytd.com/llms.txt) instead: an index with a link to each guide as Markdown, the OpenAPI document and the Postman collection.

## Then ask it

For example:

- "Read Reytd's custom store guide and write the code that sends our orders and shipments to Reytd."
- "Which fields does Reytd's `POST /v1/fulfillments` take?"
- "Our sync gets `order_not_found` from Reytd. What should it do?"

Build and test against your store's sandbox first, with a sandbox token: see [Build it in the sandbox first](https://reytd.com/docs/integrations/custom-store.md#build-it-in-the-sandbox-first). Before you test the whole loop, turn on review requests in Reytd; they start switched off.

## Limits

Up to 120 calls a minute from one address, counting every message your assistant sends, connecting and listing the tools too. Plenty, unless your assistant has a lot of questions. This is the MCP server's own limit; the API's is in [Rate limits](https://reytd.com/docs/api.json).
