Ref MCP
Ref's MCP server: documentation search for APIs and libraries that hands the agent only the relevant parts of pages
- 1,185 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Sends search queries to an external service
- Can index private repositories and PDFs
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ref-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Sends search queries to an external service
- Can index private repositories and PDFs
This is third-party code. Review the repository files before installing.
What it does
Ref gives the agent two tools: technical documentation search and reading a page by URL converted to Markdown. It searches public docs on the web and GitHub as well as private sources such as repositories and PDFs. The server tracks search history within a session: it never repeats results already shown, and when reading a large page it keeps only the most relevant parts. This saves context compared with a plain fetch. For OpenAI clients the tools are exposed as search and fetch.
Who it is for. For developers whose agents often read third-party API and library docs and burn many tokens doing so.
Good fit when
- The agent gets a library API wrong from outdated knowledge
- A plain docs fetch floods the context
- You need to search the team's private documentation
Not a fit when
- You cannot sign up for a Ref API key
- The docs already live in the repository as files the agent can read
Example request
Find the Figma API endpoint for posting a comment in the docs and show its parametersMCP
- Transport
- http, stdio
- Authentication
- API key
Environment variables
REF_API_KEYrequired, secret- Ref API key for the stdio server
Limitations
Requires signing up at ref.tools for an API key; plan terms are on the site. This repository holds the legacy stdio server; the authors recommend the remote HTTP one. Queries go to an external service; access from Russia without a VPN is unverified.
How to disable. Remove the Ref block from the MCP client config.
FAQ
Which connection option should I pick?
Remote HTTP: the authors call it recommended and the stdio server in this repo legacy.
How does Ref differ from plain page reading?
It returns about 5k tokens of the most relevant sections based on earlier searches rather than the whole page.
Discussion
No questions or reviews yet.
Related
MCP serversDocs MCP Server
Grounded Docs MCP Server
A local MCP server that indexes docs from websites, GitHub, npm, PyPI and files and gives the agent version-aware search
A remote MCP server that gives the agent docs and code of any public GitHub repository with nothing to install
Deepwiki MCP
Deepwiki MCP Server
MCP server that fetches deepwiki.com pages, cleans them and returns Markdown to the agent, as one document or split by page
An MCP server that turns a large codebase into a semantic feature graph for precise navigation and meaning-based search
A structural code search MCP server for agents: finds the right file by query intent and runs locally
An MCP server that answers an agent's questions from the documentation of one Rust crate at an exact version
README in short
The README explains how an agent searches and reads docs through Ref using sample call chains. It describes two context-saving mechanisms and why extra tokens hurt quality and cost. It gives HTTP and stdio configs, describes the tools and OpenAI deep research compatibility. MIT licensed.