What Actually Changes Between MCP Server Versions
MCP server upgrades rarely announce themselves as behavioral changes. More often they arrive as a new negotiated protocol version, an updated tool schema, a revised capability declaration, or a mid-session list-changed notification that expands or narrows what an agent can do. Each of these elements is negotiated or exchanged during the initialize handshake and the session that follows, and each can shift how an agent selects and invokes tools without any corresponding change to the agent's own code or prompts.
Tool schemas, defined in JSON Schema, govern what an agent believes it is allowed to pass to a tool call. When a server version updates a schema (adding a required field, narrowing an enum, changing a parameter type) an agent's existing reasoning may continue to produce calls that are now invalid, or calls that remain technically valid but carry different meaning than before.
Why This Creates Blind Spots in Practice
Because MCP does not define a standard mechanism for diffing behavior across versions, most teams only discover drift when it surfaces downstream: a permission failure, a tool invocation that returns an unexpected result, or an agent that silently stops using a capability it previously relied on. Free-text application logs rarely capture the structured handshake and schema data needed to reconstruct what changed, which means the investigation starts after the fact rather than during testing.
Mid-session capability changes compound this problem. A list-changed notification can add or remove tools, resources, or prompts after the initial handshake, and if this event is not logged with the same rigor as the initial session negotiation, the audit trail has a gap exactly where behavior is most likely to shift.
Implementation Decisions Worth Making Explicit
Teams building this audit capability without vendor-specific tooling need to settle a few decisions before logging begins:
- Which fields are mandatory in every session record, including protocol version, capability declarations, tool schemas in effect, and mid-session notifications.
- How version-tagged records are retained and who can access them, aligned with existing internal logging standards rather than treated as a new policy category.
- How tool descriptions and annotations supplied by the server are treated during review, consistent with MCP's own guidance that this data is untrusted unless the providing server is trusted.
- How identical test inputs are run against two server versions in parallel to produce a comparable, structured diff rather than a subjective read of two log files.