Model Context Protocol
The open standard that lets any AI app plug into tools and data — USB-C for AI integrations.
About
The Model Context Protocol (MCP) is an open standard that defines how AI applications connect to external systems. Instead of writing a bespoke connector for every pairing of AI model and business tool, developers build one MCP server per system and any MCP-compatible client can use it. The protocol runs on JSON-RPC 2.0 and defines three capability primitives: tools the model can call, resources it can read, and prompts that shape how it works.
MCP was introduced and open-sourced by Anthropic on November 25, 2024, and on December 9, 2025 Anthropic donated it to the Agentic AI Foundation, a Linux Foundation directed fund co-founded by Anthropic, Block, and OpenAI — so it is now vendor-neutral by governance, not just by license. Adoption moved fast: Anthropic reported 10,000+ active public MCP servers and 97 million monthly SDK downloads by late 2025, with support across ChatGPT, Cursor, Gemini, Microsoft Copilot, and VS Code. The current spec (dated July 28, 2026) reworked the core to be stateless, hardened authorization, and added a formal extensions framework.
The honest caveat: MCP standardizes the wire format, it does not eliminate integration work. Every system still needs someone to build and maintain its MCP server, and the flood of community servers varies wildly in quality and security posture — treat third-party servers like any other untrusted dependency.
What it can do
- Open, vendor-neutral standard (MIT) for AI-to-tool connectivity, governed by the Linux Foundation
- Host/client/server architecture: one server works with every compatible AI application
- Three primitives: executable tools, readable resources, reusable prompt templates
- Official SDKs in TypeScript, Python, C#, and Java; transports over stdio and HTTP
- Stateless core and hardened authorization in the July 2026 spec revision
Setup
- Read the spec at modelcontextprotocol.io to understand hosts, clients, and servers.
- Pick an SDK (TypeScript, Python, C#, or Java) and scaffold a server with
npx @modelcontextprotocol/create-serveror the Python equivalent. - Define your tools (
tools/list,tools/call) plus any resources or prompts. - Point an MCP-compatible host (Claude, Cursor, VS Code, etc.) at your server config and test discovery.
Prerequisites
Familiarity with JSON-RPC concepts helps; Node.js 18+ or Python 3.10+ for the official SDKs. No account or key needed — the spec is open.
Use cases
Works with
Trust score — 10/10
Scored 10/10 (verified tier, metrics-v1). Evidence: Open standard for AI-to-tool connectivity: JSON-RPC 2.0, tools/resources/prompts primitives, verified against the official spec site; Launched by Anthropic Nov 2024; donated Dec 2025 to the Agentic AI Foundation (Linux Foundation, co-founded by Anthropic, Block, OpenAI) — vendor-neutral governance verified via multiple 2026 sources; Adoption: 10,000+ public MCP servers, 97M monthly SDK downloads (Anthropic, Dec 2025); supported by ChatGPT, Cursor, Gemini, Copilot, VS Code. Manual review: standardization claims hold up; honest caveat that MCP does not eliminate integration work and community servers vary in quality/security — documented in the entry. License: MIT.
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 10.0/10
- Maintenance · recency, releases, issue load
- 10.0/10
- Openness · license + docs
- 10.0/10
- Manual review · sanity read + red-flag check
- 9.0/10
- · Open standard for AI-to-tool connectivity: JSON-RPC 2.0, tools/resources/prompts primitives, verified against the official spec site
- · Launched by Anthropic Nov 2024; donated Dec 2025 to the Agentic AI Foundation (Linux Foundation, co-founded by Anthropic, Block, OpenAI) — vendor-neutral governance verified via multiple 2026 sources
- · Adoption: 10,000+ public MCP servers, 97M monthly SDK downloads (Anthropic, Dec 2025); supported by ChatGPT, Cursor, Gemini, Copilot, VS Code
- · manual review: standardization claims hold up; honest caveat that MCP does not eliminate integration work and community servers vary in quality/security — documented in the entry
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.