Skip to content

Pick your style: Denkbaar

Book a conversation

Articles

History

MCP gains agreements for tasks and access

·

The November 2025 specification extended the protocol for connections with agents.

Two colleagues examine connections between a laptop, data and tools.
Tasks and access are part of configuring a connection. Illustration: Denkbaar.

On 25 November 2025, a new specification of the Model Context Protocol, or MCP, was published. The date coincided with the protocol’s first anniversary. The announcement names tasks and new access arrangements as key points. MCP describes how an assistant connects to tools and data. The update developed those agreements further. Source. A connection between a laptop and data has a gate and separate status blocks.

This mattered for applications made from several components. A shared agreement can describe how components work together, but a business must still decide which actions are permitted. The attention to tasks and access made that setup an explicit part of discussions about connections. Hands check cables beside a source folder, a closed gate and a task card.

For a small or medium-sized business, a concrete question for the builder is useful: what information does this connection read, and what can it change? Ask to see that in one test task. Agree how to establish that the task has finished and what happens if a component stops. Use public test information. Also ask which version of the agreements the components support. Choose a connection based on its verified operation in your application. The protocol name alone does not establish whether all the required parts are properly configured.

Sources

  1. MCP specification 2025-11-25 (one year of MCP)

Topics: protocolhistory