Skip to navigation

Versioning

The server is improved on an ongoing basis. Backwards-compatible changes are made without notice, while breaking changes to existing tools are avoided wherever possible.

Your assistant requests the list of available tools each time it connects, so new tools become available automatically, with nothing for you to update.

What’s a non-breaking change?

  • Adding a new tool.
  • Adding a new optional parameter to an existing tool.
  • Adding a new field to a tool’s response.
  • Clarifying or improving a tool’s description.

What’s a breaking change?

  • Removing or renaming a tool.
  • Removing or renaming a parameter on an existing tool.
  • Adding a new required parameter, or making an existing optional parameter required.
  • Changing the meaning or type of an existing parameter.
  • Removing or restructuring fields in a tool’s response.
  • Changing what an existing tool does.

How breaking changes are released

A breaking change is never applied to an existing tool in place. Your assistant discovers tools by name, so a changed contract under the same name would break agents that already rely on it. Instead:

1

A new tool is added

The new behaviour ships as a separate tool with its own name. For example, a breaking change to create_payment_link is released as a new create_payment_link_v2 tool.

2

The existing tool is deprecated

create_payment_link keeps working, with its description marking it as deprecated and pointing to the replacement.

3

The deprecated tool is removed

After a deprecation period, the deprecated tool is removed. Your assistant picks up the replacement automatically the next time it connects.

Protocol version

The server implements the Model Context Protocol, which is versioned by date, such as 2025-06-18. Your assistant and the server agree on a compatible protocol version automatically when they connect, so there’s nothing for you to configure.