The open directory for Model Context Protocol (MCP) servers - discover, evaluate, and install 22,000+ servers for Claude, Cursor, and AI agents.
概要
Discover, evaluate, and install MCP servers — give your AI agents superpowers. Model Context Protocol servers let AI agents talk to real systems — databases, browsers, filesystems, APIs. There are thousands of them, scattered across GitHub repos with inconsistent READMEs and no common way to search or compare them. AllMCPs is the directory that fixes that. It catalogs with semantic search, category browsing, health checks, and a copy-paste install config for every listing. - across 50+ categories, with per-listing detail pages covering install steps, tools exposed, and upstream health. - — config generator and validator, protocol inspector, token calculator, OpenAPI-to-MCP converter, and a playground. - — every listing has a copy-paste agent prompt, and the site exposes llms.txt, an MCP server of its own, and DNS-based agent discovery. - — maintainers prove ownership of a repo or domain and edit their own listings. Listings live in a database — submit at allmcps.
README
What this is
Model Context Protocol servers let AI agents talk to real systems — databases, browsers, filesystems, APIs. There are thousands of them, scattered across GitHub repos with inconsistent READMEs and no common way to search or compare them.
AllMCPs is the directory that fixes that. It catalogs 22,000+ MCP servers with semantic search, category browsing, health checks, and a copy-paste install config for every listing.
- Search and browse across 50+ categories, with per-listing detail pages covering install steps, tools exposed, and upstream health.
- Free browser tools — config generator and validator, protocol inspector, token calculator, OpenAPI-to-MCP converter, and a playground.
- Agent-native — every listing has a copy-paste agent prompt, and the site
exposes
llms.txt, an MCP server of its own, and DNS-based agent discovery. - Claim and verify — maintainers prove ownership of a repo or domain and edit their own listings.
[!NOTE] Adding a server doesn’t need a pull request. Listings live in a database — submit at allmcps.com/submit, and claim an existing listing from its page to edit it.
Quick start
Requires Node 22 (see .nvmrc).
bun install
bun run dev
Open localhost:3000. No Cloudflare account, database, or API key is needed to run the site locally.
In next dev there are no Cloudflare bindings, so data comes from
data/mcp-servers.json — a sample catalog of ~113 listings spanning every
category, enough to work on essentially any page. In production the same code
paths read from D1 and fall back to that file on error (see lib/servers.ts).
To work against the full catalog locally, rebuild it from the public source lists — and don’t commit the result:
node scripts/seed.mjs
Tech stack
| Layer | Choice |
|---|---|
| Framework | Next.js (App Router) on OpenNext |
| Runtime | Cloudflare Workers |
| Database | Cloudflare D1 (SQLite) via Drizzle ORM |
| Search | Cloudflare Vectorize + Workers AI for semantic search |
| Storage | R2 for logos, screenshots, and the ISR cache |
| Auth | Auth.js magic links, with Turnstile on public forms |
| Tooling | Biome, Vitest, Lefthook |
Project layout
app/ App Router routes — directory, listings, tools, guides, blog, API
components/ Shared React components and UI primitives
lib/ Data access and domain logic (lib/servers.ts is the entry point)
db/ drizzle/ Drizzle schema and numbered migrations
content/blog/ Markdown blog posts (YYYY-MM-DD-slug.md)
mcp-server/ The AllMCPs MCP server itself
scripts/ Build, enrichment, ingest, and maintenance scripts
Scripts
| Command | What it does |
|---|---|
bun run dev |
Start the dev server |
bun run build |
Production build |
bun run verify |
Typecheck + lint + tests — the gate before any PR |
bun run check |
Biome format and lint, writing fixes |
bun run test |
Vitest suite |
bun run preview |
Build with OpenNext and preview the Workers bundle |
bun run deploy |
Build and deploy to Cloudflare Workers |
bun run db:generate |
Generate a Drizzle migration from db/schema.ts |
bun run db:migrate:local |
Apply migrations to the local D1 |
Contributing
Contributions are welcome — see CONTRIBUTING.md for setup, the checks a change has to pass, and the conventions that aren’t obvious from the code.
Two worth knowing up front:
- This is not the Next.js you may know. The project tracks a newer release
with breaking changes. Read the bundled guides in
node_modules/next/dist/docs/before writing routing or rendering code. See AGENTS.md. - UI work follows BRAND_GUIDE.md — colors, typography, and logo usage.
Please read the Code of Conduct before participating, and report security issues privately per SECURITY.md.
License
Source code is MIT licensed.
The catalog data in data/mcp-servers.json describes third-party projects and
remains the property of their authors. Blog posts in content/blog/ are
© Jackalope Digital, all rights reserved. The AllMCPs name, logo, and
brand-assets/ are trademarks of Jackalope Digital and aren’t covered by the
MIT grant — see LICENSE.
インストール
This server does not publish a one-line install command.
Open the repository installation guide