Model Context Protocol
An open protocol for exposing tools, resources and prompts to models, so integrations are written once rather than per model provider.
By Lattice editorial · Entry last reviewed · method
What it implies
The main thing to know is that it moves the integration burden from 'an adapter per provider per tool' to 'one server per tool'. The corollary is a security one: an MCP server is a new dependency that can exfiltrate whatever it is given, so it deserves the same review as any other external service.