Back to feed
Dev.to
Dev.to
8/5/2026
Day 26/30: MCP Transport Options

Day 26/30: MCP Transport Options

Short summary

A developer debugging a LangGraph and MCP support bot discovered that the default stdio transport fails when client and server run on different machines. Switching to MCP's Streamable HTTP transport enables remote deployment by sending messages over HTTP. The post includes a code example and notes the need for retry logic (e.g., tenacity) to handle connection drops.

  • •MCP's default stdio transport breaks when client and server are on different machines
  • •Streamable HTTP transport enables remote MCP deployment over HTTP
  • •Retry mechanisms like tenacity are needed to handle connection drops in production

Generated with AI, which can make mistakes.

#ai-tools#ai-agents#open-source
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

The original headline is: "Four MCP transports: stdio, http, sse, websocket — picking the right one"
Dev.to
I Migrated My MCP Server From STDIO to Streamable HTTP. It Almost Worked.
Dev.to
Mastering Node.js Transport Layers in MCP: Stdio vs. Server-Sent Events (SSE)
Dev.to
The parts of building an MCP server that the tutorials skip
Dev.to