Model Context Protocol
Also: MCP, MCP connector
MCP (Model Context Protocol) is an open standard that defines how AI models connect to external data sources and tools. Instead of every developer building their own custom integration, MCP gives a universal interface: if a tool supports MCP, any MCP-compatible AI can use it. Anthropic created and open-sourced it. In practice, MCP is what makes it possible for Claude to connect to your file system, your database, your APIs — in a structured, secure way.
In practice
You want Claude Code to be able to read your Jira tickets, push commits to GitHub, and query your database — all from one session. Model Context Protocol is the standard that makes this work: it defines how Claude connects to external tools so every tool speaks the same language and Claude can use them all without custom integration code for each.
Related concepts
Where Model Context Protocol shows up
3 articlesMCP is the plumbing that lets Claude connect to anything. Here is what operators need to understand — and when it becomes relevant for your organisation.
The MCP connector lets a Claude agent reach live production systems — CRMs, databases, internal APIs — at runtime, without you building custom tool integrations for each one. Here's how to structure that connection safely and what breaks when you don't.
The Model Context Protocol sounds technical. The practical implication is simple: AI tools can now connect to your actual systems in a standardised, safe way. Here's what that means for how you work.