Directory
Ref (Ref Context)
Token-efficient docs search MCP
PaidMCP servers & registriesref.tools
What it is
An MCP server that searches public and private documentation from any MCP-compatible coding agent, tuned to return the relevant chunk rather than a whole page. Served at
https://api.ref.tools/mcp using an x-ref-api-key header or OAuth. Ref also ships Ref Plans, a plan-review workspace sharing the same credit pool.Why it earns a slot
Point it at your own private docs — internal API references, a design system, a team wiki — and the agent stops guessing at in-house conventions. Token efficiency keeps doc lookups from crowding out your actual code.
Know before you commit
No meaningful free tier, and credits are shared with Ref Plans, so plan-orchestration usage quietly drains your documentation-search budget.
Getting started
claude mcp add --transport http Ref https://api.ref.tools/mcp --header 'x-ref-api-key: YOUR_KEY'
Neighbourhood
How Ref (Ref Context) sits against the rest of the atlas — swaps, companions and the tools builders actually save alongside it.
Also in MCP servers & registries
Apify MCP
mcp.apify.comNot yet swept
Official MCP server (web scraping)
Free tier + paidMCP servers & registries
Free $5/mo platform credit · Starter $29/mo · Scale $199/mo
Open dossier
Browserbase MCP (Stagehand)
docs.browserbase.comNot yet swept
Official MCP server (cloud browser)
Free tier + paidMCP servers & registries
Free 1 browser hour · Developer $20/mo (100 hrs) · Startup $99/mo
Open dossier
Chrome DevTools MCP
github.comNot yet swept
Official MCP server (browser debug)
FreeMCP servers & registries
Free, open source
Open dossier
Cline MCP Marketplace
github.comNot yet swept
One-click MCP installs in Cline
FreeMCP servers & registries
Free
Open dossier