---
title: Docs MCP server
description: Connect AI clients to the public Statsig documentation MCP endpoint.
product: general
token_estimate: 713
---
# Docs MCP server

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Use the Statsig Docs MCP server to let supported AI clients read public Statsig documentation directly from `/api/mcp`. The server is read-only and serves English documentation from this site, so your AI tools answer Statsig questions with current, accurate docs content.

This server is separate from the authenticated [Statsig MCP server](https://docs.statsig.com/integrations/mcp/overview), which connects to your project data. The Docs MCP server reads documentation only and needs no API key.

## Supported clients

Use a client that supports remote MCP servers over Streamable HTTP and accepts a direct URL. Claude Code, Cursor, and Codex CLI all work.

Older MCP clients that only support the deprecated HTTP+SSE transport can't connect to this endpoint.

## Add the server

Many MCP clients read a JSON config:

```json
{
  "mcpServers": {
    "statsig-docs": {
      "url": "/api/mcp",
      "transport": "streamable-http"
    }
  }
}
```

If your client supports command-line setup, add the same URL as a remote HTTP MCP server:

```bash
claude mcp add --transport http statsig-docs /api/mcp
```

## Available tools

The server exposes three read-only tools:

- `get_page`: Retrieve the full markdown content of a Statsig documentation page.
- `list_pages`: List all available documentation pages with their titles and slugs.
- `search_docs`: Search documentation pages by keyword.

Each tool accepts an optional `rationale` string (max 500 characters) so the model can explain why it called the tool. That value may appear in server usage telemetry when enabled.

## Optional correlation headers

MCP clients may send these HTTP headers on each request. The server copies them into usage telemetry when present:

- `x-agent-trace-id`
- `x-agent-session-id`
- `x-mcp-client` (for example, `cursor` or `claude-code`)

## Limitations

> **Note:**
>
> The Docs MCP server is public, read-only, and serves English documentation only. It doesn't require authentication, doesn't expose MCP prompts or resources, and supports Streamable HTTP only. The server rate-limits requests per client.

For authenticated access to your project data, like experiments, gates, and metrics, use the [Statsig MCP server](https://docs.statsig.com/integrations/mcp/overview) instead.

## Troubleshooting

- If your client reports an unsupported transport, update it to a version that supports remote MCP servers over Streamable HTTP.
- If setup fails, confirm that you used the exact endpoint URL: `/api/mcp`.
- If you need project data or write access, this server isn't the right endpoint. Use the authenticated [Statsig MCP server](https://docs.statsig.com/integrations/mcp/overview).