Best AI Agent Skills & MCP Server Marketplaces in 2026
Skills.sh, mcpservers.org, Smithery, Glama, and claudemarketplaces.com compared — traffic, listing mechanics, and where to find or list a tool.
If you're trying to find a web-data MCP server or skill — or trying to get your own listed — "search the marketplace" undersells how fragmented this ecosystem actually is. At least seven directories index MCP servers and Agent Skills with real, different traffic, and they don't all sync with each other. This compares the ones worth knowing about, how each actually gets you listed, and what we found checking our own presence across all of them.
What to evaluate
- Does listing require a submission/PR, or does it happen automatically from real usage telemetry?
- Traffic — is this a place developers actually browse, or a low-traffic SEO farm?
- Does it index MCP servers, Agent Skills, or both — they're different things and not every directory covers both.
- Does it mirror or feed other directories (the Official Registry does; most don't)?
- Editorial vs. self-serve — a couple of these are curated 'best of' posts, not open directories.
The directories
Traffic figures are SimilarWeb estimates gathered mid-2026 — treat them as directional, not exact, and re-check before making a submission-priority decision months from now.
| Directory | ~Visits/mo | Indexes | Listing mechanic |
|---|---|---|---|
skills.sh (officialskills.sh) | ~3.07M | Agent Skills | Automatic — surfaces from real npx skills add install telemetry, no submission form |
| mcpservers.org | ~618K | MCP servers + Agent Skills (separate sections) | Submit form (/submit), category-tagged (has a dedicated Web Scraping category) |
| claudemarketplaces.com | ~380K | Claude Code skills, MCP servers, and marketplaces | Auto-updates from GitHub; policy checks for spam/off-topic, not a manual review queue |
| Smithery | ~475K | MCP servers | Auto-indexes + scores server quality (0-100) on naming, schemas, and descriptions |
| skillsmp.com | ~777K | Agent Skills | Submit form |
| claudeskills.info | ~176K | Claude Code skills (community-contributed) | Submission/PR |
| Glama | ~111K | MCP servers | Auto-indexes public GitHub repos; can build/score a local server, not a hosted-only one |
Official MCP Registry (registry.modelcontextprotocol.io) | — (API, not a browsable site) | MCP servers | mcp-publisher CLI + DNS-based domain auth; the canonical upstream several of the above mirror from |
skills.sh — the keystone, and it's not a submission form
If one channel matters most for Agent Skills specifically, it's this one: listing is automatic the moment real users install your skill via npx skills add <owner/repo>. There's no form to fill out — which also means a skill with zero real installs stays invisible here regardless of how good it is. The biggest GitHub "awesome" lists (VoltAgent's 24.8k-star awesome-agent-skills, for one) link entries straight to officialskills.sh/<vendor>/... pages, so getting real installs flowing is the actual unlock, not a submission queue.
mcpservers.org — has an actual Web Scraping category
Indexes both MCP servers and Agent Skills through a straightforward /submit form, and — unusually for this space — has a dedicated Web Scraping category rather than burying scrapers under generic "tools." A $39 fast-track badge is optional; the free submission path works fine.
claudemarketplaces.com — Claude Code-specific, high traffic, no manual review queue
The largest Claude-Code-specific directory by traffic, auto-updating from GitHub with policy checks (spam/off-topic) rather than a human review queue — so getting listed is closer to "ship a well-formed plugin marketplace.json and get discovered" than "submit and wait." It's also where competitor listings are easiest to check at a glance: Firecrawl's MCP server, for instance, shows its exact tool count and install command on its own detail page here.
Smithery — the only one that scores quality, not just presence
Smithery auto-indexes MCP servers and additionally computes a quality score (0-100) based on tool naming conventions, parameter/output schema completeness, and description quality — genuinely useful signal beyond "is it listed," since two listed servers can have wildly different scores. Auth-required servers structurally can't reach the top of the score band (optional-config points are mutually exclusive with a required auth schema), so don't chase 100 — compare your score against reference servers in your category instead.
Official MCP Registry — the one that feeds the others
registry.modelcontextprotocol.io is the canonical upstream registry several mirrors (PulseMCP among them) pull from automatically. Publishing here is more setup than the others (the mcp-publisher CLI plus DNS-based domain ownership verification via a TXT record), but it's the one submission that propagates without a separate form per mirror.
Glama — auto-indexes, but a hosted-only server can't be fully scored
Glama pulls in public MCP server repos automatically. One real limitation worth knowing before you invest time here: its build/scoring step runs the server locally — a purely hosted MCP endpoint with no local runnable server (no npx/Docker path) can't be built and therefore can't be scored, even if it's listed. If your server is hosted-only, ship a small local stdio wrapper alongside it if you want a Glama score.
What we found checking our own listings
Researching this piece meant checking Crawlora's own presence everywhere in the table above — worth sharing as a real example of how uneven coverage gets across an ecosystem this fragmented, even when you've actively worked on distribution:
- Registered: Official MCP Registry (
net.crawlora/crawlora-mcp), Smithery (quality score 81/100), Glama (built + scored), skills.sh (skills.sh/crawlora-org, 5 skills), mcpservers.org (crawlora-net-mcp). - Confirmed absent as of this pass: claudemarketplaces.com.
That's not a complaint about the ecosystem — it's the actual state of things when you list across seven independent channels with seven independent mechanics. If you're evaluating your own coverage, checking each directory directly (not assuming a registry publish covers everything) is the only reliable way to know where you actually stand.
How to prioritize, if you're listing a tool
- Building an Agent Skill → get real installs flowing first (skills.sh is telemetry-driven, not a form), then PR the GitHub awesome lists that link to your skills.sh page.
- Building an MCP server → the Official MCP Registry first (it feeds mirrors), then Smithery and Glama for the quality-score visibility, then mcpservers.org for the category-specific traffic.
- Targeting Claude Code specifically → claudemarketplaces.com and the Claude Code plugin-marketplace mechanic (
/plugin marketplace add) matter more here than the general MCP directories. - Just looking for a tool, not listing one → start with skills.sh or mcpservers.org depending on whether you want a skill or an MCP server — both let you filter by category, and Smithery's quality score is a fast way to sanity-check a candidate before installing it.
Find Crawlora across the ecosystem
893 MCP tools / 5 Agent Skills, registered on the Official MCP Registry, Smithery, Glama, skills.sh, and mcpservers.org. Pay-on-success, 2,000 free credits a month.
Sources
Related reading
Frequently asked questions
What's the best directory to find an MCP server or Agent Skill?
It depends what you're looking for. skills.sh or mcpservers.org for Agent Skills (both support category filtering); mcpservers.org, Smithery, or Glama for MCP servers generally; claudemarketplaces.com specifically for Claude Code. Smithery is the fastest way to sanity-check a candidate server's quality before installing, since it's the only one that scores servers rather than just listing them.
How do I get my own MCP server or skill listed?
It depends on the channel. skills.sh lists automatically once real users install your skill via npx skills add — there's no submission form. mcpservers.org, claudemarketplaces.com, skillsmp.com, and claudeskills.info require an explicit submission or PR. The Official MCP Registry needs the mcp-publisher CLI plus DNS-based domain verification, but it's the one channel that auto-feeds mirrors like PulseMCP afterward.
Do these directories all mirror each other?
No. The Official MCP Registry (registry.modelcontextprotocol.io) is the one that auto-feeds downstream mirrors like PulseMCP. The others are independent — being listed on Smithery doesn't get you listed on mcpservers.org or claudemarketplaces.com, and each requires checking and (usually) submitting separately.
Can a hosted-only MCP server get a Smithery or Glama score?
Smithery auto-indexes and scores hosted servers directly. Glama is more restrictive: its build/scoring step runs the server locally, so a purely hosted endpoint with no local npx or Docker path can't be built and therefore can't be scored, even if it shows up as listed. Shipping a small local stdio wrapper alongside a hosted server unlocks a Glama score.
Is Crawlora listed on these directories?
Yes, on most: the Official MCP Registry (net.crawlora/crawlora-mcp), Smithery (quality score 81/100), Glama, skills.sh (5 skills), and mcpservers.org. As of this piece it was confirmed absent from claudemarketplaces.com.