Tools

MCP specification 2025-11-25: async Tasks, OAuth, and extensions

The MCP anniversary brought the 2025-11-25 specification with async tasks, stronger authorization, and an extensions framework - an open example of how the protocol mat

Our clients

Clients and partners

Capital Group
FSK Group
SMLT
Tochno
Dogma
Sber City
FM Logistic
Danone
+10clients · View cases →

On the MCP anniversary (November 25, 2025), the specification was published 2025-11-25. Key changes relevant to enterprise integrations:

  • Tasks (experimental) — an abstraction for long-running operations: the client requests a task's status and result some time after it starts. This moves MCP from synchronous "call a tool, get a response" into managed long-running processes.
  • Stronger authorization — modern OAuth, client registration, and enterprise access management scenarios.
  • Extensions — a formal way to declare, discover, and configure optional server capabilities.

For AI-native integration, this means MCP servers on top of enterprise systems can be built for controlled, auditable, long-lived workflows, not just chat questions.

Which business process it improves

MCP is no longer a protocol only for synchronous calls: version 2025-11-25 covers authorization and long-running processes needed for enterprise integrations.

Discuss MCP Specification 2025-11-25: async Tasks, OAuth and…

Send via: