What Is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is an open standard for connecting a single AI agent to tools, data and context through a uniform interface, so a model can call a capability without a bespoke integration per source. It is the substrate by which one agent reaches the world — its hands — and it deliberately leaves organisational identity, authority and payment to other layers.

Connects

One agent ↔ tools, data, context

Shape

A uniform interface, not per-tool glue

Out of scope

Identity, authority, payment, proof

Complements

A2A (agent-to-agent)

The agent’s hands

Before a shared protocol, every tool an agent used needed its own integration. MCP standardises that surface: a server exposes tools and resources, and any MCP-speaking agent can use them. It is about capability access, not about who is allowed to act or who is accountable — those are separate layers that compose on top.

Related standards

MCPA2A

Questions

Is MCP the same as an API?

MCP is a standard way for an agent to discover and call tools and data; a REST API is one thing an MCP server might wrap. MCP standardises the agent-facing surface across many such sources.

Does MCP handle payments or identity?

No. It focuses on tool and context access. Payment, identity, authority and proof are separate, composable layers.