MCP
Model Context Protocol
An open protocol that lets a model call external tools and read external data through a standard interface.
Before MCP, every integration between a model and an outside system was bespoke. MCP standardises the handshake: a server advertises the tools it offers and the resources it can read, and any client that speaks the protocol can use them without knowing anything about that particular server.
The consequence is that an MCP server is a piece of software you install and grant access to, in much the same way as a browser extension. That framing is the useful one, and it is the reason the security questions on this site look the way they do.
It is the reason a market for third party agent tooling exists at all. A standard interface is what makes a marketplace possible.
Treating an MCP server as a library rather than as software with privileges. A library runs where you put it. A server describes its own capabilities to a model that will then decide when to use them.
Related terms
See MCP on a real listing
Every term here shows up in the catalogue next to a real result, with the findings published and the limits stated. Free to browse, no account needed.
Open the catalogue