Catalog Systems Agent frameworks (no first-party memory layer) Model Context Protocol (MCP spec)

Model Context Protocol (MCP spec)

https://modelcontextprotocol.io/

Anthropic-introduced open protocol (Nov 2024) for connecting LLMs to data sources and tools. Donated by Anthropic to the Linux Foundation's Agentic AI Foundation (announced 2025-12-09); now governed as Model Context Protocol, a Series of LF Projects, LLC. Supported across Claude, ChatGPT, VS Code, Cursor and many other clients.

Active · Verified 2026-10-27 · fresh as of 2026-10-27 · 38 cited facts, 3 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Type
Open protocol for LLM-tool I/O vendor fix
Tier
T1
Section
Agent frameworks (no first-party memory layer)
Created
2024 third-party fix
Latest release
v1.32.2 (2026-10-23) — TypeScript SDK; Python SDK v2.3.0 (2026-10-02); current spec revision 2026-07-28 registry fix
License
Apache-2.0 (new spec and code contributions; transitioning from MIT, un-relicensed MIT contributions remain MIT); docs CC-BY-4.0 repo fix
GitHub
modelcontextprotocol/modelcontextprotocol — ~9.5k stars, last commit 2026-10 repo fix
Pricing
searched not found fix
Funding
searched not found fix
Freshness
2026-10-27 fix
Layer
agent-infra repo fix
Licensing
open-source repo fix
SDK languages
csharp, go, java, kotlin, php, python, ruby, rust, swift, typescript vendor fix
Developer activity
OpenRank 17.04 (12-mo avg 34.32) · 112 participants — 2026-09 third-party fix

When to use

Optimised for: searched not found

Anti-fit: searched not found

Pros & cons

Pros

searched not found

Cons

searched not found

Claims & capabilities

Adopted by OpenAI, Microsoft, Cursor, Continue, Windsurf within ~6 months of release.

Technical surface

API surface
searched not found
Backend storage
not applicable — not a memory product
Deployment
searched not found
Embedding model
not applicable — not a memory product
Multi-tenancy
searched not found
MCP
yes — this is the MCP specification itself
A2A
searched not found
OpenTelemetry
searched not found

Compare Model Context Protocol (MCP spec) with…

Alternatives to Model Context Protocol (MCP spec) → live options ranked by shared design, licence, hosting and MCP support

Similar systems

Other agent frameworks (no first-party memory layer) in the catalog, ranked by inbound references.

  • LangChain (framework) T1

    Dominant Python/JS framework for LLM apps — tool calling, agents, retrievers, runnables. Memory is one component (LangMem cross-listed); the framework itself is the product.

  • Vercel AI SDK T1

    Vercel's TypeScript LLM SDK — streaming, tool calls, structured outputs, agents. Dominant framework for Next.js LLM apps.

  • LlamaIndex (framework) T1

    Data framework for LLM apps — connectors, indices, query engines, agents, workflows. Memory is one of many subsystems (LlamaIndex Memory cross-listed).

  • OpenAI Agents SDK T1

    OpenAI's official Python framework for agents — handoffs, guardrails, tracing built in. Successor to OpenAI Swarm (experimental); officially supported.

  • LangGraph (orchestration) T1

    LangChain's stateful graph runtime for agents — explicit state, persistence, time-travel debugging, human-in-the-loop. Memory is one persistence target (LangGraph Persistence cross-listed).

  • CrewAI T1

    Multi-agent framework — Crews (sequential) + Flows (event-driven). Open-source core + CrewAI Enterprise. Memory available via Mem0 / Letta adapters (CrewAI Memory cross-listed).

