# Support & contact How to contact us about the MCP server, and what to include in a report. ## Where to write Email **** 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](/api/v2/docs/mcp/security#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. > **Don't paste full requests or responses** > > A tool response can carry creator contact details and other personal data, and a request carries your `Authorization` header. Send the fields above instead, with personal and content data redacted. If we need a full payload to reproduce something, we’ll arrange a secure channel for it — never email one. > > If a bearer token has been shared anywhere, rotate it in the Integration tab first, then write to us. ## Before you contact us Check [Troubleshooting](/api/v2/docs/mcp/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](/api/v2/docs/guides/getting-started) and the [API reference](/api/v2/docs/queries) cover the same surface with field-level detail.