Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search a nightly-refreshed directory of MCP servers by keyword, category or topic.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcpjunction.ai/mcpRun this in your terminal
claude mcp add --transport http directory https://mcpjunction.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"directory": {
"url": "https://mcpjunction.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"directory": {
"type": "http",
"url": "https://mcpjunction.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcpjunction.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain mcpjunction.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A directory of Model Context Protocol servers, rebuilt nightly from public GitHub metadata. Roughly 1,800 servers in a hand-owned category taxonomy, also browsable by repository topic, published as a website, a downloadable dataset, and an MCP endpoint your agent can query directly.
mcpjunction.ai · Dataset · Categories · Licensing
Not affiliated with Anthropic or the Model Context Protocol project.
This repository is the whole thing: the pipeline that builds the dataset, the Astro site that renders it, and the Cloudflare Worker that serves it.
Three ways in, all public and all free to read.
Bulk download. The full directory, regenerated nightly with a generated_at timestamp.
curl -O https://mcpjunction.ai/data/mcp_servers.json
mcp_servers.json — ~2.3 MB, 28 fields per server plus a dataset envelope with counts and per-category totalsmcp_servers.csv — the same data as 16 flat columnsQuery it from an agent. /mcp is itself an MCP server — streamable HTTP, stateless JSON-RPC over POST, protocol version 2025-06-18, no authentication.
claude mcp add --transport http mcpjunction https://mcpjunction.ai/mcp
| Tool | What it does |
|---|---|
search_servers | Free-text search, optionally filtered by category and language |
get_server | One server by id (owner--repo, e.g. microsoft--playwright-mcp) |
list_categories | Every category with active counts |
get_dataset_info | Counts, generated_at, source, and licensing terms |
GET /mcp returns 405 by design; POST your JSON-RPC messages. JSON-RPC batching is not supported — it was removed in protocol 2025-06-18.
Read it as markdown. Every server and category page has a clean markdown twin with no navigation or styling to strip. Either negotiate for it:
curl -H 'Accept: text/markdown' https://mcpjunction.ai/servers/microsoft--playwright-mcp
…or just append .md to the canonical URL — /servers/microsoft--playwright-mcp.md, /categories/databases.md. Each HTML page advertises its twin via .
Machine-readable entry points are collected in llms.txt.
Listing is automatic. There is no submission form, and none is planned — the pipeline runs five GitHub search queries (topic:mcp-server, topic:model-context-protocol, topic:mcp, and two name/description phrase searches), then keeps repositories that clear a 2-star floor and match a Model Context Protocol name/topic heuristic. If your server is on GitHub and meets that bar, it will appear on the next nightly run.
Corrections, removals, and licensing: , acknowledged within three business days.
Open to read and reuse; deliberately narrow about what comes back.
Corrections are the most useful thing you can send. A wrong install hint, a stale license, a repository that moved, a server sitting in the wrong category — open an issue or email the address above with the server id (owner--repo) and what's wrong. One maintainer cannot check 1,800 entries by hand, and the people who hit these find them first.
Pull requests are welcome for the software — src/, worker/, scripts/, docs/. Bug fixes need no preamble. Open an issue first for anything that changes rendered output or the dataset shape, because the constraints in the next section are load-bearing and easy to undo by accident.
Three things don't take pull requests, for reasons rather than ceremony:
The code is MIT and contributions to it are accepted on those terms. The dataset is separately licensed — see Licensing.
A directory other people cite has to fail safe. These are the constraints the code actually enforces:
security_reviewed, verified_badge, sponsor_tier, editorial_notes, and editorial_summary are set by hand and only carried forward by the pipeline — never written by it. A machine cannot grant a badge or a security clearance here. These fields are currently unset across the entire dataset; a written summary, when one exists, is a description and not a security review.status: archived_or_removed with a delisted_at timestamp, then drop. Stable URLs, without unbounded growth.owner--repo name — a rename, or a released username claimed by someone else — the editorial state is dropped rather than inherited.=, +, -, or @ are quote-prefixed before publication. Repository descriptions are attacker-controllable: anyone can name a GitHub repo.npx -y, no --yes. The registry package sharing a repository's name may belong to someone else entirely, so hints are published as unverified suggestions.src/ Astro static site — pages, layouts, components
worker/ Cloudflare Worker — the /mcp server and markdown negotiation scripts/ pipeline.py (GitHub API → dataset), build_sitemap.py categories.json Taxonomy: human-owned, first match in file order wins topics.json Approved /topics/ pages — vetted GitHub repository topics server.json Registry metadata for registry.modelcontextprotocol.io editorial/ Human-written server summaries (summaries.md) public/ Passthrough assets — robots.txt, license.xml, llms.txt, _headers, data/ dist/ Build output and the Worker's asset root (not committed)
Every night a GitHub Action runs pipeline.py, builds the site with Astro, generates the sitemap, commits the refreshed dataset, deploys the Worker, and then verifies the live result — licensing surface, /mcp handshake, crawler access rules, and markdown negotiation — before it calls the run a success.
Locally:
npm ci && npm run dev
The pipeline needs Python 3 and a GITHUB_TOKEN; deploys need Cloudflare credentials. See docs/OPERATIONS.md.
The code is MIT. src/, worker/, scripts/, and the configuration are yours to reuse — see LICENSE.
The dataset is not. public/data/** is excluded from the MIT grant and governed by the RSL terms in public/license.xml: search indexing is free, agent and inference-time use is free site-wide with attribution during the launch phase, and AI training requires a license. Bulk /data/ retrieval carries stricter terms. Details at mcpjunction.ai/licensing; see also NOTICE.
Citing us is easy and appreciated: *via mcpjunction.ai*.