Connect Claude or ChatGPT directly to your Disqua workspace. Ask an assistant to catch you up on a channel, triage a ticket, or post an update — it reads and writes through your own account, with the permissions you grant.
On this page
Disqua runs a remote MCP server, so there is nothing to install and no key to copy. Add the connector URL in your assistant, sign in with your normal Disqua account, and pick which workspaces the assistant may reach.
https://mcp.disqua.com/mcp/sse endpoint on its own and Disqua registers the client automatically.
Not supported yet: clients that finish sign-in through a localhost callback
(for example Claude Code or Cursor). Disqua accepts only HTTPS redirect addresses, so these clients cannot
complete the connection today. For agents and scripts use an AI access token instead (see
Getting Started).
The assistant acts as you. It sees what your account can see and writes under your name — a message it posts is indistinguishable from one you typed. Grant only the workspaces you are comfortable handing over.
Thirteen tools, grouped by what they touch:
| Area | Tools |
|---|---|
| Orientation | list_workspaces, get_overview, list_channels |
| Messaging | read_messages, recap_channel, send_message |
| Helpdesk | list_tickets, get_ticket, create_ticket, reply_to_ticket |
| Follow-up | create_reminder |
| Retrieval | search, fetch |
In practice that covers most of what people ask an assistant for: “what did I miss in #support today?”, “draft a reply to ticket 412 and remind me to check it tomorrow”, “post the release notes to #general”.
Access is bounded twice over: by scope (what kind of action) and by workspace (where). Both are chosen on the consent screen and both are enforced by the API itself, not by the assistant — a token that reaches the API directly is bound by exactly the same limits. A tool aimed at a workspace outside the grant is refused; search results from outside it are never returned in the first place.
| Scope | Grants |
|---|---|
| workspaces:read | List your workspaces and their summary counts |
| channels:read | List channels you are a member of |
| messages:read | Read message history and generate channel recaps |
| messages:write | Post messages as you |
| helpdesk:read | List and open tickets |
| helpdesk:write | Create tickets and send replies |
| reminders:write | Set reminders for you |
| search:read | Search across messages, channels and tickets |
Granting a workspace does not widen what your account can do inside it. Channel membership, workspace role and helpdesk agent seat all still apply — the assistant simply cannot reach anything you could not reach yourself.
Every connected assistant is listed under Profile → Connected apps in the console, with the scopes and workspaces it was granted. Revoking takes effect immediately: the access token stops working on the next call and the refresh token is invalidated, so the assistant cannot quietly renew itself.
https://console.disqua.com/profile/appsYou should not need any of this to connect — assistants discover it on their own. It is here for anyone building a client by hand.
| Streamable HTTP transport | https://mcp.disqua.com/mcp |
| SSE transport | https://mcp.disqua.com/sse |
| Protected resource metadata | https://mcp.disqua.com/.well-known/oauth-protected-resource |
| Authorization server metadata | https://api.disqua.com/.well-known/oauth-authorization-server |
| Client registration | https://api.disqua.com/v1/oauth/register |
S256 is required — the plain method is not accepted.https://mcp.disqua.com; a token minted for another resource is rejected.