Agentic AI Notebook
0Why MCP1MCP Architecture2MCP Client3MCP Server4Resources5Tools6Prompts7Sampling8Roots9Elicitation10Capability Negotiation11Progress & Cancellation12Tasks & Long-Running Ops13Local MCP14Remote MCP15Streamable HTTP16Authentication17OAuth 2.1 & Scopes18Transport19MCP Security20Tool Poisoning21Third-Party MCP Servers22Build MCP Server23Build MCP Client24Integrate MCP with Agent
Model Context Protocol
Phase 8Module 15 of 25

Remote MCP

A local Slack server on every laptop does not scale. Remote MCP is the shared, updated, audited copy.

Local MCP is desktop software. Remote MCP is the same app in the cloud — same buttons, hosted for the team.

Visual Workflows

Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.

Overview

100%
Loading diagram...

Scroll inside the frame to explore · use + / − to zoom up to 200%

100%
Loading diagram...

Scroll inside the frame to explore · use + / − to zoom up to 200%

Client config shape

100%
Loading diagram...

Scroll inside the frame to explore · use + / − to zoom up to 200%

URL + auth header. No child process on the laptop.

Key Takeaways

  • 1.Remote MCP runs on a URL and talks over Streamable HTTP (or SSE) Teams share one server — CRM, wiki, Slack — instead of 40 local copies.
  • 2.You must add auth, TLS, and rate limits because it is on the network. Clients store a URL plus headers in mcp.json instead of a command.
  • 3.The 2025+ spec prefers Streamable HTTP. Older SSE setups still exist.
  • 4.Session reconnect and idle timeouts are your problem now — local stdio did not have them.

Learn elsewhere

  • →OAuth details — Authentication
  • →stdio vs HTTP comparison — Transport

Real Example

Scenario

The company deploys a Slack MCP server on Cloudflare. Every engineer’s Cursor points at the same URL with their own OAuth token.

What you would do

In Model Context Protocol, apply Remote MCP to this scenario: The company deploys a Slack MCP server on Cloudflare. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.

Commands

Commands to Remember

  • Remote = URL, not a spawned command
  • Streamable HTTP is the current transport
  • Auth is required on the public internet
  • Local still wins for private files

Cheat Sheet

Quick recap

quick ref
  • •Remote MCP = shared HTTP server
  • •Auth + TLS + rate limits
  • •Update once for the whole team
  • •Do not remote your .env files

Common Mistakes

  • ✕Exposing a remote server with no auth
  • ✕Putting local secrets behind a public URL
  • ✕Forgetting timeouts so a hung tool blocks the agent