MCP specification 2025-11-25 at a glance
The Model Context Protocol published a backward-compatible revision that adds experimental tasks, URL-mode elicitation, tool calling inside sampling, and simpler OAuth client registration.
What changed with MCP specification 2025-11-25
The 2025-11-25 revision of the Model Context Protocol (MCP) introduced experimental tasks, which let a client poll a long-running request and fetch its result later. It also added URL-mode elicitation, so a server can send a person to a browser flow such as an OAuth sign-in without the credentials passing through the AI client.
Other changes include tool definitions inside sampling requests, OAuth Client ID Metadata Documents as the recommended way to register clients, OpenID Connect discovery, icons for tools and resources, and guidance on tool names. The project says existing implementations keep working.
Why MCP specification 2025-11-25 matters for businesses
The release post also reported that the MCP Registry held close to 2,000 entries. For businesses connecting AI assistants to a CRM or internal systems, the auth and long-running task changes address two common integration pain points.
Sources for this story
- One Year of MCP: November 2025 Spec Release (opens in a new tab)Official
Model Context Protocol Blog · blog.modelcontextprotocol.io
- Key Changes (2025-11-25) (opens in a new tab)Official
modelcontextprotocol.io · modelcontextprotocol.io
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #mcp
- #model-context-protocol
- #interoperability
- #standards
- #oauth