Skip to main content
hc
Submit
3 compared

Documentation MCP servers compared

Documentation-retrieval MCP servers that feed Claude up-to-date library docs, compared on trust, setup, and coverage.

Open in the interactive comparison tool
FieldContext7 MCP Server for Claude

Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use.

Open dossier 		Ref Tools MCP Server

MCP server for token-efficient documentation search and URL reading across public docs plus Ref-indexed private repositories, PDFs, and documentation sources.

Open dossier 		GitMCP Docs Server

Remote MCP server that turns any GitHub repository or GitHub Pages site into a documentation and code context source for AI coding assistants.

Open dossier
Trust
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcp
Sourcesource-backedsource-backedsource-backed
AuthorUpstashRef Toolsidosal
Added2026-06-022026-06-062026-06-05
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo———
Safety notes✓Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation. Returned documentation and code snippets are third-party content; review examples before running them in your project.✓Ref Tools sends search queries and read requests to the Ref API unless a custom `REF_URL` is configured. The server exposes `ref_search_documentation` and `ref_read_url`; OpenAI-style clients can receive compatible `search` and `fetch` tool names. Prompts can steer Ref toward private docs by using the private-source prompt path, so decide which users and clients may access private Ref resources. Protect Ref API keys, avoid placing keys in shareable config screenshots, and revoke keys when a client or workspace is retired. Review fetched URLs before relying on the returned markdown for security-sensitive implementation details.✓Repository-specific endpoints reduce the chance of an agent querying the wrong project, while the dynamic endpoint relies on correct target selection. Verify generated code against the upstream project documentation and changelog before applying it to production systems. Use caution with private, unreleased, or embargoed repositories unless you self-host and have reviewed access controls.
Privacy notes✓The library names and documentation topics you query are sent to the Context7 service to return matching docs. Avoid placing secrets or private identifiers in the library queries passed to the server.✓Search queries, read URLs, Ref API keys, session ids, client identifiers, result URLs, module ids, and returned documentation snippets may be processed by the Ref service. Private Ref resources can include repository content, PDFs, internal docs, proprietary API references, architecture notes, and vendor documentation. The HTTP transport can receive API keys through headers, query parameters, or encoded config depending on the client path. Redact keys, private URLs, module ids, internal search terms, and returned passages before sharing MCP logs or transcripts.✓GitMCP may receive repository choices, documentation queries, tool calls, and surrounding prompts through the MCP client. The README states that the hosted service does not collect personal information or store queries, but teams should still review the current privacy posture before sending proprietary context. Self-hosting may be preferable for private repositories, regulated work, or sensitive customer projects.
Prerequisites
  • Node.js 18+ and npx available (verify with: npx --version)
  • Claude Code or Claude Desktop with MCP support
  • Internet access so the server can reach the Context7 documentation service
  • Optional Context7 API key for higher rate limits; the server also works without one
  • Ref API key for hosted or stdio use.
  • MCP client with streamable HTTP support, or Node.js and npm for the legacy stdio package.
  • Agreement on whether the agent may search only public documentation or also Ref-indexed private resources.
  • Private repositories, PDFs, and docs uploaded to Ref reviewed for sensitivity before enabling private search prompts.
  • MCP client that supports remote MCP servers or an mcp-remote bridge.
  • GitHub repository owner and repository name, GitHub Pages site, or the dynamic GitMCP docs endpoint.
  • Network access to GitMCP and GitHub.
  • Team agreement on which repositories can be queried through a hosted MCP service.
Install
claude mcp add context7 -- npx -y @upstash/context7-mcp
REF_API_KEY=ref_api_key_here npx -y ref-tools-mcp@3.0.3
npx mcp-remote https://gitmcp.io/{owner}/{repo}
Config
{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "Ref": {
      "command": "npx",
      "args": ["-y", "ref-tools-mcp@3.0.3"],
      "env": {
        "REF_API_KEY": "<ref-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "gitmcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://gitmcp.io/{owner}/{repo}"
      ]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimed
More comparisons, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.