Skip to content
BENIBIX Learn

MCP Protocol Version

AI🔌 MCPMCP Architecture

Also known as MCP Spec Version, MCP Specification Revision, server/discover, MCP Lifecycle

The date that names one MCP release, like 2026-07-28, so both sides speak alike.

Think of it like

It is like the date on a rule book. Both players check they use the same book before they play.

Example

A client sends a request marked 2026-07-28. An older server does not know that version, so it replies with the versions it does know.

Why it matters

Clients and servers update at different times. The version lets an old one and a new one still find a way to talk.

Definition

The MCP protocol version is the date that names one release of the MCP rules, such as 2026-07-28. The date marks the last time the rules changed in a way that breaks old code. Up to 2025-11-25, client and server agreed on a version in a start-up handshake. Since 2026-07-28, every request carries its version instead. A client can also ask a server which versions it speaks.

Example code

json
{
  "method": "server/discover",
  "params": {
    "_meta": {
      "io.modelcontextprotocol/protocolVersion": "2026-07-28"
    }
  }
}
A client asks a server which versions and features it has.
Each MCP release is named by a date. The newest puts it on every request.

Common mistake

Thinking the date changes every time the rules do. It only changes when old code would break.

Key takeaways

  1. 1
    Named by a date. Year, month and day.
  2. 2
    On every request. Since the 2026-07-28 release.
  3. 3
    Ask first if you like. server/discover lists versions.