Versioning and changelog

The running MCP tool registry and its schemas are the source of truth. Public documentation is checked against the implemented registry before release.

Tool and schema changes

Adding an optional field or a new tool is normally additive. Removing a tool, changing a required input, changing output meaning, or widening authorization requires explicit compatibility and security review.

Existing connections keep the scopes approved at their own consent time. A newly introduced scope requires a fresh authorization flow before a connection can use tools guarded by it.

Changelog policy

A release changelog should identify the affected tools or scopes, whether a change is additive or breaking, the action required from a host or account owner, and the effective date.