About MCP Blog

Who publishes MCP Blog

MCP Blog is an independent editorial project. It is not operated by Anthropic, the Agentic AI Foundation, the Linux Foundation, or the official Model Context Protocol project. “MCP” is used descriptively to identify the protocol we cover.

Articles are published under the MCP Blog Editorial Team byline while the project is in its founding stage. Articles cite specifications, repository history, security advisories and product documentation.

Why another MCP publication?

The July 2026 specification created a sharp compatibility boundary. It removed initialization and sessions from the modern core, introduced discovery and multi-round-trip requests, and moved some behavior into extensions. Yet many highly visible explainers continue to describe the previous stateful architecture without a version label.

Each technical guide names the protocol revision it describes. Older behavior is labeled so that you can compare it with the version you use.

How automation is used

AI tools are used to help research, draft and edit articles. Automated checks also validate links, code and the built website. Sources and test results are cited separately; a generated explanation is not itself evidence.

Tested examples and product reviews

The Python server and Skills guides include commands we ran and the results we observed. Product support tables describe vendor documentation unless a test is explicitly stated. A successful local example does not establish that every host supports it.