Best MCP Server Directories in 2026: Where to Find Them

The best MCP server directory in 2026 is Remote OpenClaw, which indexes 13,870+ Model Context Protocol servers, is free with no signup, and works for Claude Code, Codex, OpenCode, OpenClaw, and Hermes. Full disclosure: Remote OpenClaw is our directory, so we have ranked seven strong alternatives below it, including the official MCP registry, Glama, PulseMCP, and Smithery, each with real strengths and one honest limitation.

How We Ranked the Directories

An MCP server directory earns its rank on four factors: how many servers it indexes, whether listings carry trust signals like quality grades or official badges, whether it supports multiple agents, and whether you can get from listing to installed server without friction. We verified every directory live in July 2026 and flagged any count that could only be traced to secondary sources. This is a list of places to find MCP servers; if you want the servers themselves ranked, see our best MCP servers list.

The 8 Best MCP Server Directories in 2026

1. Remote OpenClaw

Remote OpenClaw's MCP directory indexes 13,870+ servers and is the only entry on this list that covers Claude Code, Codex, OpenCode, OpenClaw, and Hermes from one index. Full disclosure: Remote OpenClaw is our directory. The concrete reasons it leads the list: it is free, requires no signup, publishes public usage analytics, and each listing shows a copyable install command for your agent. You can also skip the browser entirely: npx remoteopenclaw search postgres searches the index from your terminal, and our open-source Remote OpenClaw MCP server lets your agent run the same search itself mid-task. The honest limitation: it is a directory, not a host, so remote servers that need managed OAuth are easier to run through Smithery.

2. The official MCP registry

The official MCP registry at registry.modelcontextprotocol.io is the canonical upstream source of MCP server metadata, maintained by the MCP project's Registry Working Group. Launched in preview in September 2025 with its v0.1 API frozen in October 2025, it offers a REST API and the mcp-publisher CLI, which verifies namespaces through GitHub or DNS proof, so a listing under a company's domain actually belongs to that company. Directories like PulseMCP consume it programmatically. The limitation is deliberate: it is still preview software with a minimal browsing UI and no quality vetting, so treat it as the source of truth rather than the place you browse.

3. Glama

Glama lists 50,845 open-source MCP servers as of July 3, 2026, the largest count of any directory we verified. Its standout is automated quality grading: every server gets license, code quality, and maintenance-recency ratings on an A to F scale, plus a "claimed" badge on 7,767 servers where the author has verified ownership. Semantic search and 30+ categories make the volume navigable. The limitation follows from the size: the grades are automated heuristics rather than manual security review, and the 50k count includes thousands of unmaintained or duplicate forks you need the filters to avoid.

4. PulseMCP

PulseMCP indexes 20,109 servers, updates daily, and pairs the directory with the most useful editorial layer in the ecosystem: a clients directory, curated use-case walkthroughs, and a weekly newsletter. Its listings hew close to the official registry, with filters for Anthropic references, official providers, and remote-available servers. It is the best read for understanding what people actually do with MCP. The limitation: it is discovery and editorial only, with no hosting, no CLI, and no quality or security scoring on listings.

5. Smithery

Smithery is the only major directory that doubles as a managed host: many of its servers run as Smithery-hosted remote endpoints with credential management and OAuth handled for you, plus a CLI (npm i -g smithery) for searching, adding, and publishing servers. Browsing and installing are free; vendors publishing hosted servers pay from $10 per month including $10 of credits, then $0.10 per 1,000 RPCs. That hosting is also the honest tradeoff: hosted servers proxy your traffic and credentials through Smithery's infrastructure, which is a real trust decision for anything touching production data.

6. mcp.so

mcp.so is one of the largest community-driven directories and covers both MCP servers and MCP clients, with featured, latest, hosted, and official tabs across categories from browser automation to knowledge and memory. Uniquely, the site itself is open source: the chatmcp/mcpso codebase is on GitHub under Apache-2.0, so you can see exactly how listings are assembled. Third-party roundups put its catalog around 20,000 servers, though the site does not display a verifiable total. The limitation: listings are scraped or submitted with no quality scoring or security vetting, so you are on your own for due diligence.

