Archive API docs
esc
    Jump to
    Getting started Token, first query, response Explorer Run queries in the browser items The connection most integrations start with Changelog Additions and deprecations

    Narrow by kind with a prefix — q: queries, m: mutations, t: types, g: guides, f: fields and arguments.

    Support & contact

    How to contact us about the MCP server, and what to include in a report.

    Where to write

    Email [email protected] for connection problems, unexpected tool behavior, rate-limit questions, and listing feedback. We reply within two business days.

    For vulnerabilities and suspected data exposure, use the same address with SECURITY in the subject line — see Report a vulnerability.

    What to include

    • The workspace ID (UUID or the numeric ID shown in the app).
    • The tool name and the timestamp of the failing call, with timezone.
    • The JSON-RPC request id, the HTTP status, and the isError flag or userErrors entries that came back.
    • Your MCP client and version (Claude.ai, Claude Desktop, Claude Code, or another client).

    That is enough to trace a call in our logs.

    Before you contact us

    Check Troubleshooting first — the symptom table covers 401s, missing tools, workspace resolution, empty results, and rejected writes, which between them account for most reports.

    For API-level questions unrelated to MCP, the guides and the API reference cover the same surface with field-level detail.