Protocol Deep Dives Articles
12 articles

MCP now uses round-trips, not streams, for user input
The July 28 spec deprecated elicitation and sampling. Multi Round-Trip Requests (SEP-2322) replace both with a stateless pattern: the server returns InputRequiredResult, the client collects input, the client re-submits. Here's how to migrate.

MCP SSE Is Deprecated. Here's How to Migrate
SSE transport is being deprecated across major MCP platforms in 2026. Here's a practical migration guide from HTTP+SSE to Streamable HTTP, with TypeScript examples and a phased rollout strategy.

MCP tasks: how async tool calls fix your agent's timeout problem
The November 2025 MCP spec introduced Tasks: a call-now, fetch-later primitive that lets agents kick off slow operations without blocking. Here's how it works and how to build with it.

What the July 28 MCP spec means for your stateful agents
The July 28 MCP spec is the largest protocol revision since launch. Sessions are removed. Stateless request handling replaces the initialization handshake. Here's what breaks and how to fix it before the deadline.

How to Migrate Your MCP Server to Stateless Mode
The MCP 2026 release candidate makes stateless the recommended default. Your MCP server can now scale behind any load balancer without sticky routing. Here's how to migrate and use the new Tasks extension for async work.

Four protocols that power every AI agent
MCP handles tools, A2A handles agent delegation, ACP routes across enterprise frameworks, and ANP crosses org boundaries. Here's how the four protocols divide the work and when each belongs in your stack.

MCP's 2026 spec changes what your tools can do
The MCP spec RC is out with Extensions, Tasks, MCP Apps, and OAuth hardening. Here's what changes for AI agent builders before the July 28 final.

How to Use MCP Sampling, Roots, and Elicitation in AI Agents
Most MCP tutorials cover only server-side features: tools, resources, prompts. The three client capabilities (Sampling, Roots, Elicitation) unlock human-in-the-loop patterns that server tools alone can't. Here's how to use them.

Build the MCP + A2A agent protocol stack from scratch
Wire an MCP server to an A2A agent that delegates tasks and calls tools. TypeScript and Python examples, Streamable HTTP transport, Agent Cards, and auth.

MCP vs A2A: Tools Protocol, Agents Protocol, and Why You Need Both
MCP connects agents to tools. A2A connects agents to each other. Most developers confuse them. This guide breaks down both protocols with architecture diagrams, real code, and a decision framework for production systems.

Why Browser Agents Waste 89% of Their Tokens
Browser agents burn 1,500-2,000 tokens per screenshot. Chrome 146's navigator.modelContext API lets websites expose structured tools instead, cutting token usage by 89% and raising task accuracy to 98%. Here's how WebMCP works.

The Three Protocols Every AI Agent Will Speak
The AI agent protocol stack has three layers: MCP for tools, A2A for agent-to-agent communication, and WebMCP for browser interaction. A practitioner's guide to how they work together in production.
MCP changelog and dev notes
Short, occasional updates on the MCP spec, new Protobox features, and patterns we've seen in production. No marketing fluff.