Best Remote MCP Servers in 2026: 10 Hosted Servers Compared

The best remote MCP servers are the ones run by the companies whose data they reach: GitHub, Notion, Atlassian, Linear, Stripe, HubSpot, Asana, Zapier, Cloudflare and Box all host official servers. You connect with a URL and sign in with OAuth, so there is nothing to install and no long-lived key to paste.

A remote MCP server runs on the vendor's infrastructure instead of your computer. Your AI app, such as Claude, ChatGPT or Cursor, talks to it over the internet using the Streamable HTTP transport. The vendor handles updates and uptime, and you control access through the same sign-in and permissions you already use.

We checked each server below against the vendor's own docs and pricing pages on 28 October 2026. eSEOspace did not install or test these servers for this list.

How we chose

We included a server only if it passed these tests:

1. Remote and official. The product's own company hosts it at a public URL.
2. Live and documented. We could open its setup docs on 28 October 2026.
3. Real sign-in. The docs describe OAuth or another per-user sign-in, not just a shared key.
4. Clear cost. The vendor states pricing or plan rules, or links them from an official pricing page.

We spread the list across departments: code, docs, tickets, payments, CRM, projects, automation, infrastructure and files. For a developer-only view, see our list of MCP servers for developers. For local servers you run yourself, see open-source MCP servers.

Comparison table

1. GitHub MCP Server: code, issues and pull requests

What it is. The GitHub MCP Server has a remote endpoint at https://api.githubcopilot.com/mcp/ that accepts OAuth or a personal access token. You choose which toolsets load, and a --read-only flag skips every write tool. The same project also ships a local version, so you can move between the two.

Best for: Any team whose code lives on GitHub.

Pricing: GitHub's docs say it is "available to all GitHub users regardless of plan type." Tools tied to paid features need that same paid license.

Pros:

• Free to use, with an MIT-licensed codebase you can read.
• Toolsets keep the tool list short.
• Read-only mode takes priority over requested write tools.

Cons:

• Copilot Business and Enterprise orgs must enable the "MCP servers in Copilot" policy first.
• Loading all toolsets gives the AI a very long tool list.

Checked against: GitHub MCP Server README on 28 October 2026. Full profile: GitHub MCP server.

2. Notion MCP: docs, wikis and databases

What it is. Notion MCP is a hosted server at https://mcp.notion.com/mcp, with an SSE fallback for older clients. It uses OAuth by default. On Business and Enterprise, a workspace owner can create MCP tokens for clients that cannot open a browser.

Best for: Teams whose plans, notes and knowledge base live in Notion.

Pricing: Notion's docs say "Notion MCP works on every plan." Some tools and higher request limits need Business or Enterprise.

Pros:

• No plan gate for basic use.
• Enterprise workspaces can use enterprise-managed authorization through SAML SSO.
• Clear docs on which tools need which plan.

Cons:

• Workspace guests cannot connect, only members.
• Limiting which clients members can use "needs the Enterprise plan."

Checked against: Notion MCP docs on 28 October 2026. Full profile: Notion MCP server.

3. Atlassian Rovo MCP Server: Jira, Confluence and more

What it is. The Atlassian Rovo MCP Server runs at https://mcp.atlassian.com/v2/mcp. It covers Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals and Loom. It is "powered by secure OAuth 2.1 authorization," so actions respect each user's existing permissions, with API tokens as an option.

Best for: Companies that run work and documentation on Atlassian Cloud.

Pricing: Atlassian's Rovo pricing page says "Installing and connecting to Rovo MCP Server" is free. Enriched Teamwork Graph calls consume Rovo credits, most costing 1 to 10 credits. Credits beyond your plan's allowance cost $0.01 each.

Pros:

• One server for most Atlassian Cloud products.
• Uses existing Atlassian permissions rather than a new role model.
• Admins can turn off extra credit usage.

Cons:

• Credit costs vary by call, which makes budgeting harder.
• Data Center customers need a Cloud plan for full Rovo features.

Checked against: Atlassian's MCP getting started guide and Rovo pricing on 28 October 2026. Full profile: Atlassian MCP server.

4. Linear MCP: issues with a read-only endpoint

What it is. Linear MCP runs at https://mcp.linear.app/mcp over Streamable HTTP. It uses OAuth 2.1 with dynamic client registration, or a bearer token or API key. A separate /mcp/readonly endpoint "only ever exposes read tools."

Best for: Product and engineering teams that track work in Linear.

Pricing: Linear's MCP docs state no plan requirement or MCP price.

Pros:

• A dedicated read-only URL is easy to hand to a new user.
• Read-only access is also possible through the read OAuth scope.
• Okta-managed sign-in is supported once SAML is set up.

Cons:

• The SSE endpoint is deprecated, so older clients need an update.
• No published pricing statement to point a finance team at.

Checked against: Linear MCP docs on 28 October 2026. Full profile: Linear MCP server.

5. Stripe MCP: payments with human approval

What it is. The Stripe MCP server lives at https://mcp.stripe.com. It signs in with OAuth or an agent API key. Stripe "requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments."

Stripe's docs also say that from December 2026, the server stops accepting full-access secret keys and restricted keys without the Agent tag. Migrate by 30 November 2026.

Best for: Businesses that bill or take payments through Stripe.

Pricing: Stripe's MCP docs list no separate MCP price.

