Model Context Protocol (MCP) is an open standard released by Anthropic in late 2024 for connecting LLMs to external data sources and tools. It's quickly becoming the "USB-C of AI" — a universal connector that lets any AI application talk to any data source through a standardized interface.
Before MCP, every AI application that wanted to connect to external tools had to build custom integrations. Want your AI assistant to read your Google Drive? Custom integration. Slack? Another custom integration. GitHub? Another one. This led to a combinatorial explosion of integrations that were hard to build and harder to maintain.
MCP standardizes this with a single protocol: LLM applications speak MCP on one side, tool providers implement MCP on the other, and any combination works.
MCP defines three primitives:
An MCP server exposes these primitives over a standard transport (stdio or HTTP/SSE). The LLM client connects to one or more MCP servers and gets access to all their resources and tools.
# Example MCP server config (claude_desktop_config.json)
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/Documents"]
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."}
}
}
}
With this config, Claude Desktop can read your local filesystem and interact with GitHub repositories through standardized MCP tools.
MCP adoption has been rapid. Major adopters include:
Hundreds of MCP servers are now publicly available for databases, APIs, developer tools, and SaaS products.
| Function calling | MCP | |
|---|---|---|
| Scope | Per-application | Cross-application standard |
| Reusability | Low — rebuild for each app | High — build once, use anywhere |
| Discovery | Static, defined in code | Dynamic, servers advertise capabilities |
| Transport | In-process | stdio or HTTP/SSE |
| Ecosystem | Fragmented | Growing standard |
MCP is to AI agents what HTTP is to the web — a common protocol that lets any client talk to any server. Teams building agents today should be building MCP servers, not proprietary integrations.
Agentic MCP workflows make many LLM calls per task. Tokoscope tracks every call so you know what each agent session actually costs. Free to start.
Get started free →