Search
Search MCP guides and references.
Documentation ↗MCP server / documentation / source-linked
MCP Documentation Server
Official modelcontextprotocol.io endpoint scoped to published MCP documentation. The endpoint is valuable when a claim should resolve to an MCP-owned specification page rather than a search snippet. Keep feedback submission separate from ordinary reading because it changes external documentation state.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Official modelcontextprotocol.io endpoint scoped to published MCP documentation. The endpoint is valuable when a claim should resolve to an MCP-owned specification page rather than a search snippet. Keep feedback submission separate from ordinary reading because it changes external documentation state.
Implementation source ↗
Official modelcontextprotocol.io endpoint scoped to published MCP documentation. The endpoint is valuable when a claim should resolve to an MCP-owned specification page rather than a search snippet. Keep feedback submission separate from ordinary reading because it changes external documentation state.
Implementation source ↗
Official modelcontextprotocol.io endpoint scoped to published MCP documentation. The endpoint is valuable when a claim should resolve to an MCP-owned specification page rather than a search snippet. Keep feedback submission separate from ordinary reading because it changes external documentation state.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- hosted HTTP
- Authentication
- Public docs access; no local filesystem permission.
Add https://modelcontextprotocol.io/mcp, search the docs and retrieve the discovered path.
Setup reference ↗What it actually exposes.
Concrete capabilities with maintainer sources.
Exact retrieval
Read/search the virtual docs filesystem.
Documentation ↗Feedback
Submit documentation feedback as a separate action.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Resolve a Roots question (proposed; not tested)
Suggested evaluation, not an observed test result.
- Search for client Roots capability.
- Open the returned reference and update rules.
- Write a requirement checklist with links.
What to inspect: Each requirement has a docs passage; proposed, no feedback sent.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Queries operate on documentation chunks, not a real OS or arbitrary network.
Boundary reference ↗submit_feedback is a write action; do not call it without approval.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
Each requirement has a docs passage; proposed, no feedback sent.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Fetch MCP Server | Editorial inference: you know a URL outside MCP docs. | You must assess that source yourself. Documentation ↗ |
| Everything MCP Server | Editorial inference: you need client behavior tests. | Synthetic tests are not authoritative docs. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Can it read my files?
No; the virtual filesystem contains MCP docs only.
Documentation ↗
Should it submit feedback automatically?
No; ask before sending.
Documentation ↗
Source trail.
Maintainer documentation used in this record.