Remote MCP Servers: The Most Popular in 2026
Last updated 2026-10-09
Quick answer
The most prominent remote MCP servers in 2026 are GitHub, Context7, Figma, Supabase, Notion, Linear, Cloudflare, Stripe and Sentry — hosted services that AI assistants connect to over Streamable HTTP without running anything locally. There is no authoritative global ranking; this list combines ecosystem visibility, official hosted endpoints and directory data.
What 'remote MCP server' means
MCP servers come in two shapes. Local servers run on your machine and speak stdio — you install them, scope them, and your client launches them. Remote servers are hosted by the publisher (or a trusted operator) and expose a Streamable HTTP or SSE endpoint: you paste a URL, authorise, and the client connects. Nothing to install, nothing running on your laptop.
Remote is how web-first clients — ChatGPT connectors, custom agents, and increasingly Claude and Cursor — reach tools. The official MCP Registry lists transport for every server; MCPNav shows a Remote badge on every entry that speaks Streamable HTTP or SSE.
Top remote MCP servers in 2026
Who benefits most, in one line each:
- ▸GitHub MCP — repositories, issues, PRs — developers and coding agents
- ▸Context7 — current library docs — AI coding assistants
- ▸Figma MCP (official remote) — design files and UI context — frontend teams
- ▸Supabase MCP — databases and projects — full-stack developers
- ▸Notion MCP — docs and wikis — research and productivity
- ▸Linear MCP (official remote) — issues and projects — software teams
- ▸Cloudflare MCP — infrastructure operations — site and platform operators
- ▸Stripe MCP — payments and business data — finance and commerce teams
- ▸Sentry MCP — production errors — on-call engineers
- ▸Jira MCP — issues and Confluence — project teams
Local vs remote, honestly compared
Remote wins on zero-install, cross-device access and working from web clients. Local wins on data privacy (files never leave your machine), speed (no network hop) and offline use. Security differs too: a remote server holds an authorised token on a server you do not control, while a local server holds credentials on a machine you do. Neither is automatically safer — what matters is scope, and whether you trust the operator.
The ecosystem is moving remote-first: every major SaaS vendor now publishes an official hosted endpoint, and community lists such as awesome-remote-mcp-servers track hundreds more. The MCPNav directory marks transport on every listing so you can filter either way.
How to connect one
In Claude or Cursor, add a server with type 'http' (or 'sse' for older endpoints) and the publisher's MCP URL. In ChatGPT, use Settings → Connectors and paste the same URL. You will authorise through the provider's normal OAuth flow on first connect. Each server page in this directory shows the exact remote config block where supported.
The picks, one by one
The official GitHub server with hosted remote options — full repo, issue and PR surface for agents.
Best for: Coding agents that need repository context from anywhere.
Watch out: Remote tokens should be scoped read-only first.
Figma's official remote endpoint — the reference example of a vendor-hosted MCP server.
Best for: Design-to-code context with zero local install.
Watch out: Requires an eligible Figma plan.
Linear's official remote server over Streamable HTTP — issues, projects and workflows.
Best for: Software teams asking status questions in chat.
Watch out: Plan dependent; authorise with read scopes first.
Official Cloudflare server for zones, workers and infrastructure operations.
Best for: Operators managing sites and edge services.
Watch out: Use narrowly-scoped API tokens.
Hosted Stripe server with confirmation steps before consequential actions.
Best for: Payments data and operations grounded in live accounts.
Watch out: Restricted keys + test mode until confident.
Official Sentry server over hosted endpoints — errors, traces and releases.
Best for: On-call debugging with real telemetry.
Watch out: Read-only by default; keep it that way.
Official Notion server; remote options let web clients read wikis and databases.
Best for: Knowledge-base answers inside ChatGPT and other web agents.
Watch out: Audit integration scopes.
Supabase project and database management; hosted paths available alongside local install.
Best for: Full-stack developers moving fast on Supabase backends.
Watch out: Dev projects first.
Hosted Jira endpoint (Streamable HTTP/SSE) for issues and project context.
Best for: Project teams living in tickets.
Watch out: Verify the hosting operator before granting tokens.
Smithery's hosted Notion server — a community-operated remote alternative to self-hosting.
Best for: Trying Notion MCP without any local setup.
Watch out: Third-party operator — understand who can see your tokens.
Frequently asked questions
What transport does a remote MCP server use?＋
Streamable HTTP is the current standard; older servers use Server-Sent Events (SSE). Both are network transports — the client connects to a URL instead of launching a local process.
Are remote MCP servers safe?＋
They remove local install risk but add operator trust: the host holds authorised tokens to your systems. Prefer official publisher endpoints, scope credentials tightly, and revoke unused servers. A listing in any directory is discovery, not a security audit.
How many remote MCP servers exist?＋
Tens of thousands are listed across directories and the official registry, but the number of production-grade, publisher-operated endpoints is far smaller — the curated list on this page is a realistic shortlist.
Can I self-host a remote MCP server?＋
Yes — any stdio server can be wrapped with an HTTP bridge and hosted, and projects like mcp-remote exist for exactly that. Self-hosting keeps credentials in infrastructure you control, at the cost of running it.