3.3 KiB
2026-01-13 Agents WG
Originally published as https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2081
Date: January 13, 2026 Attendees: Luca Chang, Peter Alexander, Shaun Smith, Jamu Kakars, Michael Milstead, Vinay Ramesh, Lachlan Heywood, @thoorp
Discussion
Immediate Plans
SEP-1938 has been raised to the Core Maintainers for review but has not yet been discussed by them.
Tasks stabilization remains the primary focus. Stabilization requires usage data to inform further decisions, which in turn requires unblocking developers from building on the experimental Tasks primitive. The current goal is expanding support in client applications. The Everything MCP server and MCP Inspector are have in-progress integrations, and Luca is working on integration in several AWS projects. Once developers build on Tasks, their feedback will inform how the WG addresses follow-up proposals and stabilizes the specification.
The working group remains open to new priorities as well.
Implicit/Explicit Session Creation and Session Tokens
Shaun introduced the brief for the Transports WG's Sessions track, which is of particular interest to the Agents WG as it affects how state is owned by different parties in multi-agent interactions over MCP. The Transports WG's next objective is to divide-and-conquer the many planned HTTP transport and protocol revisions for the June specification release. Shaun is leading the Sessions sub-group, which aims to decouple sessions from connection state. The first major TWG meeting for the year will be on January 14, 2026 (tomorrow).
The Sessions sub-group is looking at a cookie-style mechanism for connection-level statelessness, but hasn't yet decided on if session creation should be implicit when the client executes an operation against a server, or if it should be explicit via introducing new RPC methods. This concern also affects client applications more broadly - there are UX questions around whether a session should be scoped to a single chat (in applications with chats) or scoped to an entire application.
Peter noted that this is also of interest to the TypeScript and Python SDK maintainers, as it will potentially affect the design of the v2 SDKs in each language.
The Agents WG will continue to be involved in this initiative.
Agent Discovery and Interop Surfaces
Vinay raised the topic of how MCP, A2A, and similar protocols should enable agent-to-agent interaction. The idea he introduced is that these protocols should be able to support something that looks like a chat completions call for interacting with remote agents, which may or may not be stateful and/or have an internal tool loop. Sampling isn't sufficient for this use case as it's server-to-client rather than client-to-server. @thoorp highlighted similar work in IDEs to be able to represent calls to an agent as a sort of tool over MCP. @thoorp also noted that agencyHint (#1938) is along these lines and is, in addition to being a governance tool, an explicit codification that agent-driven tools exist from the perspective of the protocol.
The group will return to this in the next meeting after discussing these ideas in more detail.