GlossaryMCP (Model Context Protocol)

Before it, connecting a model to an internal system meant writing that integration against one vendor's tool-calling format, then writing it again for the next. MCP standardises the layer: a server describes what it offers, any compliant client can discover and call it, and the integration outlives the decision about which model to use.

That portability is the practical argument for it, and it matters more than it sounds. Model choice moves faster than internal systems do, and the work of exposing a CRM, a document store or a ticketing system is the expensive part. Doing it once against a protocol rather than against a vendor is what keeps that work from being rewritten every time the landscape shifts.