Docs MCP server
Connect AI clients to the public Statsig documentation MCP endpoint.
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.
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:
{
"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:
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.
Limitations
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.
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.
Was this helpful?