Model Context Protocol (MCP)
Model Context Protocol (MCP) is an open protocol developed by 📝Anthropic that standardizes how 📝Artificial Intelligence models connect to external tools, data sources, and systems. Anthropic introduced MCP in November 2024 and on December 9, 2025 donated it to the Agentic AI Foundation, a directed fund of the 📝Linux Foundation co-founded by Anthropic, Block, and 📝OpenAI, which now hosts it as a vendor-neutral standard. At the time of the donation, MCP counted more than 97 million monthly SDK downloads and 10,000 active servers. Sources: Anthropic — Introducing the Model Context Protocol; Anthropic — Donating the Model Context Protocol.
MCP solves a fundamental problem: AI models are powerful reasoners trapped behind limited interfaces. Without MCP, every integration between an AI and an external tool requires custom code — a different API wrapper for every database, every SaaS product, every knowledge system. MCP provides a universal connector protocol so that any AI client can use any 📝MCP server, and any tool builder can expose their system to any AI model.
How It Works
MCP uses a client-server architecture:
- MCP clients are AI applications (like 📝Claude Code, 📝Claude.ai, 📝Cursor, Windsurf) that connect to servers to access external capabilities
- MCP servers are lightweight programs that expose specific tools, resources, and prompts to clients. A server might give the AI access to a database, a file system, a browser, a knowledge base, or any other system
- Transport layers handle communication — stdio for local servers, Streamable HTTP for remote ones
The protocol exposes three primitives: Tools (actions the AI can take), Resources (data the AI can read), and Prompts (reusable instruction templates). This maps naturally to 📝The Augmentation Stack — tools are Mind-layer capabilities, resources are Memory-layer access, and prompts are orchestration patterns.
The current specification, revision 2026-07-28, carries these three server features over JSON-RPC 2.0 messages and lists one client feature, Elicitation, through which a server asks the user for additional information. The same revision deprecates the Roots, Sampling, and Logging features and removes the initialize handshake, so every request is self-contained. Sources: MCP Specification; 2026-07-28 changelog.
The Ecosystem
- 21,561 servers listed on PulseMCP as of November 10, 2026
- Major adopters: 📝Google Cloud, OpenAI, 📝Microsoft, 📝Vercel, 📝Cloudflare, 📝Shopify
- Governance: the Agentic AI Foundation since December 9, 2025 — co-founded by Anthropic, Block, and OpenAI, with AWS, Google, Microsoft, Cloudflare, and Bloomberg as platinum members — where MCP is a founding project alongside Block's goose and OpenAI's 📝AGENTS.md
Sources: Google Cloud MCP release notes (remote MCP servers generally available May 1, 2026); Anthropic (ChatGPT, Microsoft Copilot, and Visual Studio Code among MCP's adopters); Vercel MCP; Cloudflare MCP docs; Shopify Checkout MCP; Linux Foundation, December 9, 2025 (platinum members and founding projects).
Notable MCP servers include the reference Filesystem, Git, and Fetch servers (modelcontextprotocol/servers), GitHub's official server, browser automation (Microsoft's Playwright MCP), and knowledge management platforms like MythOS. The protocol supports both local servers (running on your machine via stdio) and remote servers (hosted services accessible via HTTP).
Why It Matters for Augmentation
MCP is the infrastructure layer that makes 📝human-AI augmentation practical at scale. Before MCP, connecting an AI to your knowledge system, your calendar, your codebase, and your CRM required building four separate integrations. With MCP, each of those systems publishes a server, and your AI client connects to all of them through one protocol.
As of April 2026, for 📝Brian Bot's 57-agent ecosystem, MCP is the connective tissue: every agent accesses 📝MythOS through the 📝MythOS MCP server, gaining access to 17,000+ memos, augmentation context, and the full knowledge graph. Without MCP, each agent would need its own database connection, its own context loading logic, and its own tool definitions. MCP standardizes all of it.
For how MCP differs from retrieval, see 📝MCP vs RAG; for knowledge bases connected through it, 📝MCP for Personal Knowledge Systems and 📝AI Memory Systems; to build one, 📝How to Build Your First MCP Server.
MCP is the thing I point people to when they ask how BrianBot works. Not Claude, not 📝OpenClaw, not MythOS — MCP. Because MCP is what makes the system possible. It's the reason 57 agents (as of April 2026) can all access the same knowledge base, the reason my 📝CLAUDE.md syncs from a MythOS memo, the reason I can talk to my library from my phone.
The best analogy: MCP is to AI what HTTP was to the web. HTTP didn't create web pages — it created the standard that let any browser talk to any server. MCP doesn't create AI tools — it creates the standard that lets any AI talk to any tool. That's the kind of infrastructure shift that changes everything downstream.
