Skip to main content
The MCP server’s tools and their inputs and outputs are versioned. Each version is fixed once published: a client connected to a version keeps the same tools and the same schemas for as long as that version is served.

Choosing an endpoint

The current default is 0.9.0. The latest version is 0.11.0. Use /mcp for interactive assistants such as Claude, which read the tool list each time they connect and adapt to changes. Pin a version for anything built against specific tool calls: an internal app, a scheduled job, or an agent harness whose prompts are tuned to a tool contract. A pinned version only changes when you change the URL.
Pin in production and test the latest version in development. That way you find out about a contract change on your own schedule.

How versions change

  • Additive changes, such as a new tool or a new optional parameter, can ship in a new version without notice. Existing calls keep working.
  • Breaking changes, such as a removed or renamed tool, a newly required parameter, or a changed result shape, ship first as a new version you can test at its versioned URL. The default only moves to a version with breaking changes on a date we announce in advance. The version history below marks each breaking version, with a migration guide where you need to change your client.
  • If you’re not ready to move, pin the version you’re on before the announced date. Older versions stay served.
Some clients, including ChatGPT, keep the tool list they read when they first connected. After the default moves, refresh or reconnect the connector so it reads the new list.

Version history

Full tool and parameter references: Version 0.9.0, Version 0.10.0, Version 0.11.0.

Tools by version

Which customer-facing tools each version registers. A session may see fewer: some tools also depend on the user’s permissions and your organization’s setup, as the tool reference explains.