{
  "$schema": "https://zambo.dev/ai-compatibility.schema.json",
  "title": "Zambo AI compatibility matrix",
  "last_reviewed": "2026-09-10",
  "canonical_mcp_url": "https://zambo.dev/mcp",
  "source_of_truth": "Live MCP tools/list and https://zambo.dev/api/health take precedence over this guide.",
  "status_definitions": {
    "tested": "Verified in the named client during the review period.",
    "partial": "A documented path exists, but client availability, plan, policy, or behavior must be confirmed by the user.",
    "planned": "No supported direct integration is represented."
  },
  "compatibility": [
    {
      "client": "Claude",
      "status": "partial",
      "integration": "Remote MCP connector where available; Desktop MCP configuration otherwise",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Connector availability and remote-MCP policy vary by Claude product and plan."
    },
    {
      "client": "ChatGPT",
      "status": "partial",
      "integration": "Custom MCP/app connection where exposed",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Developer mode, plan, and workspace policy may be required. This is not an official endorsement."
    },
    {
      "client": "Codex",
      "status": "planned",
      "integration": "No separately verified Codex setup path is advertised",
      "transport": "Not applicable",
      "auth": "Not applicable",
      "limitations": "Do not infer Codex support from ChatGPT support; use only if the current Codex host independently supports remote HTTP MCP."
    },
    {
      "client": "Grok",
      "status": "partial",
      "integration": "Custom connector only where the current Grok product exposes remote HTTP MCP",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Connector availability and plan policy must be confirmed. Use only the canonical zambo.dev MCP URL."
    },
    {
      "client": "Gemini",
      "status": "planned",
      "integration": "No documented direct Zambo MCP setup",
      "transport": "Not applicable",
      "auth": "Not applicable",
      "limitations": "Use documented REST only if the workflow can make HTTP requests; do not assume native MCP support."
    },
    {
      "client": "Cursor",
      "status": "partial",
      "integration": "Add the canonical URL to Cursor MCP settings",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Confirm current Cursor MCP UI and remote-server support."
    },
    {
      "client": "AI code assistants",
      "status": "planned",
      "integration": "No documented direct Zambo MCP setup",
      "transport": "Not applicable",
      "auth": "Not applicable",
      "limitations": "Feature availability varies by editor and organization policy."
    },
    {
      "client": "Windsurf",
      "status": "partial",
      "integration": "Add the canonical URL to Windsurf MCP settings",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Confirm current Windsurf MCP UI and remote-server support."
    },
    {
      "client": "Cline",
      "status": "partial",
      "integration": "Add the canonical URL in Cline MCP settings where remote HTTP servers are supported",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Cline version and remote transport support must be confirmed by the user."
    },
    {
      "client": "Telegram",
      "status": "partial",
      "integration": "Use https://t.me/zambodev_bot as a separate bot interface; this is not an MCP connection",
      "transport": "Telegram Bot API",
      "auth": "Telegram identity; capability-specific access rules still apply",
      "limitations": "The bot does not imply every web or MCP workflow is available in Telegram."
    },
    {
      "client": "Generic MCP client",
      "status": "partial",
      "integration": "Configure one remote server using the canonical URL",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Client must support remote HTTP JSON-RPC MCP; inspect tools/list for the live catalog."
    },
    {
      "client": "A2A agents",
      "status": "partial",
      "integration": "Authenticated, permissioned room coordination at https://zambo.dev/api/a2a; request a project-specific card from /api/a2a/card?project_id=<room_id>",
      "transport": "JSON-RPC 2.0 over HTTPS",
      "auth": "Project or member bearer capability",
      "limitations": "Supports durable message/send, tasks/get, and tasks/cancel plus Zambo Network evidence and approval flows. It is not unrestricted remote execution and does not yet provide streaming or push notifications."
    },
    {
      "client": "Browser agents",
      "status": "partial",
      "integration": "Use the agent's HTTP/MCP capability or human setup page",
      "transport": "HTTP JSON-RPC MCP or HTTPS REST",
      "auth": "Endpoint-dependent; basic MCP tier has no auth",
      "limitations": "Browser controls and cross-origin policy are agent-specific; do not expose credentials in prompts."
    },
    {
      "client": "Local models",
      "status": "partial",
      "integration": "Use an MCP-capable local agent host",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "A local runtime needs an MCP bridge/client; model tool-use reliability is outside Zambo's control."
    },
    {
      "client": "API agents",
      "status": "partial",
      "integration": "Use documented HTTPS REST endpoints or an MCP client library",
      "transport": "HTTPS REST and HTTP JSON-RPC MCP",
      "auth": "Endpoint-dependent; consult the endpoint contract",
      "limitations": "Rate limits, availability, and permitted side effects are returned by live endpoints."
    },
    {
      "client": "Coding agents",
      "status": "partial",
      "integration": "Use an MCP-capable coding client or HTTP integration layer",
      "transport": "HTTP JSON-RPC MCP",
      "auth": "No auth for the basic tier; X-Zambo-Key for eligible Pass access",
      "limitations": "Check remote-MCP support and review tool calls before side effects."
    }
  ]
}