Pros:

• Approval links for refunds and payouts stop silent money movement.
• Admins can enable or disable MCP for the team, separately for live mode and sandboxes.
• OAuth sessions can be revoked per user from the Dashboard.

Cons:

• The key-auth change on 30 November 2026 means existing setups may break.
• Some tools, such as Treasury actions, are still in public preview.

Checked against: Stripe MCP docs on 28 October 2026. Full profile: Stripe MCP server.

6. HubSpot MCP: CRM records and marketing content

What it is. The HubSpot MCP server runs at https://mcp.hubspot.com. It uses OAuth, and "PKCE is required." It can read and write CRM records and activities, and create landing pages, blog posts and marketing email drafts. Actions respect the installing user's HubSpot permissions.

Best for: Sales and marketing teams that live in HubSpot.

Pricing: HubSpot's docs give no MCP price. Some tools need paid tiers, such as AEO tools on Marketing Hub Professional or Enterprise.

Pros:

• Wide read and write coverage across CRM and content.
• If Sensitive Data is on, activity and conversation data is blocked from MCP.
• Uses existing user permissions.

Cons:

• Revenue objects and quotes are still marked beta.
• Some content tools only work in Claude, ChatGPT and Gemini.

Checked against: HubSpot MCP integration guide on 28 October 2026. Full profile: HubSpot MCP server.

7. Asana MCP: tasks and projects

What it is. The Asana MCP V2 server is at https://mcp.asana.com/v2/mcp. It needs OAuth and a client that supports Streamable HTTP. The old beta URL at /sse is deprecated, with a listed shutdown date of 05/11/2026.

Best for: Teams that plan and assign work in Asana.

Pricing: Asana's MCP docs make no pricing statement.

Pros:

• Current V2 server with standard OAuth.
• Enterprise+ admins can allow or block MCP clients one by one.
• Clear deprecation date for the old server.

Cons:

• Clients still on the beta URL lose access at the listed shutdown date.
• Other tiers must contact support to block the beta app.

Checked against: Asana MCP server docs on 28 October 2026. Full profile: Asana MCP server.

8. Zapier MCP: thousands of apps behind one server

What it is. Zapier MCP is "the Model Context Protocol interface to Zapier." It gives an AI access to "9,000+ apps and 40,000+ actions." Zapier "handles OAuth, credentials, and rate limiting," and most clients sign in with OAuth.

Best for: Small teams that want AI actions in apps without their own MCP server.

Pricing: "Each successful call uses two tasks from your Zapier plan, and failed calls do not count." Zapier's pricing page lists MCP on Free (100 tasks a month), Pro (from $19.99/month billed annually), Team (from $69/month billed annually) and Enterprise (custom).

Pros:

• Reaches apps that have no official MCP server.
• You choose which actions the AI can use.
• Available on the free plan.

Cons:

• Two tasks per call can use up a small plan quickly.
• Sharing a server with teammates needs Team or Enterprise.

Checked against: Zapier MCP docs and Zapier pricing on 28 October 2026. Full profile: Zapier MCP server.

9. Cloudflare MCP: the whole Cloudflare API in two tools

What it is. Cloudflare's API MCP server at https://mcp.cloudflare.com/mcp covers "over 2,500 endpoints across DNS, Workers, R2, Zero Trust, and every other product." It uses a Code Mode pattern with search() and execute() tools. Cloudflare says this uses about 1,000 tokens, against roughly 1,170,000 for full schemas.

Best for: Teams that manage DNS, security or apps on Cloudflare.

Pricing: Cloudflare's docs make no MCP pricing statement.

Pros:

• OAuth sign-in lets you pick which permissions to grant.
• API tokens work for CI and automation.
• Narrow product servers exist for docs, containers and browser runs.

Cons:

• Broad API reach means a write-capable token can change live DNS and security settings.
• No pricing statement on the docs page.

Checked against: Cloudflare MCP servers docs on 28 October 2026. Full profile: Cloudflare MCP server.

10. Box MCP: files with permission-aware access

What it is. Box runs a "hosted Model Context Protocol (MCP) server at https://mcp.box.com" that "lets AI agents search and use Box files over OAuth." Box's docs say MCP does not bypass Box permissions. Custom clients need OAuth credentials created by an admin.

Best for: Companies that store contracts and documents in Box.

Pricing: Box's MCP docs did not state a price or plan list when we checked.

Pros:

• "An admin enables MCP in the Box Admin Console," so rollout is controlled.
• Respects existing Box permissions.
• No server to run.

Cons:

• No pricing or plan details on the docs page.
• The docs do not name the transport.

Checked against: Box MCP server docs on 28 October 2026. Full profile: Box MCP server.

Remote or local: how to decide

Pick a remote server when the vendor offers one, you want OAuth instead of stored keys, and the data already lives in that vendor's cloud. Pick a local server when the data sits on your machine or network, you need to read the code, or you want nothing to leave your environment. Our lesson on remote vs local servers covers the trade-offs, and the Streamable HTTP page explains the transport these servers use.

Before you connect any of them, turn on tool approvals in your client and start with read-only access where it exists. Our MCP security hub has checklists, and the best-of collection lists more category picks.

Next step

Not sure which servers your team should connect first, or how to lock them down? Our MCP readiness audit maps your tools to the official servers that exist and the permissions each one needs.

Frequently asked questions