Model Context Protocol

Protocolo P2P

Open JSON-RPC 2.0 protocol specification for connecting AI applications (clients) to external tools, data sources, and capabilities (servers). Defines a small set of primitives — tools (actions), resources (read-only context), and prompts (reusable templates) — over two transports (stdio for local processes, HTTP/SSE for remote servers), with a capability-negotiation handshake on connect. Originally introduced by Anthropic in November 2024 to address the N×M integration problem; donated to the Agentic AI Foundation under the Linux Foundation in December 2025 as neutral infrastructure

Comunidad
Enlaces
Visitar Comunidad

Detalles

Licencia MIT (specification and SDKs) — Python, TypeScript, C#, Java, and other reference SDKs
Estado de Desarrollo 🟢 Activo
Detalle del Estado de Desarrollo Released — widely adopted production standard with versioned spec releases (most recent revision 25 Nov 2025); over 10,000 active public MCP servers reported by March 2026
Propietario Agentic AI Foundation (directed fund of the Linux Foundation, co-founded by Anthropic, Block, OpenAI, with support from Google, Microsoft, AWS, Cloudflare, Bloomberg). Originally created and open-sourced by Anthropic
Órgano de Gobierno Agentic AI Foundation (directed fund of the Linux Foundation; co-founded by Anthropic, Block and OpenAI)
País USA (originated at Anthropic, San Francisco; governance now under Linux Foundation)
Año de Inicio 2024
Stack JSON-RPC 2.0 over stdio or HTTP+SSE
Financiamiento Originally Anthropic; now governed under Linux Foundation directed fund (AAIF) with member support from Anthropic, Block, OpenAI, Google, Microsoft, AWS, Cloudflare, Bloomberg
Última Investigación 1 jul 2026

Dominios de Caso de Uso

Evolución de Plataformas y Soberanía

Protocolo P2P Atributos

Orígenes Anthropic (Nov 2024)
Base de Datos N/A — protocol does not specify or mandate persistence; servers may use any backing store
Lenguaje de Consulta N/A — protocol uses JSON-RPC method calls (initialize, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get, sampling/createMessage), not a query language
Formatos de Datos JSON-RPC 2.0 messages
Edición Colaborativa en Vivo N/A — agent-to-tool protocol, not a collaboration protocol
Edición de Texto Enriquecido N/A — protocol carries structured tool inputs/outputs and resource content, not authored documents
Soporte Móvil Yes — transport-agnostic; clients run on any platform that can speak JSON-RPC over stdio or HTTP, including Claude mobile and other mobile-hosted clients
Soporte Web Yes (HTTP+SSE transport)
Aplicaciones Nativas Yes (stdio transport for local processes; reference clients include Claude Desktop, Claude Code)
Términos Open standard, free to implement
Fondos Unknown — Agentic AI Foundation funding details not publicly itemized; member contributions from Anthropic, Block, OpenAI, and other AAIF members fund overall foundation operations
Basado En JSON-RPC 2.0
Arquitectura P2P Client–server (not peer-to-peer in the architectural sense; included in OpenHaven on the precedent set by A2A and x402 as an open multi-implementor specification with no single controlling network operator)
Red de Superposición N/A — runs over stdio or HTTP+SSE; no overlay network
Direccionamiento por Contenido N/A — Resources are URI-addressed by server-defined schemes; protocol does not require content-addressing
Local-First Yes — stdio transport is local-first by design; servers can run entirely on the user's machine with no network dependency
Cifrado de Extremo a Extremo (E2EE) Transport-dependent (HTTPS for remote; local for stdio); no protocol-level E2EE primitive
Biblioteca de CRDTs N/A — protocol does not define replicated data types or merge semantics
Tolerancia a Fallos Bizantinos N/A — single-host single-server interaction model; no consensus or multi-party agreement
Firma N/A at the protocol layer — message integrity relies on transport (TLS for HTTP+SSE, OS-level for stdio); spec does not define application-layer signatures
Permisos Capability negotiation handshake; per-tool authorization handled by host application
Compatibilidad con la Web Semántica N/A — Resources use URIs but no semantic-web vocabulary, RDF mapping, or JSON-LD context defined by the protocol
Contrato Inteligente N/A — no on-chain contracts or cryptoeconomic enforcement
Posición en la Pila del Protocolo Application layer — agent-to-tool integration
Incorporación de Activos/Valor None — MCP carries no native value transfer; companion to x402 (HTTP-payments) and A2A (agent-to-agent) for the agent-economy stack
Madurez del Protocolo / Estandarización Production-ready; governed under Linux Foundation Agentic AI Foundation