What should an MCP client do when no mutually supported protocol version can be found?

Attempt it

Quick reference

TL;DR

When no shared protocol version exists, the MCP client should abort gracefully at initialize time and report the mismatch, never proceed and hope runtime errors catch it.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Picture two people meeting who each speak a few languages. Before chatting, they swap lists and pick one both know. If the lists overlap, great, they talk in that shared language. If there is zero overlap, the sensible move is to stop and say 'we cannot understand each other' right away. The reckless move is to just start talking in your own language and hope the other person guesses. MCP works the same way at connection time. The client sends the newest version it knows. The server either agrees or names one it prefers. If nothing matches, the honest move is to close the connection and report it, not to barrel ahead and discover the breakage halfway through a real task.

Key concepts

Protocol version negotiation Initialize handshake Capability gating

Quick scan · 2–4 min

Everything important, quickly.

4 min: walk the initialize handshake, the version proposal and counter, the no-overlap abort decision, capability decay risk, and how version vs capability gating drives compatibility.

Side-by-side

Aspect	Protocol version	Capabilities
What it selects	The wire contract and method set	Which optional features are live
Format	Date based string (2025-06-18)	Named flags (tools, resources, prompts)
Negotiated where	initialize request and response	Same handshake, capabilities field
No agreement means	Abort the connection	Feature is simply unavailable
Failure mode if ignored	Wrong method set, broken contract	Calling an unadvertised feature

Real-world examples

Real products, models, and research that use this idea.

Claude Code and Claude Desktop send their supported MCP version in the initialize request and refuse to operate against a server with no shared version.
The official MCP TypeScript and Python SDKs implement the initialize handshake and reject connections when the negotiated version is unsupported.
mcp-inspector lets you watch the initialize exchange and see exactly which protocolVersion string each side proposes during debugging.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QHow does capability negotiation in the same handshake differ from protocol version negotiation?

Sign in or go Pro to see the approach for this follow-up.

QHow would you design a host to stay compatible across a server fleet on mixed MCP versions?

Sign in or go Pro to see the approach for this follow-up.

QWhy does MCP use date-based version strings instead of semantic versioning?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.