Skip to content

Capabilities API + server/discover handler #2896

@maxisbey

Description

@maxisbey

Tracks: #2804 #2793

Let servers/clients actually configure what they advertise (currently pre-computed), surface the extensions map, and provide the default server/discover handler that returns it.

What's in it

  • Rework get_capabilities() / InitializationOptions so capabilities are configurable, not pre-computed.
  • The extensions capability map surfaced on both client and server.
  • Default server/discover handler: capabilities, serverInfo, supportedVersions, instructions (cache-hint defaults from Caching hints (ttlMs / cacheScope) #2899).

Conformance

  • (the discover checks live inside server-stateless)
  • Together with Backwards compatibility & version negotiation, New HTTP serving path (modern + dual-era), subscriptions/listen, Context object (layered, per-request): server-stateless

Dependencies

References

Metadata

Metadata

Assignees

Labels

spec-2026-07-282026-07-28 MCP spec release workv2Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixes

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions