Support and data requests
Describe the problem. Keep private details private.
Check the common states below, or use your own GitHub identity to submit a private support request. Never paste authentication secrets into a public page or support request.
Support, privacy or deletion requests
Sign in to submit a request and review your own records in the account support area. Requests are stored persistently and accessible to you and authorized maintainers. Limit: three requests per person per day. Individual maintenance, with no promised response time.
These details are enough
- Host and version, steps to reproduce, and when it happened.
- A fixed error code and a screenshot with private information removed.
- For privacy or deletion, specify the data category, workspace and relevant record identifiers. Do not include original private content or member lists.
Please do not send
Passwords, API keys, verification codes, login tokens, session files, enterprise invitation codes, payment card information, government identifiers or protected health information. If a credential was exposed, revoke or rotate it with its provider first, then request assistance without the secret value.
Common states
Still loading, or no records shown
Loading or a failed request has not established whether records exist. Wait for identity verification, then retry manually as the interface suggests. A failed read is not an empty library.
Workspace access denied
Check the workspace chosen during authorization. Joining an enterprise requires a valid invitation. Accepting it neither switches the connection nor copies personal data. Authorize again to change workspaces.
A write has an unknown result
Keep the receipt and record identifier, then check through a read. Do not treat an unknown outcome as success or blindly resubmit it.
Does disconnecting delete the data?
Disconnecting or signing out ends the corresponding access. It does not delete saved data, long-term audit records or host chats. Submit a data deletion request through account support for verification.
Why is there no panel in my host?
The host must support MCP Apps and remote OAuth. A successful protocol connection does not prove that the host rendered the panel. Check the host capability and error code before requesting help.