7. mcpservers.org

mcpservers.org takes the opposite approach to the mega-indexes: a curated, awesome-list-style directory aimed at "Claude, Codex, Cursor, and other AI agents," with an official-server designation, 15+ categories, and topic guides like Browser Automation MCP. It reads like a well-maintained reading list, which is exactly what you want when you need one good server rather than fifty candidates. The limitation is the flip side of curation: no stated total count, no published vetting criteria, and no API or install tooling.

8. MCP Market

MCP Market presents itself as a community-curated catalog of 10,000+ servers across 23+ categories, from security and testing to game development, with official and featured collections and per-server install details for Claude, Cursor, and Windsurf. Category depth is its strength; niches like e-commerce and analytics get dedicated shelves that bigger indexes bury. One honest caveat: aggressive bot protection blocked every automated fetch we tried, so its counts could not be confirmed first-hand, and that same wall keeps AI assistants from citing it.

Comparison Table

Here is how the eight MCP server directories compare on size, agent coverage, cost, and standout capability as of July 2026.

Finding MCP Servers for Claude Code

Claude Code installs MCP servers with the claude mcp add command, which supports stdio, HTTP, and SSE transports. Per the official Claude Code MCP docs, the double dash separates Claude's flags from the server command:

# Local stdio server
claude mcp add airtable --env AIRTABLE_API_KEY=KEY -- npx -y airtable-mcp-server

# Remote HTTP server
claude mcp add --transport http notion https://mcp.notion.com/mcp

# Add the Remote OpenClaw search server, then ask Claude to find servers itself
claude mcp add remoteopenclaw -- npx -y remoteopenclaw

Use --scope project to write a shared .mcp.json for your team, and run /mcp in-session for OAuth flows. Our Claude Code MCP guide covers scopes and troubleshooting, this walkthrough shows how to search directories from the CLI, and the best MCP servers for Claude Code ranking names the servers worth installing first.

Finding MCP Servers for Cursor

Cursor reads MCP servers from .cursor/mcp.json in a project or ~/.cursor/mcp.json globally, and supports stdio, SSE, and Streamable HTTP transports per the Cursor MCP docs. Stdio entries take command, args, and env keys; remote entries take a url plus optional headers or a static OAuth config. Cursor also supports one-click "Add to Cursor" deeplinks, which Glama and MCP Market embed on listing pages. Any server in the Remote OpenClaw directory drops into that JSON with the command shown on its listing.

Finding MCP Servers for OpenClaw and Hermes

OpenClaw and Hermes do not ship a native MCP catalog, so a cross-agent directory matters more for them than for Claude Code. The common pattern is to bridge MCP servers in as tools via a JSON config or an adapter such as mcporter, then let the agent call them like any other capability. The Remote OpenClaw MCP directory tags which servers work agent-agnostically over stdio, which is the safest bet for OpenClaw and Hermes setups, and our Hermes MCP integration guide walks through wiring a server into a running Hermes agent step by step.

When a Directory Is Not Enough

No MCP directory audits server code for you, and every server you install runs with real credentials and real tool access. Counts and grades are signals, not guarantees: Glama's A grade is an automated heuristic, namespace verification proves ownership rather than safety, and the biggest indexes knowingly include abandoned forks. Read the server's source or at least its README, prefer official vendor servers for anything holding secrets, and scope API keys tightly. If you only need one or two well-known servers, installing straight from the vendor's docs is a perfectly good answer.

Related Guides

• Best MCP Servers in 2026: The Complete Ranked List
• Claude Code MCP: How to Add and Manage MCP Servers
• How to Find MCP Servers From Inside Claude Code
• Claude Plugins: What They Are and How to Install Them