# Model Context Protocol Docs MCP server > Search and read the official Model Context Protocol specification and documentation, with a way to report doc problems. - Listing: https://mcp.tc/i/mcp-docs - Connect: use the server's own URL `https://modelcontextprotocol.io/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: none - Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge) - Vendor: Model Context Protocol - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: - Repository: ## About Connects to the published Model Context Protocol documentation site. You can search the knowledge base for guides, API references and code examples, and read full pages through a read-only virtual filesystem of the docs using commands such as head, cat and rg. The server is hosted at modelcontextprotocol.io/mcp and uses streamable HTTP. No sign-in or API key is needed. Apart from the feedback tool, which sends a report about a documentation page to the docs team, it is read-only and limited to public site content. ## What it can do - Search the MCP documentation for guides, examples and references - Read full documentation pages by path - Run keyword or regex searches over the docs with rg - Report incorrect or outdated documentation pages - Read resources with extra skill guidance ## Tools (3) - `search_model_context_protocol`: Search the MCP knowledge base for docs, code examples and guides, returning titles and links. (read-only) - `query_docs_filesystem_model_context_protocol`: Run read-only shell-like commands (head, cat, rg) on a virtual filesystem of the MCP docs. (read-only) - `submit_feedback`: Send feedback to the docs team about an incorrect, outdated or unclear documentation page. ## Example prompts - "Search the MCP docs for how streamable HTTP transport works" - "Show me the docs page on building an MCP server" - "Find what the MCP spec says about authorization" - "Report that a docs page has an outdated example" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http mcp-docs https://modelcontextprotocol.io/mcp ``` 2. Start Claude Code and type `/mcp`. **mcp-docs** should show as connected. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Model Context Protocol Docs** and paste this URL: ```url https://modelcontextprotocol.io/mcp ``` 3. Click **Add**. Its tools appear in the chat’s tools menu. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://modelcontextprotocol.io/mcp` and click **Add**. 3. Turn it on in a chat from the tools menu. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://modelcontextprotocol.io/mcp` as the server URL and choose **No authentication**. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "mcp-docs": { "url": "https://modelcontextprotocol.io/mcp" } } } ``` ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"mcp-docs","type":"http","url":"https://modelcontextprotocol.io/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "mcp-docs": { "type": "http", "url": "https://modelcontextprotocol.io/mcp" } } } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "mcp-docs": { "serverUrl": "https://modelcontextprotocol.io/mcp" } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add mcp-docs --url https://modelcontextprotocol.io/mcp ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.mcp-docs] url = "https://modelcontextprotocol.io/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http mcp-docs https://modelcontextprotocol.io/mcp ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "mcp-docs": { "type": "http", "url": "https://modelcontextprotocol.io/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://modelcontextprotocol.io/mcp`. ## Details - Server version: 1.0.0 - MCP protocol version: 2026-07-28 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/mcp-docs (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report