Ref Tools MCP

Ref Tools MCP is a Model Context Protocol (MCP) server that connects AI coding tools and agents to documentation for APIs, services, and libraries.

  • AI
  • Tools & Utilities
Ref Tools MCP is a Model Context Protocol (MCP) server that connects AI coding tools and agents to documentation for APIs, services, and libraries. It performs fast, token-efficient agentic search to provide exactly the context a developer or agent needs, helping code generation stay accurate and up to date.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

48/100 Fair

Maintained
75last commit 15 days ago
Popular
611,186 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM
Security check
201 serious finding, 6 minor, CI
GitHub stars
1,186
Open issues
13
Last commit
2026-11-06
License
MIT
Activity
declining

Checked yesterday - source: GitHub (ref-tools/ref-tools-mcp)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Get and paste your Ref API key Copy your API key (a secret login key) from ref.tools/keys and replace <YOUR_API_KEY> or YOUR_API_KEY before saving. Without a real key, Ref can't authenticate and its documentation search tools won't work. source
  • Verify Ref connected after setup After adding the MCP (Model Context Protocol, the add-on system that gives your app tools), run amp mcp doctor if you used Amp. This catches typos or missing keys before you rely on Ref. source
  • Set the right team scope if needed If you use OAuth sign-in with Teams and belong to multiple teams, add scope=user or scope=t-team_id to the Ref URL. This stops Ref from guessing the wrong account or team. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What credential must be configured before Ref Tools MCP can search documentation?

Replace the API key placeholder with a real Ref API key from ref.tools/keys. Without a valid key, Ref cannot authenticate and its documentation search tools will not work.

How do I choose the correct Ref team when using OAuth sign-in?

If you belong to multiple teams, add scope=user or scope=t-team_id to the Ref URL. This stops Ref from guessing the wrong account or team.

How do I confirm the Ref MCP connection is working in Amp?

Run amp mcp doctor after adding the MCP. It catches typos or missing keys before you rely on Ref.

Does the server aim to limit the amount of documentation context sent to the model?

Yes, it performs fast, token-efficient agentic search to provide only the documentation context an agent needs.

Answers sourced from docs.ref.tools, docs.ref.tools, github.com

Community

Collected 48 days ago - public community threads