Sources (37 cited facts, 3 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-27
    • License “MIT (spec)” → “Apache-2.0 (new spec and code contributions; transitioning from MIT, un-relicensed MIT contributions remain MIT); docs CC-BY-4.0” source
    • Latest release first recorded as “v1.32.2 (2026-10-23) — TypeScript SDK; Python SDK v2.3.0 (2026-10-02); current spec revision 2026-07-28” source
    • MCP support first recorded as “yes — this is the MCP specification itself” source
    #270

Related systems

Referenced by (93)

  • Agent Router (formerly Envoy AI Gateway) integrates with — Agent Router docs have an MCP gateway capability page. (verified 2026-10-29)
  • agentgateway integrates with — agentgateway integrations docs have a MCP page. (verified 2026-10-29)
  • Alita depends on at runtime — Generalist agent with minimal predefinition and maximal self-evolution via MCP generation. Headline: 75.15% pass@1 and 87.27% pass@3 on GAIA validation
  • Alita-G depends on at runtime — Self-evolution from generalist to domain expert via MCP synthesis, abstraction, and curation into MCP Box.
  • Arize Phoenix integrates with — Arize Phoenix docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Auth0 for AI Agents integrates with — Auth0 for AI Agents docs have an "AI Agents & MCP" section (auth for MCP servers). (verified 2026-10-29)
  • AutoGen / AG2 integrates with — AG2 docs describe connecting agents to MCP servers as tools. (verified 2026-10-29)
  • Braintrust integrates with — Braintrust docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Chroma integrates with — Chroma's docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Cipher (byterover) (now ByteRover CLI) depends on at runtime — Opensource memory layer focused on programming agents — works with Cursor, Windsurf, Claude Code, Roo Code via MCP. Maintains a coding-context memory across sessions and across IDEs.
  • claude-brain depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Claude Code (Anthropic) depends on at runtime — adjacent-infrastructure cell: Anthropic API; MCP server ecosystem
  • Claude Code auto-memory depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Claude-CursorMemoryMCP depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • claude-mem depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • claude-supermemory depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Cline (harness) depends on at runtime — adjacent-infrastructure cell: OpenAI-compatible API; MCP
  • Cloudflare MCP server portals integrates with — Cloudflare MCP server portals docs: a portal exposes multiple MCP servers behind one MCP endpoint. (verified 2026-10-29)
  • Coalfire AI Operations depends on at runtime — On 2026-05-05 Coalfire launched Audit AI in its Compliance Essentials platform, letting customers' AI agents work on live compliance data via MCP and open APIs
  • codebase-memory-mcp (DeusData) depends on at runtime — adjacent-infrastructure cell: self-contained binary + SQLite WAL; MCP client (Claude Code/Codex CLI/etc.); no LLM lock-in
  • Cognee MCP depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • context-mode depends on at runtime — Sandboxes tool output (98% reduction), persists session memory, and enforces routing across 17 platforms via MCP + hooks.
  • Continue.dev depends on at runtime — adjacent-infrastructure cell: any OpenAI-compatible API; MCP
  • Continue.dev Memory MCP depends on at runtime — Memory is injected via MCP rather than native to the Continue core.
  • Coveo depends on at runtime — RAG-as-a-Service for AWS (Dec 2025) via hosted MCP server grounding Amazon Bedrock agents in enterprise knowledge.
  • CrewAI integrates with — CrewAI docs have an MCP section for using MCP servers as agent tools (stdio, SSE, streamable HTTP). (verified 2026-10-29)
  • Dapr Agents integrates with — Dapr Agents tools integrations include MCP Toolbox for Databases. (verified 2026-10-29)
  • Datadog Agent Observability (LLM Observability) integrates with — Datadog LLM Observability auto-instrumentation page lists a MCP LLM integration. (verified 2026-10-29)
  • Daytona integrates with — Daytona docs have a guide for running Model Context Protocol (MCP spec) with Daytona sandboxes. (verified 2026-10-29)
  • DBOS integrates with — DBOS integrations docs have a DBOS MCP Server page. (verified 2026-10-29)
  • Descope Agentic Identity Hub integrates with — Descope docs have a Model Context Protocol section (MCP SDKs, auth for MCP servers). (verified 2026-10-29)
  • Docker MCP Catalog, Toolkit & Gateway integrates with — Docker MCP Toolkit page: management interface to run containerized MCP servers and connect them to MCP clients. (verified 2026-10-29)
  • e2b integrates with — E2B docs have a Model Context Protocol (MCP spec) integration guide. (verified 2026-10-29)
  • engram depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Glama MCP integrates with — Glama MCP directory of Model Context Protocol servers. (verified 2026-10-29)
  • Golem integrates with — Golem docs have an MCP invocation page (expose agents as MCP servers). (verified 2026-10-29)
  • Google Agent Development Kit (ADK) integrates with — ADK docs have an MCP tools section for using MCP servers as ADK agent tools. (verified 2026-10-29)
  • Google Cloud Model Armor integrates with — Model Armor docs have an integration page for Google and Google Cloud MCP servers. (verified 2026-10-29)
  • Goose (Block) depends on at runtime — adjacent-infrastructure cell: LiteLLM for multi-model routing; MCP for tool integrations; Block-internal extensions (square/cash app workflows)
  • Graphiti MCP Server (Zep) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Hatchet integrates with — Hatchet "Hatchet Agent Tools" cookbook exposes Hatchet tasks as MCP tools. (verified 2026-10-29)
  • Haystack (framework) integrates with — Haystack integrations directory has a Model Context Protocol - MCP integration page ("Haystack Tool Integration with the MCP"). (verified 2026-10-29)
  • Helicone integrates with — Helicone docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Hindsight MCP depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • IBM ContextForge MCP Gateway integrates with — IBM ContextForge docs: MCP gateway and registry federating Model Context Protocol servers. (verified 2026-10-29)
  • Inngest integrates with — Inngest AgentKit docs: AgentKit "MCP as tools" guide. (verified 2026-10-29)
  • Keycard integrates with — Keycard docs have an MCP SDK page (OAuth for MCP servers). (verified 2026-10-29)
  • Kong AI Gateway integrates with — Kong has an AI MCP Proxy plugin. (verified 2026-10-29)
  • Kuzu depends on at runtime — Sub-3ms recall via MCP.
  • Langflow integrates with — Langflow integration page: MCP client and server. (verified 2026-10-29)
  • Langfuse integrates with — Langfuse's integrations directory has a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Letta / MemGPT integrates with — Letta Agent SDK docs cover connecting sessions to stdio, HTTP and SSE MCP servers. (verified 2026-10-29)
  • LiteLLM integrates with — LiteLLM docs describe its MCP gateway for exposing and calling MCP servers. (verified 2026-10-29)
  • LlamaIndex (framework) integrates with — LlamaIndex has an official tool integration package llama-index-tools-mcp in its repo. (verified 2026-10-29)
  • local-memory-mcp depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Lunar.dev MCPX integrates with — Lunar.dev MCPX product page: MCP gateway. (verified 2026-10-29)
  • mcp-knowledge-graph depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • mcp-memory (Puliczek) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • mcp-memory-service (doobidoo) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Mem0 MCP (official) depends on at runtime — MCP server that brings the Mem0 layer into any MCP-compatible agent — including Claude Code — without rewriting code.
  • Memobase depends on at runtime — Cross-tool memory passport for Claude / Cursor / MCP-compatible agents.
  • Merge Agent Handler integrates with — Merge Agent Handler page says it is installed as a remote MCP server and lists MCP connectors. (verified 2026-10-29)
  • Microsoft MCP Gateway integrates with — Microsoft MCP Gateway README: reverse proxy and management layer for Model Context Protocol servers. (verified 2026-10-29)
  • Microsoft Semantic Kernel integrates with — Semantic Kernel Python has an MCP connector for using MCP servers as plugins. (verified 2026-10-29)
  • Milvus integrates with — Milvus's integrations overview lists a Milvus + Model Context Protocol (MCP spec) integration tutorial. (verified 2026-10-29)
  • n8n (AI agent flows) integrates with — n8n built-in AI cluster node: MCP Client Tool node. (verified 2026-10-29)
  • Nango integrates with — Nango "MCP Auth" guide lets users connect to MCP servers through Nango. (verified 2026-10-29)
  • Neo4j integrates with — Neo4j's GenAI ecosystem docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • Obot integrates with — Obot docs describe its MCP gateway concept. (verified 2026-10-29)
  • Official MCP Memory server depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Official MCP Registry integrates with — Official MCP Registry: registry of Model Context Protocol servers run by the MCP project. (verified 2026-10-29)
  • Okta Cross App Access (XAA) integrates with — Okta Cross App Access page says XAA is the recommended way to connect to MCP servers in the enterprise. (verified 2026-10-29)
  • OpenAI Agents SDK integrates with — OpenAI Agents SDK docs have an MCP page for using MCP servers as agent tools. (verified 2026-10-29)
  • OpenAI Codex CLI depends on at runtime — adjacent-infrastructure cell: OpenAI API (Codex / o-series); MCP for tool extensibility; runs locally with TLS-only network egress
  • Opencode (SST) depends on at runtime — SST team's open-source terminal coding agent — TypeScript, multi-model, MCP-native.
  • OpenInference integrates with — The OpenInference repo README lists an OpenInference instrumentation package for Model Context Protocol (MCP spec). (verified 2026-10-29)
  • OpenMemory MCP depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Paragon ActionKit integrates with — Paragon ActionKit overview says capabilities are exposed to AI agents via its API or MCP (Paragon MCP Server). (verified 2026-10-29)
  • Phidata (now Agno) integrates with — Agno ships MCP tools (agno.tools.mcp) for connecting agents to MCP servers. (verified 2026-10-29)
  • Pieces for Developers (LTM) depends on at runtime — Long-term memory engine for developers — captures everything the user does (browser, IDE, terminal) on-device, exposes via MCP for any IDE/agent.
  • Pipedream Connect integrates with — Pipedream Connect docs have an MCP Servers page (Pipedream MCP for AI frameworks and LLMs). (verified 2026-10-29)
  • Pydantic-AI integrates with — Pydantic AI docs have an MCP client page for connecting agents to MCP servers. (verified 2026-10-29)
  • Pydantic Logfire integrates with — Pydantic Logfire integrations docs have a MCP page. (verified 2026-10-29)
  • RL Developer Memory depends on at runtime — adjacent-infrastructure cell: Model Context Protocol (MCP)-native architecture; logged contextual-bandit policy gates; static (11/11) and dynamic (10/10) integration test harness
  • Smithery integrates with — Smithery docs "What is MCP?" concept page: Smithery is a registry and host for MCP servers. (verified 2026-10-29)
  • smolagents (Hugging Face) integrates with — smolagents tools tutorial covers using tools from an MCP server. (verified 2026-10-29)
  • Strands Agents (AWS) integrates with — Strands Agents docs cover connecting agents to MCP tools. (verified 2026-10-29)
  • Stytch Connected Apps integrates with — Stytch Connected Apps docs have an MCP authorization overview guide. (verified 2026-10-29)
  • Superpowers episodic-memory plugin depends on at runtime — Claude Code plugin that indexes prior conversations at session end and exposes search/show tools via MCP. Distributed via obra/superpowers-marketplace
  • Temporal integrates with — Temporal integrations catalog lists MCP integration: call MCP tools, prompts and resources as durable Activities. (verified 2026-10-29)
  • TopQuadrant TopBraid EDG (now TQ Data Foundation) depends on at runtime — serves governed context to agents via MCP, a Python SDK and REST.
  • Weights & Biases integrates with — W&B Weave docs have a Model Context Protocol (MCP spec) integration page. (verified 2026-10-29)
  • WorkOS AuthKit for MCP integrates with — WorkOS AuthKit MCP docs: authorization for MCP servers. (verified 2026-10-29)