docs-mcp-server vs ref-tools-mcp
docs-mcp-server: Docs MCP Server provides an always-current, personal documentation index to combat AI hallucinations and outdated knowledge for AI coding assistants. It fetches official documentation from various sources, including websites, GitHub, and local files, allowing AI to query exact library versions.; ref-tools-mcp: Ref MCP is a server that enables AI coding tools and agents to access technical documentation efficiently. It optimizes token usage by filtering search results and extracting only the most relevant parts of documentation pages, helping models stay focused and reducing operational costs.
Ref is a hosted search tuned to return small slices of docs. docs-mcp-server keeps the index and queries on your machine.
TL;DR
- You need internal or private documentation indexed alongside public libraries.
- Everything must stay on your machine or network.
- You want answers for the exact library version your project uses.
- You do not want to scrape and index each library yourself: hosted indexes come ready-made.
- You cannot run Node.js 22 or newer.
- You want the best search quality with no embedding model or API key: the README says search is better with embeddings.
- Context size is your main concern: page reads return about the most relevant 5k tokens, and repeat searches do not return the same results in a session.
- You want two simple tools, search and read-URL, in Claude Code, Cursor or another MCP client.
- You want to search private resources such as repos and PDFs alongside public docs.
- You cannot send queries to a vendor: it needs an API key and the hosted ref.tools service.
- You want the recommended HTTP server: this repository is the legacy stdio server.
- You need independent proof of the token savings: the README's numbers are the project's own example traces.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.