A common connection interface
The Model Context Protocol is an open protocol for connecting AI applications to external tools and context. Its architecture includes a host application, clients and servers. A server can expose capabilities such as tools, resources or prompt templates.
What a connection does
An application can discover an available capability and exchange structured messages with the server. This helps integrations use a common interface instead of each application inventing a different connector format.
What it does not guarantee
MCP is not an AI model, a database or automatic permission to access a system. Authentication, authorisation, tool validation and consent still need deliberate implementation. A reachable server is not proof that every tool is safe or appropriate.
An enterprise example
An approved server could expose a read-only document search tool. The host should pass the correct user identity, enforce document access and treat retrieved text as data. Any action that changes a record needs the organisation’s own authority and review controls.
Sources & further reading
Reviewed 19 October 2026. This is a technology learning session; examples describe possible designs, not a claim that a particular integration is active.
METANOW