MCP is a common plug that connects models to tools without custom glue code.
DefinitionWhat it means
MCP, the Model Context Protocol, is an open standard, originated by Anthropic and now widely adopted, that defines a uniform way for a model-serving application to discover and call external tools, resources, and data sources exposed by an MCP server, replacing bespoke integration code for each pairing.
Why it mattersWhy you should care
MCP matters commercially because it turns tool integration into a build-once, connect-anywhere problem: a company can expose its database or SaaS product once as an MCP server and have it work with any compliant client, which is reshaping how vendors think about AI distribution and how buyers evaluate agent ecosystems.
At a glanceSee it
Before any tool runs, client and server negotiate capabilities — the model learns which tools exist and how to call them.
At runtime the model loops each turn, choosing to call a tool or answer, feeding results back until it stops.
Where you see itIn the wild
- MCP server directories for databases, browsers, and SaaS products.
- Claude Code and Claude Desktop configuration files listing connected MCP servers.
- Vendor roadmaps announcing native MCP support as an integration feature.