SEP-2575: Make MCP Stateless

Tracking implementation of SEP-2575 for the 2026-07-28 MCP spec release.

+1

@Kehrlann

Hello @Kehrlann , is this work in progress or are you looking for someone to take it on? Thanks

@YousefHaggy

Hey @YousefHaggy - as I mentioned in #274 (comment) , the core maintainer team is on-and-off on PTO, so we won't start the work for a few more weeks.

It tightly linked to #1004. Since this is quite foundational and involves a lot of design decisions, we'd like the core team to drive this. We'll request input from the community.

EDIT: we are not accepting contributions for this at the moment.

I'd like to contribute to this. Having reviewed SEP-2575 and the existing stateless server implementation (McpStatelessAsyncServer, HttpServletStatelessServerTransport, DefaultMcpStatelessServerHandler), the SDK already has strong foundations for stateless operation on the server side.

I'd propose tackling this incrementally, starting with the server-side protocol gaps:

server/discover RPC handler in the stateless server that returns ServerCapabilities, supported protocol versions, and server info without requiring initialization
Per-request protocol version validation via MCP-Protocol-Version header extraction in HttpServletStatelessServerTransport, returning appropriate errors on version mismatch
Per-request _meta extraction for clientInfo, clientCapabilities, and protocolVersion from request params, surfaced to handlers through McpTransportContext
Schema additions for MissingRequiredClientCapabilityError (-32003), discover request/response types, and the 2026-07-28 protocol version constant

This leaves the client-side stateless mode and subscriptions/listen as follow-up PRs. Would this scoping work for the maintainers? Happy to adjust based on feedback.

I see PR #1034 adding repository contracts for the stateless server. My work would be complementary, focusing on the protocol-level stateless mechanics rather than primitive resolution.

@elang2

@elang2 as stated in the comment above

Since this is quite foundational and involves a lot of design decisions, we'd like the core team to drive this. We'll request input from the community.

We will not be accepting contributions at this time.

Understood, thanks for the clarity. Happy to provide input when the community review phase opens.

Hey @YousefHaggy - as I mentioned in #274 (comment) , the core maintainer team is on-and-off on PTO, so we won't start the work for a few more weeks.

Hi, did the protocol change get picked up by now?
Interested, because we have several pending features related to that update

@clojj

Hey @clojj - not yet. Unfortunately it won't land before September.

@Kehrlann

Hey @Kehrlann,
Any news on this?

We have quite a lot of anticipation on MCP Gateway protocol mediation waiting for the SDK update.
Thank you

@Johngren

@Johngren Still won't land before September.

We're in the early stages of the design process. We'll try to get the first milestones out in September.

Hi, Any Update on this?

Navigation Menu

Repository navigation

SEP-2575: Make MCP Stateless #1011

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

SEP-2575: Make MCP Stateless #1011

Description

Activity

BerkeAras commented on Jun 16, 2026

YousefHaggy commented on Jul 4, 2026

Kehrlann commented on Jul 10, 2026

elang2 commented on Aug 2, 2026

Kehrlann commented on Aug 3, 2026

elang2 commented on Aug 3, 2026

clojj commented on Aug 6, 2026

Kehrlann commented on Aug 6, 2026

Johngren commented on Aug 26, 2026

Kehrlann commented on Aug 26, 2026

morad3741 commented on Sep 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions