Creativity · Agent Protocol
Agents ↔ MCP Interoperability
MCP was introduced by Anthropic in late 2024 and adopted across OpenAI, Google, and the open-source agent ecosystem by 2025. A well-built MCP server is automatically usable by Claude Code, ChatGPT Enterprise, Cursor, and any framework (LangChain, LlamaIndex, CrewAI) that speaks MCP — replacing bespoke per-vendor tool integrations with one shared interface.
Protocol facts
- Sponsor
- Anthropic (origin) + broad industry adoption
- Status
- stable
- Spec
- https://modelcontextprotocol.io/
- Interop with
- Claude, ChatGPT, Gemini, LangChain, LlamaIndex, Cursor
Frequently asked questions
How do MCP and A2A relate?
MCP is agent↔tool; A2A is agent↔agent. An A2A-compliant agent may internally use MCP servers to do its work. They're layered, not competing.
What transports does MCP support?
stdio (local subprocess), Streamable HTTP (remote, 2025+), and historically SSE (deprecated in favor of Streamable HTTP). Remote MCP typically adds OAuth for authentication.
Is there a registry of MCP servers?
Yes — Anthropic and the community maintain registries of popular MCP servers (GitHub, Slack, Google Drive, Postgres, etc.). Many vendors now publish official MCP servers for their products.
Sources
- MCP specification — accessed 2026-04-20
- MCP GitHub org — accessed 2026-04-20