# Best MCP Marketplaces & Registries (2026)

> The best MCP marketplaces and registries in 2026, compared — the official registry, Glama, mcp.so, Smithery, PulseMCP, Docker, and what each is for.

Source: https://designrevision.com/blog/best-mcp-marketplaces-and-registries

---

The best MCP marketplaces and registries are where you go to *find* Model Context Protocol servers — the directories that turn "does an MCP server exist for this?" into a two-minute search. In 2026 the field has sorted into a canonical **registry** (the official one) and a layer of **marketplaces** on top of it (Glama, mcp.so, Smithery, PulseMCP, Docker, and more), each with a different strength. Whether you searched for an *MCP server marketplace*, an MCP store, or a registry, this guide compares the ones worth your time, explains the registry-vs-marketplace split most posts skip, and shows where a specialist registry fits.

*Last updated: July 2026. The MCP directory space moves fast — new marketplaces launch monthly and server counts change weekly; every entry here was checked in July 2026, but treat specific numbers as approximate.*

## Registry vs. Marketplace: The Distinction That Matters

These two words get used interchangeably, and they shouldn't be:

- A **registry** is the canonical metadata layer — a machine-readable index of servers (name, description, where to install), designed for *tools* to build on. The [official MCP Registry](https://registry.modelcontextprotocol.io) is the reference example.
- A **marketplace** is the human-facing layer on top — search, categories, quality scores, one-click install, sometimes hosting or monetization. Glama, mcp.so, and Smithery are marketplaces, and increasingly they consume registry data underneath.

The practical upshot: the registry is your source of truth, marketplaces are where discovery is pleasant. You'll use both.

## The Best MCP Marketplaces & Registries at a Glance

| Directory | Type | Best for |
|-----------|------|----------|
| Official MCP Registry | Registry | The canonical, authoritative index |
| Glama | Marketplace | Largest curated directory + quality scores |
| mcp.so | Marketplace | Broad discovery and an MCP "store" |
| PulseMCP | Marketplace | Freshness — weekly updates and news |
| Smithery | Marketplace + hosting | One-click hosted deployment |
| Docker MCP Catalog | Marketplace | Containerized, security-scanned servers |
| Awesome MCP Servers | Curated list | The community's hand-picked GitHub list |
| Cursor Directory | Client gallery | One-click "Add to Cursor" |
| VS Code `@mcp` gallery | Client gallery | In-editor install for Copilot |
| DesignRevision | Specialist registry | shadcn/ui components, not general tools |

## How We Judged Them

A marketplace is only as good as what it saves you, so we judged these the way you'd actually use them — searching the same handful of servers (a GitHub connector, a Postgres server, a UI server) across each and seeing what came back. Four things separated them:

- **Coverage** — how much of the real ecosystem it indexes. The gap between a directory that lists a niche server and one that doesn't is the entire point of using it.
- **Trust signals** — quality scores, security scanning, and provenance, not a raw dump of names. The difference between Glama's scored listings and an unvetted list is real when you're about to run someone's code.
- **Install friction** — a one-click button or a copy-paste config beats "clone the repo and figure it out." This is where the in-editor galleries pull ahead.
- **Freshness** — a directory that's months stale is worse than useless, because MCP servers rename and move constantly. This is where PulseMCP earns its spot.

Specialist registries like DesignRevision are judged differently — by depth in their niche, not breadth.

## The Marketplaces & Registries

### 1. Official MCP Registry

**Type:** Registry · **Best for:** the canonical, authoritative index · **Link:** [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io)

**Start here.** The official registry is the community-maintained index published by the Model Context Protocol project itself, which makes it the closest thing to a source of truth — and the reason it matters is that the good marketplaces increasingly sync *from* it. Its own interface is more developer-facing than polished, so most people discover through a marketplace and rely on the registry for provenance. *Use it to* confirm a server is real and official before installing.

### 2. Glama

**Type:** Marketplace · **Best for:** the largest curated directory with quality signals · **Link:** [glama.ai](https://glama.ai/mcp/servers)

**The generalist leader.** Glama indexes a very large catalog — several thousand open-source MCP servers as of mid-2026 — and layers on quality and security scoring, so you're not just staring at an undifferentiated list. It also hosts servers and has a strong "alternatives to X" discovery flow. If you only bookmark one general marketplace, this is the safe pick. *Watch for* the usual directory caveat — inclusion isn't endorsement, so still check a server's source.

### 3. mcp.so

**Type:** Marketplace · **Best for:** broad discovery and an MCP "store" · **Link:** [mcp.so](https://mcp.so)

**The high-traffic directory.** mcp.so consistently ranks at or near the top of search for the term, and positions itself as a store, server list, and curated directory in one. Coverage is broad and it's a good second opinion to Glama when you're hunting for something niche. *Watch for* breadth over curation — more listings, lighter vetting.

### 4. PulseMCP

**Type:** Marketplace · **Best for:** freshness and staying current · **Link:** [pulsemcp.com](https://www.pulsemcp.com)

**The one that's never stale.** PulseMCP is known for keeping pace — frequent updates, new-server tracking, and MCP news alongside the directory. When something launched last week, this is where it shows up first. *Use it to* stay current rather than as an exhaustive archive.

### 5. Smithery

**Type:** Marketplace + hosting · **Best for:** one-click hosted deployment · **Link:** [smithery.ai](https://smithery.ai)

**Discovery plus deployment.** Smithery is a registry and marketplace that also *hosts* servers, so you can go from "found it" to "running it" without provisioning anything — handy for remote servers you'd otherwise self-host. *Watch for* the trade-off of routing tool traffic through a third party; fine for many servers, worth a thought for sensitive ones.

### 6. Docker MCP Catalog

**Type:** Marketplace · **Best for:** containerized, security-scanned servers · **Link:** [hub.docker.com/mcp](https://hub.docker.com/mcp)

**The security-first option.** Docker's MCP Catalog (paired with the MCP Toolkit) distributes servers as vetted container images, which sidesteps the "random `npx` package" trust problem and gives you isolation by default. If your team cares about supply-chain hygiene, start here. *Watch for* the Docker dependency — great if you already run it, extra weight if you don't.

### 7. Awesome MCP Servers

**Type:** Curated list · **Best for:** the community's hand-picked shortlist · **Link:** [github.com/punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers)

**The original.** Before the polished marketplaces, there was the "awesome" list — a community-maintained GitHub README grouping servers by category. It has no install flow, but it's an excellent, opinionated map of what exists, and it's still one of the fastest ways to scan a category. *Use it to* orient, then install elsewhere.

### 8. Cursor Directory & VS Code Gallery

**Type:** Client galleries · **Best for:** one-click install inside your editor · **Links:** [cursor.directory](https://cursor.directory), VS Code's `@mcp` gallery

**Discovery where you work.** Both Cursor and VS Code ship in-editor galleries with one-click install, so you never leave the editor. They're narrower than a full marketplace but unbeatable for friction. If you live in one tool, its gallery is often the fastest path. See our guides on adding servers to [Cursor](/blog/add-mcp-server-to-cursor) and [VS Code](/blog/add-mcp-server-to-vscode).

### 9. DesignRevision — The Specialist Registry

**Type:** Specialist registry · **Best for:** real shadcn/ui components, not general tools · **Link:** [DesignRevision MCP](/mcp)

**The niche done deeply.** Most entries above are *generalist* — they index every kind of server. [DesignRevision](/mcp) is the opposite: a specialist registry for one job done well, serving real, production-grade [shadcn/ui components](/components) to your agent through a single MCP server. You won't find a database connector here, but you also won't find a deeper, better-maintained source of installable UI anywhere on the generalist lists. *Use it when* the thing you're building is a frontend — alongside, not instead of, a generalist marketplace.

## Which One Should You Use?

For most people the answer is **two**: a generalist marketplace for breadth (Glama or mcp.so), plus whatever's closest to your workflow — your editor's gallery for one-click install, or a specialist registry like DesignRevision when you're building UI. Anchor both to the **official registry** when you need to confirm a server is legitimate. You don't need to pick a single home; you need a browse-first stop and a trust-check stop.

## Listing Your Own MCP Server

Building a server rather than shopping for one? The distribution order that gets the most reach: submit to the **official MCP Registry** first (the marketplaces increasingly sync from it), then list on **Glama**, **mcp.so**, and **PulseMCP**, and add the **client galleries** (Cursor Directory, Cline Marketplace) to reach those tools' users. Each has its own submission flow, but the registry is the highest-leverage first step.

## Conclusion

The MCP directory space in 2026 is a canonical **registry** with a layer of **marketplaces** on top: the official registry for truth, Glama and mcp.so for breadth, PulseMCP for freshness, Smithery for hosting, Docker for security, and the client galleries for one-click install. Browse a generalist for discovery, lean on the official registry to verify, and reach for a specialist like DesignRevision when your work is UI. Two bookmarks beat ten.

---

## Related Resources

- [DesignRevision MCP — the shadcn/ui MCP server](/mcp)
- [MCP Clients Compared: Every AI Coding Agent](/blog/mcp-clients-compared)
- [Best MCP Servers for Claude Code (2026): Tested & Ranked](/blog/best-mcp-servers-for-claude-code)
- [Best MCP Servers for Cursor (2026): Ranked](/blog/best-mcp-servers-for-cursor)
- [Best MCP Servers for Codex (2026): Ranked](/blog/best-mcp-servers-for-codex)
- [Browse the shadcn/ui component registry](/components)