MCP App StoreLe meilleur de l'écosystème IA et MCP, sélectionné chaque jour.
Sources
The Model Context Protocol (MCP) has released a new specification RC featuring a stateless protocol core, an Extensions framework, and a formal deprecation policy. This update introduces critical groundwork for MCP Apps and enhanced authorization hardening.
The Model Context Protocol project added a new Lead Maintainer and expanded its Core Maintainer group as the open-source project scales. This formalizes governance and should speed reviews, releases, and community contributions—important for developers and integrators building on MCP. Expect clearer ownership of key repos and faster turnaround on contributions.
The MCP team reviews the state of tool annotations — the metadata that tells clients whether a tool is read-only, destructive, or reaches outside its local environment. Five community SEPs have proposed new annotations, and this post provides a clear framework for evaluating them: what annotations can actually communicate, where the limits are, and how clients should treat them as hints rather than guarantees. Essential reading for MCP server developers.
The MCP team explains the extensions system — how developers can layer new capabilities (custom auth, richer UI, domain-specific conventions) on top of the core protocol without modifying the spec itself. Covers the design philosophy, current community patterns, and how extensions stay compatible across client implementations. The guide for any developer hitting the limits of baseline MCP.
The official MCP roadmap for 2026 covers four focus areas: transport scalability for enterprise deployments, agent-to-agent communication primitives, governance maturation through the SEP process, and enterprise readiness features. The post also explains how SEPs get prioritised and how the community can contribute. The definitive reference for where MCP is heading this year.
MCP Apps launched as the first official MCP extension, enabling tools to return interactive UI components — dashboards, forms, visualisations, multi-step workflows — that render directly in the conversation. Built as an open standard in collaboration with OpenAI and the MCP-UI community. A landmark moment for the MCP ecosystem that expands what MCP servers can deliver beyond plain text.
The MCP Core Maintainer team announces changes for 2026: Inna Harper and Basil Hosmer are stepping back, with new maintainers joining to keep the project moving. Also covers what's ahead for MCP governance as the protocol moves under the Agentic AI Foundation. Good context for anyone tracking MCP's organisational trajectory.
The MCP Transport Working Group outlines plans to evolve beyond Streamable HTTP for enterprise-scale remote deployments — addressing the stateful connection bottleneck that makes load balancing and managed services difficult. Proposes a direction that preserves backward compatibility while enabling stateless, horizontally-scalable MCP server deployments. Critical reading for teams deploying MCP at scale.
Anthropic donated MCP to the newly formed Agentic AI Foundation — a directed fund under the Linux Foundation — ensuring vendor-neutral governance for the protocol's future. MCP becomes a founding project of the foundation alongside other agentic AI standards. A major governance milestone that signals MCP's transition from an Anthropic project to a true open standard.
MCP Specification Enhancement Proposals (SEPs) are moving from GitHub Issues to pull requests against the `seps/` directory, making proposals easier to review, version, and track. The post explains the rationale and what changes for contributors submitting new SEPs. Relevant for anyone participating in MCP spec development.
MCP marks its first anniversary with a retrospective on the year and a full breakdown of the November 2025 spec release — the most significant update since launch. Covers new primitives, transport changes, and the governance evolution that brought MCP to production at companies large and small. The canonical reference for what changed in the 2025-11-25 spec version.
The original proposal for MCP Apps (SEP-1865) — introducing a standardised extension for interactive UIs in MCP, developed jointly with the MCP-UI team, OpenAI, and Anthropic. Explains the motivation, design decisions, and how the extension fits within the broader MCP extension model. The precursor post to the January 2026 official launch.
The MCP Bundle format (.mcpb) is now an official part of the MCP project — a portable package format for local MCP servers that enables one-click installation across any compatible client. Addresses the friction of manual JSON config setup and makes MCP server distribution more like installing a regular app.
An underused MCP protocol feature gets a spotlight: server instructions let you give the LLM a structured user manual for your server — explaining what tools do, when to use them, and how to combine them effectively. The post shows how well-written server instructions dramatically improve tool call accuracy without any prompt engineering on the client side.
The MCP team shares timelines and priorities for the next spec version — covering what features are slated, what's been deferred, and how the community can influence what gets included. Useful context for developers planning integrations or building on features that depend on upcoming spec changes.
The MCP Registry launched in preview — an open catalog and API for discovering publicly available MCP servers. Provides a standardised way for clients to discover servers, check metadata, and verify compatibility without relying on community-maintained lists. The infrastructure layer that makes the MCP ecosystem more navigable as it grows.
The official PHP SDK for MCP is now generally available, built in collaboration with the PHP Foundation and Symfony. Brings idiomatic PHP support to MCP server development, opening the protocol to the large PHP developer community. Part of MCP's push to have official SDKs across all major languages.
A deep dive into how MCP handles OAuth 2.1 client registration — the mechanism that lets MCP clients and servers establish trust without a pre-existing relationship. Explains the two core challenges (dynamic registration, trust bootstrapping) and the design choices made to solve them in a way that scales to the open MCP ecosystem. Essential for developers building MCP clients or auth-enabled servers.
A practical tutorial on using MCP prompts and resource templates to build workflow automation — walking through a meal planning example that demonstrates how prompts can chain resources and tools into reusable, composable workflows. Prompts are an underused MCP primitive and this is one of the clearest guides to their practical value.
The MCP project introduced its formal governance model: Specification Enhancement Proposals (SEPs), a defined maintainer structure, and a community-driven process for evolving the protocol. This post marked MCP's transition from an Anthropic-led project to a community-governed open standard, laying the groundwork for the later Linux Foundation donation.