Term
MCP
MCP, the Model Context Protocol, is a contract for how a model calls tools: what it may see, what it may change, and how the call is logged. The official split is host, client, and server, with tools, resources, and prompts as the primitives. Auth is optional; least privilege is not. A server without a contract is a hole in the repo. Founders should care about the interface and the permission, not the logo on the protocol. A clean server with no charter is still a hole with nicer plumbing.
When to use it
Use it when an agent can touch files, mail, or money and nobody wrote the ceiling down. If the permission lives in a Slack thread, you do not have a contract.
Do not confuse with
Not a vendor product line and not the definition of an agent. MCP is how a worker is allowed to touch the building. The worker still needs a charter.