Ref
MCP server by Ref
Search public and private documentation and read pages as markdown while using as few tokens as possible.
Connect to Ref
Ref needs an API key. Connect with its own URL and your key:
Send your key in the X-Ref-Api-Key header. mcp.tc never sees or stores keys. Where to get a key
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/ref-toolsAbout
Ref gives coding agents access to documentation for APIs, services and libraries. It searches public docs on the web and GitHub, plus private sources such as repos and PDFs, and reads a URL as markdown. It uses the MCP session's search history to skip repeated results and return only the most relevant part of a page, about 5k tokens.
A hosted streamable HTTP endpoint is available at https://api.ref.tools/mcp, which takes an API key in the X-Ref-Api-Key header or an apiKey query parameter. A local stdio package, ref-tools-mcp, runs with npx and reads REF_API_KEY. The source is MIT licensed.
What you can do
- Search public documentation on the web and GitHub
- Search private repos and PDFs
- Read any URL converted to markdown
- Skip repeated results across similar searches in a session
- Return the most relevant part of a long page
- Expose search and fetch tool names for OpenAI deep research
Tools
Ref lists its tools only to clients with a key, so we can’t show them here.
Example prompts
Find the Figma REST API endpoint for posting a comment.
Search the docs for how the n8n Merge node handles multiple inputs.
Read this documentation URL and summarize the auth section.
Look up the correct usage of this library's config options in its docs.
Set up
Every client connects to api.ref.tools. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http ref-tools https://api.ref.tools/mcp --header "X-Ref-Api-Key: <YOUR_API_KEY>"- Replace the placeholder with your key before you run it, then check it with
/mcpinside Claude Code.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Use the
mcp-remotebridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"ref-tools": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.ref.tools/mcp",
"--header",
"X-Ref-Api-Key: <YOUR_API_KEY>"
]
}
}
}- Replace the placeholder with your key and restart Claude Desktop.
The bridge needs Node.js on your computer.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://api.ref.tools/mcp. Under Request headers, addX-Ref-Api-Key: <YOUR_API_KEY>with your key from Ref, then click Add. - 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.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"ref-tools": {
"url": "https://api.ref.tools/mcp",
"headers": {
"X-Ref-Api-Key": "<YOUR_API_KEY>"
}
}
}
}VS Code
Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:
{
"servers": {
"ref-tools": {
"type": "http",
"url": "https://api.ref.tools/mcp",
"headers": {
"X-Ref-Api-Key": "${input:x-ref-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "x-ref-api-key",
"description": "X-Ref-Api-Key",
"password": true
}
]
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"ref-tools": {
"serverUrl": "https://api.ref.tools/mcp",
"headers": {
"X-Ref-Api-Key": "<YOUR_API_KEY>"
}
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add ref-tools --url https://api.ref.tools/mcpcodex mcp add can’t set the X-Ref-Api-Key header, so this step is required: put this entry in ~/.codex/config.toml instead of running the command, or add its env_http_headers line to the entry the command made:
[mcp_servers.ref-tools]
url = "https://api.ref.tools/mcp"
env_http_headers = { "X-Ref-Api-Key" = "X_REF_API_KEY" }Codex reads the header values from the environment variables named in env_http_headers.
Gemini CLI
gemini mcp add --transport http --header "X-Ref-Api-Key: <YOUR_API_KEY>" ref-tools https://api.ref.tools/mcpThis 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.
{
"mcpServers": {
"ref-tools": {
"type": "http",
"url": "https://api.ref.tools/mcp",
"headers": {
"X-Ref-Api-Key": "<YOUR_API_KEY>"
}
}
}
}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://api.ref.tools/mcp.
Embed
Show Ref in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/ref-tools)<a href="https://mcp.tc/i/ref-tools"><img src="https://mcp.tc/i/ref-tools/badge.svg" alt="Ref on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/ref-tools.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/ref-tools" title="Ref on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/ref-tools.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Ref card to your site.
Add the mcp.tc card for Ref, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/ref-tools.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="ref-tools"><a href="https://mcp.tc/i/ref-tools">Ref on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/ref-tools)
```
Reference: https://mcp.tc/embedChange history
Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.
Nothing recorded yet. Edits by the server’s owner will show up here.
FAQ
Can I paste mcp.tc/i/ref-tools into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://api.ref.tools/mcp, so your client talks to Ref directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Ref need an API key or a sign-in?
Yes. Ref needs an API key, sent as the X-Ref-Api-Key header. Get one from Ref and keep it in your client’s config, never in a shared file.
Is Ref a remote or a local server?
Remote. Ref hosts it at https://api.ref.tools/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Ref do?
You can search public documentation on the web and GitHub, search private repos and PDFs and read any URL converted to markdown.
Which clients can use it?
Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.
Does mcp.tc track changes to Ref?
Partly. Ref’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Ref’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Ref. This page was built from Ref’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.