Skip to the content
five peers
Journal · Developers

MCP explained, and what it does not give you

A useful, boring piece of plumbing that is regularly oversold. Worth understanding precisely, because the overselling is usually about portability.

Developers · 5 min read
What is the Model Context Protocol? An open standard for connecting AI assistants to external tools and data sources through a common interface, so a capability built once can be reached from several assistants rather than integrated separately into each.

Before a standard existed, every assistant had its own way of exposing tools, and every integration was rebuilt per platform. MCP defines a common protocol: a server exposes capabilities, a client connects, the assistant can call them. That is genuinely useful and genuinely unglamorous.

What it gives you

What it does not give you

This is the part that gets skipped in marketing copy.

Portability comes from the format your data leaves in, not from the protocol it arrives through.

The honest version of the portability claim

What genuinely survives a change of model is a record in an open format that you can export and read without our software. That is a property of the data, and it is testable: ask any vendor for an export and see what you get.

Five Peers editorial note. Sources named in the text.

The record exports whether or not the connector is open.

Compose my board