MCP Transport (stdio vs Streamable HTTP)
MCP runs either as a local stdio process or as a remote streamable HTTP endpoint — the choice decides auth, deployment and who can reach it.
/ quick answer
stdio transport launches the server as a local subprocess: zero network exposure, ideal for developer tooling. Streamable HTTP exposes an endpoint any remote client can dial, which requires real authentication (OAuth 2.1 with bearer tokens) and rate limiting. Remote MCP without auth is a public API over your internal systems.
/ frequently asked
What is MCP Transport (stdio vs Streamable HTTP)?
stdio transport launches the server as a local subprocess: zero network exposure, ideal for developer tooling. Streamable HTTP exposes an endpoint any remote client can dial, which requires real authentication (OAuth 2.1 with bearer tokens) and rate limiting. Remote MCP without auth is a public API over your internal systems.
What is an example of MCP Transport (stdio vs Streamable HTTP)?
A Postgres MCP server runs over stdio in Cursor locally, while the company's CRM MCP server is deployed over HTTPS with OAuth and per-user scopes.
Why does MCP Transport (stdio vs Streamable HTTP) matter?
MCP runs either as a local stdio process or as a remote streamable HTTP endpoint — the choice decides auth, deployment and who can reach it.
What should I learn after MCP Transport (stdio vs Streamable HTTP)?
Open the related workflows and prompts further down this page: they show how this idea is applied in a real task, step by step.
/ continue exploring
Related concepts
The vocabulary this page depends on.
- →MCP Server
An MCP server exposes tools, resources and prompts from one system so any MCP-compatible AI client can use them over a standard protocol.
- →MCP Client
An MCP client is the AI-side host that discovers servers, lists their tools and routes the model's calls to them.
- →AI Security
AI security protects systems where the model is an untrusted decision-maker acting on untrusted input with real tool access.
- →Prompt Injection
An attack where hostile input hijacks the LLM's instructions, causing it to leak data or misbehave.
Related workflows
Turn this into a repeatable process.
- →Audit MCP Tool Security
A checklist that catches the failure modes unique to model-driven tool calls.
- →Connect MCP to Internal Systems Without Losing Control
Give agents real access to your CRM, database and docs with least privilege.
- →Build an MCP Server for Your Own App
Expose your product's capabilities to every AI client with one server.
- →Build an MCP Server for Your Internal Data
Expose one internal data source to every AI client via the Model Context Protocol.
Related tool stacks
The tools that run it in production.
- →MCP Integration Stack
Build, deploy and secure MCP servers that real AI clients can use.
- →AI Security Stack
Least-privilege tooling, approval gates and audit trails for agentic systems.
Related prompts
Reusable prompts for this job.
- →MCP Tool Surface Design Prompt
Turns an app description into a minimal, safe MCP tool and resource surface.
- →Refactor and Security Review Prompt
Clean up a vibe-coded app and catch security gaps before launch.
- →MCP Tool Designer Prompt
Turn a plain-English capability list into a clean MCP tool schema.
- →Autonomy Boundary Prompt
Defines exactly what an agent may do alone, with approval, or never.
Related use cases
How people apply it, and what came out.
- →Sales Team Queries the CRM from Claude via MCP
One MCP server replaced three brittle chatbot integrations.
- →Consultancy Ships a Client-Wide MCP Server in 2 Weeks
A boutique AI consultancy replaces 6 bespoke Zapier flows with one MCP server.
- →Monitor Wallet Transactions
Alerting on the user's own wallet activity caught an unauthorised approval attempt and forced an approval cleanup that removed 14 standing allowances.
Comparisons & alternatives
Pick between the options.
- →MCP vs Native Function Calling
Function calling is per-app plumbing; MCP is a portable protocol so one integration serves every client.
- →Hot Wallet vs Cold Wallet
Hot wallets trade convenience for exposure; cold wallets trade friction for a signing key that never touches an internet-connected device.
- →Rabby vs OKX Web3 Wallet
Rabby is the safety-focused EVM wallet with pre-transaction simulation; OKX Web3 Wallet trades some of that depth for multi-chain breadth and built-in trading.