MCP News

This feed includes only recent releases, roughly from the last 12 months, not the full historical archive. That is why a long-established product may have only a few news items.

5 news

MCP
Roadmap updated: agent identity, unified HTTP transport, SDK experience

The March roadmap has been expanded from 4 to 5 priorities. Agent identity and SDK developer experience have been added as a separate item; messaging primitives (Tasks, subscriptions/listen, progress) are being extended to server-initiated events via webhooks/channels instead of polling, and the local stdio transport is proposed to be unified with remote HTTP. The release follows the 2026-07-28 specification, the largest revision since the protocol launched.

MCP's move from polling to server-initiated events via webhooks/channels is a pattern that message brokers like Kafka addressed with push subscriptions years ago. Apache Kafka →Agent identity as a separate MCP priority for 2026 is not new - in enterprise LLM-gateway products, agent access control is already standard functionality. LLM & Security Gateway →
MCP
Specification dated July 28, 2026: the protocol becomes stateless

The largest revision since launch. Protocol-level sessions (Mcp-Session-Id), the initialize/notifications/initialized handshake, ping, and SSE resumability were removed; cross-call state is now carried in explicit handle arguments. server/discover was added, the MRTR pattern replaced server-initiated requests, and resultType became mandatory. Roots, Sampling, Logging, and the HTTP+SSE transport are marked Deprecated (at least 12 months before removal), and Dynamic Client Registration gives way to Client ID Metadata Documents.

MCP gives up persistent sessions and subscriptions for scalability over plain HTTP, while Kafka solves the same horizontal scaling problem through partitioning, not through protocol statelessness Apache Kafka →
MCP
MCP Apps: interactive UI inside chat, the first official extension

MCP server tools can return interactive HTML components, such as dashboards, forms, and multi-step wizards, rendered in an iframe sandbox directly in the chat with the model. The first extension to move from an SEP proposal (November 21, 2025) to official production-ready status.

MCP Apps directly builds on the OpenAI Apps SDK pattern and the earlier MCP-UI project OpenAI →n8n has provided a visual UI over workflow nodes for years; MCP Apps brings a comparable interactive UI into the tool-calling protocol itself for the first time n8n →
MCP
Specification dated November 25, 2025: Tasks, simplified authorization, sampling with tool calling

Protocol anniversary. Experimental task-based workflows were added (SEP-1686, statuses working/input_required/completed/failed/cancelled), Dynamic Client Registration was replaced by URL-based Client ID Metadata Documents (SEP-991), URL mode elicitation for OAuth was added without passing credentials through the client (SEP-1036), tool calling inside sampling requests was added (SEP-1577), and the tool name format was standardized (SEP-986).

MCP
MCP Apps (SEP-1865): proposed extension for interactive UI

Standardization of UI resource declarations, their binding to tools, and bidirectional messaging between embedded UI and the host. Initially limited to text/html in a sandboxed iframe. One of the community's most requested features, building on earlier MCP-UI work and the OpenAI Apps SDK.

Discuss MCP News

Enter your email or phone number so we can get back to you.

Send via: