Remote MCP servers

Good to know

• Connect by URL

  Paste the server URL into your MCP client config. No binaries to install or update.

• Auth handled by the vendor

  Sign in once with OAuth or an API key. The AI client inherits your access scopes.

• Best for SaaS tools

  Use remote for hosted apps like Slack, Linear, or Cloudflare. Use local when you need file or process access.

Connect in 3 steps

1. 1

   Pick a server

   Tap any card above to open the vendor page and read what tools the server offers.

2. 2

   Copy the server URL

   The vendor lists the connection URL in their docs, along with any auth steps.

3. 3

   Paste it in your client

   Add the URL to your MCP client config, save the file, and restart the client.

Frequently asked

What is a remote MCP server?

A remote MCP server runs on the internet, not on your machine. You connect to it by URL. Nothing to install, nothing to keep updated.

When should I pick remote over local?

Pick remote when the tool lives in the cloud, like Slack, Linear, or Cloudflare. Pick local when the server needs to read your files or talk to apps on your machine.

Which clients support remote MCP?

Claude Desktop, Cursor, Windsurf, Cline, and Continue all work with remote servers. Most clients accept either an SSE URL or a Streamable HTTP URL.

Is my data safe with a remote server?

Remote servers run on infrastructure the vendor controls. The server only sees what your client sends. Use OAuth where possible so the server gets a scoped token instead of a long lived API key.

Do remote MCP servers cost money?

Most remote servers are free for basic use. Some vendors charge for higher rate limits or team features. The vendor page tells you the pricing.