agents-mcp
MCP (Model Context Protocol)
Use this skill to decide whether MCP is the right abstraction, configure existing servers in Claude Code or Codex, or build a narrow custom server when repeated agent workflows justify it.
Protocol revision is a lookup, not a constant. Before building or migrating a server, open the newest revision listed at modelcontextprotocol.io/specification, read its changelog and its deprecated-features registry, and record which revision your server targets. The answer decides which shapes below apply and which features are migration debt.
Breaking boundary to know: the 2026-07-28 revision redesigned the protocol relative to 2025-11-25 (changelog):
- Stateless protocol. The
initialize/notifications/initializedhandshake and theMcp-Session-Idheader were removed (SEP-2567, SEP-2575). Every request carries its protocol version and client capabilities in_meta; a mandatoryserver/discoverRPC advertises supported versions and identity. Servers needing cross-call state mint explicit handles passed as ordinary tool arguments. - Roots, Sampling, and Logging deprecated (SEP-2577): still functional, but new implementations should not adopt them. Migrate to tool-parameter directories or resource URIs, direct LLM provider API calls, and stderr or OpenTelemetry respectively.
- Server-initiated requests removed.
roots/list,sampling/createMessage, andelicitation/createwere replaced by Multi Round-Trip Requests (MRTR): the server returnsresultType: "input_required"withinputRequests, and the client retries the original request carryinginputResponses. - Transport changes. The HTTP GET endpoint and
resources/subscribe/unsubscribecollapse into onesubscriptions/listenstream; SSE resumability (Last-Event-ID) was removed, so a broken stream means re-issuing the request with a new ID.pingandlogging/setLevelwere removed. HTTP+SSE transport is formally Deprecated; use Streamable HTTP.
The deprecation clock is the planning fact. The spec has a formal feature lifecycle (Active / Deprecated / Removed) with a minimum twelve-month deprecation window (SEP-2596). Anything built on a deprecated feature has a bounded lifetime: treat it as migration debt from the start. The window is a floor, not a promised removal date; check the registry for the current state.
SDK release lines move independently of the spec. Which SDK major version targets which revision, and how long the older line gets fixes, is a lookup in the SDK repo's README (see Build a Custom Server).
Governance (a vendor-trust input, not a technical one): Anthropic donated MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025 (blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation). The maintainers keep technical authority through the SEP process. When a security review asks "who owns this protocol", cite the foundation, not Anthropic.