Best MCP Servers and Tool Platforms in 2026
Quick answer
"MCP server" covers three different products wearing the same name, so pick by job. To find servers, start with a registry: Smithery
Visit: Smithery(now a free directory powered by Arcade, after its hosted services shut down in October 2026) or Glama
Visit: Glama, which pairs its directory with a hosted gateway. Both are free to start. To give your agent authenticated access to business apps (its Gmail, your users' Slack), use a tool platform built for that: Composio
Visit: Composio, Arcade AI
Visit: Arcade AI, Pipedream Connect
Visit: Pipedream Connect, or Zapier MCP
Visit: Zapier MCP, which differ mainly in how many apps they cover and how they handle user authorization. There is no single "best MCP server" — there are thousands of individual servers, and the platforms below are how you reach them without running each one yourself. Pricing here is what each platform publishes; where a pricing page rendered incompletely during verification, the dataset says so instead of inventing numbers.
First, sort the category
- Registries/directories list servers and their metadata. Glama and Smithery both do this.
- Hosted gateways actually run servers for you and route calls, so your agent needs one connection instead of fifty installs. Glama's gateway and Composio's managed MCP endpoints do this. (Smithery used to — it shut down its hosted services in October 2026 and is a directory again, which is why this distinction matters.)
- Tool platforms are integration businesses (thousands of app connectors, OAuth handling, per-user authorization) that now expose everything over MCP. Composio, Arcade, Pipedream Connect, and Zapier MCP live here.
An agent stack often uses two layers: a registry to discover, and a tool platform for the authenticated apps. Paying for both is normal; paying twice for the same layer is the mistake.
The six platforms compared
| Platform | Type | Entry price (published) | Free tier | What it covers |
|---|---|---|---|---|
| Smithery | Registry (directory only) | No paid tier — free | Yes — directory is free | Thousands of listed MCP servers |
| Composio | Tool platform | $29/mo (first paid tier) | Yes — generous free tier | 1,500+ apps with managed OAuth |
| Glama | Directory + gateway | Tiered gateway pricing (site) | Yes — directory/inspector free | Listed MCP servers, inspection |
| Arcade AI | Tool platform | Tiered (free dev tier) | Yes — developer tier | Curated app toolkits with per-user auth |
| Pipedream Connect | Tool platform | $99/mo billed annually (Startup) | Yes (free development plan) | 3,000+ connectors, 10,000+ tools |
| Zapier MCP | Tool platform | Included in Zapier plans | Yes — free plan, task-metered | 9,000+ apps, 30,000+ actions |
Prices verified 2026-11-03; exact tier allowances for Smithery, Composio, Glama, and Arcade should be confirmed on their live pricing pages — see the notes in the open dataset.
Smithery — the registry with a hosted front door
Smithery began as the place to browse MCP servers and grew a hosted gateway — then reversed course: on October 31, 2026 it shut down its connection services (API, Connect, Toolbox), refunded recent charges, cancelled subscriptions, and became a public, non-proxied registry powered by Arcade.dev. Listings now point to each vendor's own MCP URL. That history is itself the lesson of this category: hosted convenience can be discontinued, while a directory of direct endpoints cannot strand your agent the same way. Use Smithery today for what it is — the best-known free index of what exists — and keep your integrations pointed at vendors' own servers where you can.
Best for: discovery plus hosted calls in one place; solo builders and prototypes going live.
Glama — directory, inspector, and gateway
Glama's public face is its directory and its inspector — the tool people use to look inside an MCP server and see its tools, prompts, and resources before trusting it. It also offers a hosted gateway on tiered pricing, with the directory and inspector free. If your workflow is evaluating servers (yours or others'), Glama is the workbench; if you mainly need calls routed, compare its gateway tiers against Smithery's on your expected call volume.
Best for: evaluating and debugging MCP servers; teams standardizing which servers are approved.
Composio — authenticated app access for agents
Composio solves the unglamorous problem that decides whether agent products ship: OAuth. It manages authentication for 1,500+ apps and exposes them as tools and per-app MCP servers, with published rate limits (2,000 requests/minute on the free Hobby tier, 10,000 on Pro) and a first paid tier at $29/month that includes $29 in monthly credits. Its free tier is unusually deep — a headline 100,000 tool calls/month, with 20,000 free calls on Composio-managed apps. Composio also runs a public partner program via Dub ($5 per activated user plus bounties), one of the few in this category. Instead of your agent holding raw user tokens, Composio brokers the connection — the architecture your users' security review will ask about.
Best for: agent products where end users connect their own accounts.
Arcade AI — curated toolkits, per-user authorization
Arcade takes the curated end of the spectrum: hand-built toolkits for apps like Gmail, Slack, and GitHub, designed around per-user authorization so an agent acts as the user, with the user's permissions, and nothing broader. It offers a free developer tier and tiered paid pricing on its site. The catalogue is smaller than the everything-platforms by design — the bet is depth and safety over breadth.
Best for: production agents acting inside workplace apps, where permission scoping matters more than app count.
Pipedream Connect — 10,000 tools from an automation platform
Pipedream Connect exposes Pipedream's integration library — 3,000+ connectors, 10,000+ pre-built tools — through its Connect API and an official MCP server, on Pipedream's current pricing: a free development plan, then Startup at $99/month billed annually ($150 monthly) with 10,000 usage credits and 100 external users included. Because the same account also runs event-driven workflows, Connect suits builders who want agent tool calls and deterministic automation in one system rather than two vendors.
Best for: developer-heavy stacks mixing agent calls with classic workflow automation.
Zapier MCP — the biggest app library, metered in tasks
Zapier MCP puts Zapier's 9,000+ apps and 30,000+ actions behind one hosted MCP endpoint, included from Zapier's free plan upward — with the meter to watch: MCP tool calls consume Zapier tasks (published at 2 tasks per MCP call). At agent scale, that math decides the bill, so model your expected calls against Zapier's task pricing (Professional from $19.99/month billed annually, 750 tasks) before falling in love with the library size.
Best for: non-developer teams and agents that need an obscure app nobody else integrates.
Building your own vs buying a platform
Running individual open-source MCP servers yourself costs $0 in platform fees and real hours in hosting, secrets management, updates, and debugging. The honest rule from this dataset: below a handful of servers, self-host; the moment your agent needs authenticated access to other people's accounts, buy a tool platform — OAuth done wrong is a security incident, not a savings. And whatever you choose, keep the dataset habit: record each server's owner, permissions, and last-reviewed date, because MCP servers are software supply chain, not furniture.
What "best" means in a directory of thousands
A directory cannot rank thousands of servers the way a review ranks six products, and any site that claims to has not used them. What a builder actually needs from this layer is curation signals: who maintains the server (the vendor, or a stranger?), when it last changed, what permissions it asks for, and whether a platform has reviewed it. The six platforms above are the curation layers — they differ in how much of that vetting they do for you. Smithery and Glama lean open: broad listings, community energy, inspection tools to check things yourself. Composio and Arcade lean closed: fewer, vendor-grade integrations with authorization handled as a product feature. Neither posture is morally better; they fit different risk profiles. A hobby agent reading public data can live happily in the open end. An agent that can send email as your user belongs in the closed end, where every tool's scope was somebody's deliberate decision.
One more practical filter: prefer servers and platforms that publish changelogs and version their tools. An agent's prompts and plans quietly depend on tool names and parameters, so a server that renames tools without notice breaks production agents the way a silent API change breaks apps — except the agent may not even error loudly; it may just start doing a slightly different job. The platforms that treat MCP as infrastructure (registries with versioning, gateways with stable endpoints) are betting their business on not doing that to you, and that alignment is worth more than a marginally longer tool list.
FAQ
What is an MCP server, in one sentence?
A small program that exposes a tool's capabilities (search, send email, query a database) to AI agents through the Model Context Protocol, so any MCP-compatible agent can use it without a custom integration.
Which platform has the most tools?
By published counts, Zapier MCP advertises 30,000+ actions across 9,000+ apps, and Pipedream Connect 10,000+ tools across 3,000+ connectors. Registry size is a different number: Smithery and Glama list thousands of third-party servers of varying quality.
Are MCP platforms free?
All six here have a free way in: Smithery and Composio free tiers, Glama's free directory/inspector, Arcade's developer tier, and Pipedream/Zapier free plans (Zapier's is task-metered). Production volume is where they diverge — compare meters, not stickers.
Do I need a platform, or can I run servers myself?
You can run open-source servers yourself for free. Platforms earn their fee when you need hosting at scale or authenticated access to users' app accounts. Most production stacks end up hybrid: a few self-hosted servers plus one tool platform.
Is MCP safe to give an agent access to my apps?
MCP itself is a protocol; safety comes from scoping. Prefer platforms with per-user authorization and least-privilege tool access (Arcade and Composio are built around this), review each server like a dependency, and never give an agent a broader token than the task needs.