Agent Compatibility Matrix
Every row is a source-backed fact with status, evidence, confidence, and risk level.
52 facts
Total compatibility facts currently available in the static graph.
Status
Risk
Compatibility types
runtime_deployment
22 source-backed facts.
server_host
20 source-backed facts.
framework_mcp
4 source-backed facts.
tool_permission
5 source-backed facts.
server_transport
1 source-backed facts.
Entity matrix
| Source | Claude Code | Claude Desktop | Codex | Cursor | Edge Worker Runtime | GitHub Copilot | GitHub MCP Server | Local Desktop Runtime | PostgreSQL MCP Server | Serverless / Container Runtime | Visual Studio Code | Windsurf | Workflow Orchestration Runtime |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AutoGen | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported AutoGen applications can be packaged as Python or .NET services and deployed in server or container environments. | not_recorded | not_recorded | not_recorded |
| Brave Search MCP Server | not_recorded | supported Brave Search MCP is part of the reference MCP servers and integrates with Claude Desktop. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Windsurf supports MCP configuration; Brave Search compatibility requires host-specific setup. | not_recorded |
| Claude Code | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Claude Code is a local developer host that runs against local project workspaces and configured command-line tools. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Claude Desktop | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Claude Desktop local MCP setup runs desktop-hosted MCP server processes through local configuration. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Cloudflare Agents SDK | not_recorded | not_recorded | not_recorded | not_recorded | supported Cloudflare Agents SDK is designed for Cloudflare's edge platform and Workers execution model. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Cloudflare Agents SDK can be paired with Cloudflare workflow-style orchestration, but exact state and retry semantics must be validated per workflow design. |
| Cloudflare MCP Server | verify_required Cloudflare MCP Server can support Claude Code workflows after authentication and account-scoped permissions are configured. | not_recorded | not_recorded | not_recorded | verify_required Cloudflare MCP Server belongs to Cloudflare platform operations, but whether it should run in an edge worker runtime depends on transport, credentials, and operational security constraints. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Cloudflare MCP Server can be considered for VS Code MCP workflows, but host support and Cloudflare account permissions must be verified before use. | not_recorded | not_recorded |
| Context7 MCP Server | not_recorded | not_recorded | verify_required Context7 MCP Server is useful for Codex-style coding workflows that need current library documentation, but the configured MCP transport must be verified. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Context7 MCP Server can support VS Code coding workflows where the host exposes MCP server configuration. | not_recorded | not_recorded |
| CrewAI | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required CrewAI tool workflows can be evaluated with MCP server access, but GitHub MCP transport, auth, and tool permission boundaries must be verified. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Database tool | not_recorded | not_recorded | verify_required Database tools can support Codex analysis workflows, but write permissions, production access, and destructive queries require human review. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Dify | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | adapter_required Dify is designed for server deployment; desktop runtime requires container adapter. | supported Dify supports PostgreSQL as a data source for RAG pipelines and dataset management. | supported Dify can be deployed as a containerized application on serverless and container platforms. | not_recorded | not_recorded | not_recorded |
| Documentation tool | not_recorded | not_recorded | supported Documentation retrieval tools are low-risk support tools for Codex coding workflows when they do not mutate local or remote systems. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Filesystem MCP Server | not_recorded | supported Claude Desktop supports local MCP servers, and the filesystem server is designed for local stdio operation with configured directories. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Filesystem MCP Server is a local stdio server pattern that fits a desktop runtime with explicit filesystem boundaries. | not_recorded | not_recorded | supported VS Code supports MCP server configuration, and the filesystem server exposes local file tools over stdio. | not_recorded | not_recorded |
| Filesystem tool | not_recorded | not_recorded | verify_required Filesystem write access can alter local project files and should be bounded by repository instructions and explicit user intent. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| GitHub MCP Server | not_recorded | not_recorded | verify_required GitHub MCP Server can be considered for coding-agent host workflows, but local host configuration, authentication, and transport support must be verified. | verify_required Cursor supports MCP configuration surfaces, but GitHub MCP server auth, transport, and permission scope must be verified in the target workspace. | not_recorded | supported GitHub Copilot documentation describes MCP context support and GitHub MCP workflows. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Google Agent Development Kit | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Google ADK is positioned for building and deploying agents, but runtime-specific process, secrets, and network assumptions must be verified for each target. | not_recorded | not_recorded | not_recorded |
| Haystack | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Haystack pipelines and agent workflows are suitable for server and container deployment patterns. | not_recorded | not_recorded | not_recorded |
| HTTP API tool | not_recorded | not_recorded | verify_required HTTP API calls can disclose data or trigger external side effects, so sensitive endpoints and credentials require explicit review. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Hugging Face MCP Server | not_recorded | not_recorded | not_recorded | verify_required Hugging Face exposes MCP integration patterns and Cursor can consume MCP servers, but deployment details should be verified per workspace. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| LangChain / LangGraph | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported LangChain and LangGraph applications commonly run in server, container, and workflow runtime deployments. | not_recorded | not_recorded | not_recorded |
| LlamaIndex | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported LlamaIndex agent and workflow applications can run as service or container deployments for data-connected agent workflows. | not_recorded | not_recorded | not_recorded |
| Mastra | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Mastra is a TypeScript agent framework that can fit serverless or containerized Node.js deployments, subject to persistence, workflow, and provider configuration. | not_recorded | not_recorded | not_recorded |
| Microsoft Agent Framework | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Agent Framework can orchestrate tool-using agents, while GitHub MCP Server exposes repository tools through MCP; integration should be verified per host and transport. | not_recorded | not_recorded | supported Agent Framework targets production-grade agent and workflow deployments that fit server and container runtime patterns. | not_recorded | not_recorded | not_recorded |
| Notion MCP Server | not_recorded | supported Notion MCP server is listed in MCP directory as compatible with Claude Desktop. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Notion MCP uses HTTP transport which is compatible with local desktop runtime. | not_recorded | not_recorded | supported Notion MCP can be configured via VS Code MCP settings file. | not_recorded | not_recorded |
| OpenAI Agents SDK | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Both entries participate in agent tool orchestration, but a production integration should verify transport, auth, and runtime assumptions. | not_recorded | not_recorded | verify_required OpenAI Agents SDK workflows can be deployed in server or container environments, but production runtime assumptions should verify process lifetime, secrets, network access, and tracing setup. | not_recorded | not_recorded | not_recorded |
| Playwright MCP Server | not_recorded | not_recorded | verify_required Playwright MCP can expose browser automation tools to MCP-capable hosts, but Codex host integration should be verified per workspace. | not_recorded | not_recorded | not_recorded | not_recorded | supported Playwright MCP Server runs browser automation through local process tooling and fits local desktop runtime workflows. | not_recorded | not_recorded | supported The Playwright MCP repository describes availability for GitHub Copilot agent workflows in VS Code. | not_recorded | not_recorded |
| PostgreSQL MCP Server | not_recorded | verify_required Postgres MCP Server can be configured for desktop MCP hosts, but credential storage, SQL scope, and network reachability must be verified. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Postgres MCP Server can expose database context to VS Code MCP workflows, but database credentials and query permissions require explicit review. | not_recorded | not_recorded |
| Pydantic AI | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Pydantic AI Python agents can be evaluated for server or container deployment, but packaging, process lifetime, and observability must be verified. | not_recorded | not_recorded | not_recorded |
| Semantic Kernel | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Semantic Kernel can run in application services and containerized enterprise stacks, but language runtime and connector dependencies must be validated. | not_recorded | not_recorded | not_recorded |
| Sentry MCP Server | verify_required Sentry MCP Server may be configured for Claude Code MCP workflows, but server command, authentication, and workspace permissions must be checked locally. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Sentry MCP Server can be considered for VS Code MCP-compatible workflows, but extension-level MCP support, authentication, and transport configuration must be verified. | not_recorded | not_recorded |
| Terminal tool | not_recorded | not_recorded | verify_required Terminal execution can mutate local files, install packages, or run long-lived processes, so commands should be bounded by task intent and workspace rules. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Vercel AI SDK | not_recorded | not_recorded | not_recorded | not_recorded | verify_required Vercel AI SDK can be used in edge-oriented application stacks, but provider, streaming, and runtime API compatibility must be verified for each deployment target. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Visual Studio Code | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported VS Code manages workspace-level MCP server configuration and local tool execution from a desktop IDE runtime. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Zed | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded | supported Zed is a local IDE host for coding workflows and can participate in local agent context through its AI and MCP configuration. | not_recorded | not_recorded | not_recorded | not_recorded | not_recorded |
| Source | Target | Type | Status | Risk | Evidence | Verified |
|---|---|---|---|---|---|---|
| AutoGen | Serverless / Container Runtime | runtime_deployment | supported | low | AutoGen applications can be packaged as Python or .NET services and deployed in server or container environments. | 2026-05-18 |
| Brave Search MCP Server | Claude Desktop | server_host | supported | low | Brave Search MCP is part of the reference MCP servers and integrates with Claude Desktop. | 2026-09-15 |
| Brave Search MCP Server | Windsurf | server_host | verify_required | low | Windsurf supports MCP configuration; Brave Search compatibility requires host-specific setup. | 2026-09-15 |
| Claude Code | Local Desktop Runtime | runtime_deployment | supported | medium | Claude Code is a local developer host that runs against local project workspaces and configured command-line tools. | 2026-05-18 |
| Claude Desktop | Local Desktop Runtime | runtime_deployment | supported | medium | Claude Desktop local MCP setup runs desktop-hosted MCP server processes through local configuration. | 2026-05-18 |
| Cloudflare Agents SDK | Edge Worker Runtime | runtime_deployment | supported | low | Cloudflare Agents SDK is designed for Cloudflare's edge platform and Workers execution model. | 2026-05-18 |
| Cloudflare Agents SDK | Workflow Orchestration Runtime | runtime_deployment | verify_required | medium | Cloudflare Agents SDK can be paired with Cloudflare workflow-style orchestration, but exact state and retry semantics must be validated per workflow design. | 2026-05-18 |
| Cloudflare MCP Server | Claude Code | server_host | verify_required | high | Cloudflare MCP Server can support Claude Code workflows after authentication and account-scoped permissions are configured. | 2026-05-18 |
| Cloudflare MCP Server | Edge Worker Runtime | runtime_deployment | verify_required | high | Cloudflare MCP Server belongs to Cloudflare platform operations, but whether it should run in an edge worker runtime depends on transport, credentials, and operational security constraints. | 2026-05-18 |
| Cloudflare MCP Server | Visual Studio Code | server_host | verify_required | high | Cloudflare MCP Server can be considered for VS Code MCP workflows, but host support and Cloudflare account permissions must be verified before use. | 2026-05-18 |
| Context7 MCP Server | Codex | server_host | verify_required | low | Context7 MCP Server is useful for Codex-style coding workflows that need current library documentation, but the configured MCP transport must be verified. | 2026-05-18 |
| Context7 MCP Server | Visual Studio Code | server_host | verify_required | low | Context7 MCP Server can support VS Code coding workflows where the host exposes MCP server configuration. | 2026-05-18 |
| CrewAI | GitHub MCP Server | framework_mcp | verify_required | medium | CrewAI tool workflows can be evaluated with MCP server access, but GitHub MCP transport, auth, and tool permission boundaries must be verified. | 2026-05-18 |
| Database tool | Codex | tool_permission | verify_required | high | Database tools can support Codex analysis workflows, but write permissions, production access, and destructive queries require human review. | 2026-05-18 |
| Dify | Local Desktop Runtime | runtime_deployment | adapter_required | medium | Dify is designed for server deployment; desktop runtime requires container adapter. | 2026-09-15 |
| Dify | PostgreSQL MCP Server | framework_mcp | supported | low | Dify supports PostgreSQL as a data source for RAG pipelines and dataset management. | 2026-09-15 |
| Dify | Serverless / Container Runtime | runtime_deployment | supported | low | Dify can be deployed as a containerized application on serverless and container platforms. | 2026-09-15 |
| Documentation tool | Codex | tool_permission | supported | low | Documentation retrieval tools are low-risk support tools for Codex coding workflows when they do not mutate local or remote systems. | 2026-05-18 |
| Filesystem MCP Server | Claude Desktop | server_host | supported | high | Claude Desktop supports local MCP servers, and the filesystem server is designed for local stdio operation with configured directories. | 2026-05-18 |
| Filesystem MCP Server | Local Desktop Runtime | runtime_deployment | supported | high | Filesystem MCP Server is a local stdio server pattern that fits a desktop runtime with explicit filesystem boundaries. | 2026-05-18 |
| Filesystem MCP Server | Visual Studio Code | server_host | supported | high | VS Code supports MCP server configuration, and the filesystem server exposes local file tools over stdio. | 2026-05-18 |
| Filesystem tool | Codex | tool_permission | verify_required | high | Filesystem write access can alter local project files and should be bounded by repository instructions and explicit user intent. | 2026-05-18 |
| GitHub MCP Server | Codex | server_host | verify_required | medium | GitHub MCP Server can be considered for coding-agent host workflows, but local host configuration, authentication, and transport support must be verified. | 2026-05-18 |
| GitHub MCP Server | Cursor | server_host | verify_required | medium | Cursor supports MCP configuration surfaces, but GitHub MCP server auth, transport, and permission scope must be verified in the target workspace. | 2026-05-18 |
| GitHub MCP Server | GitHub Copilot | server_host | supported | medium | GitHub Copilot documentation describes MCP context support and GitHub MCP workflows. | 2026-05-18 |
| Google Agent Development Kit | Serverless / Container Runtime | runtime_deployment | verify_required | medium | Google ADK is positioned for building and deploying agents, but runtime-specific process, secrets, and network assumptions must be verified for each target. | 2026-05-18 |
| Haystack | Serverless / Container Runtime | runtime_deployment | supported | low | Haystack pipelines and agent workflows are suitable for server and container deployment patterns. | 2026-05-18 |
| HTTP API tool | Codex | tool_permission | verify_required | medium | HTTP API calls can disclose data or trigger external side effects, so sensitive endpoints and credentials require explicit review. | 2026-05-18 |
| Hugging Face MCP Server | Cursor | server_host | verify_required | medium | Hugging Face exposes MCP integration patterns and Cursor can consume MCP servers, but deployment details should be verified per workspace. | 2026-05-18 |
| LangChain / LangGraph | Serverless / Container Runtime | runtime_deployment | supported | low | LangChain and LangGraph applications commonly run in server, container, and workflow runtime deployments. | 2026-05-18 |
| LlamaIndex | Serverless / Container Runtime | runtime_deployment | supported | low | LlamaIndex agent and workflow applications can run as service or container deployments for data-connected agent workflows. | 2026-05-18 |
| Mastra | Serverless / Container Runtime | runtime_deployment | verify_required | medium | Mastra is a TypeScript agent framework that can fit serverless or containerized Node.js deployments, subject to persistence, workflow, and provider configuration. | 2026-05-18 |
| Microsoft Agent Framework | GitHub MCP Server | framework_mcp | verify_required | medium | Agent Framework can orchestrate tool-using agents, while GitHub MCP Server exposes repository tools through MCP; integration should be verified per host and transport. | 2026-05-18 |
| Microsoft Agent Framework | Serverless / Container Runtime | runtime_deployment | supported | low | Agent Framework targets production-grade agent and workflow deployments that fit server and container runtime patterns. | 2026-05-18 |
| Notion MCP Server | Claude Desktop | server_host | supported | low | Notion MCP server is listed in MCP directory as compatible with Claude Desktop. | 2026-09-15 |
| Notion MCP Server | Local Desktop Runtime | server_transport | supported | low | Notion MCP uses HTTP transport which is compatible with local desktop runtime. | 2026-09-15 |
| Notion MCP Server | Visual Studio Code | server_host | supported | low | Notion MCP can be configured via VS Code MCP settings file. | 2026-09-15 |
| OpenAI Agents SDK | GitHub MCP Server | framework_mcp | verify_required | medium | Both entries participate in agent tool orchestration, but a production integration should verify transport, auth, and runtime assumptions. | 2026-05-18 |
| OpenAI Agents SDK | Serverless / Container Runtime | runtime_deployment | verify_required | medium | OpenAI Agents SDK workflows can be deployed in server or container environments, but production runtime assumptions should verify process lifetime, secrets, network access, and tracing setup. | 2026-05-18 |
| Playwright MCP Server | Codex | server_host | verify_required | medium | Playwright MCP can expose browser automation tools to MCP-capable hosts, but Codex host integration should be verified per workspace. | 2026-05-18 |
| Playwright MCP Server | Local Desktop Runtime | runtime_deployment | supported | medium | Playwright MCP Server runs browser automation through local process tooling and fits local desktop runtime workflows. | 2026-05-18 |
| Playwright MCP Server | Visual Studio Code | server_host | supported | medium | The Playwright MCP repository describes availability for GitHub Copilot agent workflows in VS Code. | 2026-05-18 |
| PostgreSQL MCP Server | Claude Desktop | server_host | verify_required | high | Postgres MCP Server can be configured for desktop MCP hosts, but credential storage, SQL scope, and network reachability must be verified. | 2026-05-18 |
| PostgreSQL MCP Server | Visual Studio Code | server_host | verify_required | high | Postgres MCP Server can expose database context to VS Code MCP workflows, but database credentials and query permissions require explicit review. | 2026-05-18 |
| Pydantic AI | Serverless / Container Runtime | runtime_deployment | verify_required | medium | Pydantic AI Python agents can be evaluated for server or container deployment, but packaging, process lifetime, and observability must be verified. | 2026-05-18 |
| Semantic Kernel | Serverless / Container Runtime | runtime_deployment | verify_required | medium | Semantic Kernel can run in application services and containerized enterprise stacks, but language runtime and connector dependencies must be validated. | 2026-05-18 |
| Sentry MCP Server | Claude Code | server_host | verify_required | medium | Sentry MCP Server may be configured for Claude Code MCP workflows, but server command, authentication, and workspace permissions must be checked locally. | 2026-05-18 |
| Sentry MCP Server | Visual Studio Code | server_host | verify_required | medium | Sentry MCP Server can be considered for VS Code MCP-compatible workflows, but extension-level MCP support, authentication, and transport configuration must be verified. | 2026-05-18 |
| Terminal tool | Codex | tool_permission | verify_required | high | Terminal execution can mutate local files, install packages, or run long-lived processes, so commands should be bounded by task intent and workspace rules. | 2026-05-18 |
| Vercel AI SDK | Edge Worker Runtime | runtime_deployment | verify_required | medium | Vercel AI SDK can be used in edge-oriented application stacks, but provider, streaming, and runtime API compatibility must be verified for each deployment target. | 2026-05-18 |
| Visual Studio Code | Local Desktop Runtime | runtime_deployment | supported | medium | VS Code manages workspace-level MCP server configuration and local tool execution from a desktop IDE runtime. | 2026-05-18 |
| Zed | Local Desktop Runtime | runtime_deployment | supported | medium | Zed is a local IDE host for coding workflows and can participate in local agent context through its AI and MCP configuration. | 2026-05-18 |