Skip to main content
Platform MCP Docs

MCP Environments and Versioning

Select the canonical route, negotiate supported protocol versions, and migrate compatibility clients safely.

Version MCP 2025-11-25 Current Streamable HTTP contract with compatibility versions Reviewed Jul 26, 2026 Next review Oct 26, 2026

The free Developer workspace is for non-production building and learning under published limits. External API or MCP client credentials use a separate scoped request and approval process.

Owner: Batoi Developer Experience Reviewed by: Batoi Platform Security Source revision: upgrade-jul-26-2026

Browse Batoi Platform MCP Documentation MCP Environments and Versioning

MCP Environments and Versioning

Workspace host registration and policy determine the environment and capabilities available to a client. A client cannot promote itself by changing a URL, workspace slug, header, or tool argument.

Negotiation

The current server version is 2025-11-25. Initialization selects a supported client version or the current version. Current requests send the negotiated MCP-Protocol-Version header.

Compatibility versions are retained for measured migration. They do not bypass workspace, host, policy, capability, or audit controls.

Canonical and alias routes

Use /mcp/{workspace}/ for new clients. The /ai-gateway/mcp/{workspace}/ route is a compatibility alias to the same implementation and authorization service.

An alias can be removed only after usage falls below the approved threshold, a sunset is published, consumers are contacted, compatibility tests pass, and rollback evidence exists.