Cheqq Docs
Guides

Integrations

Connect apps, custom OAuth apps, and MCP servers for use in Cheqq work.

Open Integrations

Open Integrations from Cheqq. The catalog has four tabs — Apps, Credentials, MCP Servers, and Channels — each showing supported connections and their current status. The Channels tab connects the Cheqq bot to Slack or Telegram; see Talk to Cheqq from Slack and Telegram.

The MCP Servers tab is a browsable catalog of 30+ providers — Linear, Notion, GitHub, Stripe, Atlassian, Figma, Airtable, and more. Each connects per-user through the provider's own authorization screen; Cheqq never sits between you and the provider with a shared client. Open servers like Hugging Face and DeepWiki need no account at all and connect in one click.

Connect a service

Choose an integration from the catalog and open its detail card.
Select Connect.
For OAuth integrations, a popup opens the provider's authorization screen — review what it's requesting and approve it there. For API-key or MCP integrations, fill in the inline form Cheqq shows instead.
Return to Cheqq and confirm the integration shows as Connected.

Only grant access you're comfortable using in chat, Wapps, and automations. If your browser blocks the popup, or you close it before finishing, the connect attempt simply resets — reopen it and allow the popup to try again.

Connect your own OAuth app or MCP server

Beyond the built-in catalog:

  • Custom App — register your own OAuth 2.0 client: app name, authorize/token URLs (must be HTTPS), client ID and secret, and optional scopes. Cheqq shows you the exact redirect URI to register with your provider. Changing the client secret later invalidates the existing connection and requires reconnecting.
  • Custom MCP — add a server by name and URL. Cheqq probes it, discovers its tools, and starts an OAuth or API-key flow automatically if the server requires one.

Reconnect or disconnect

Open the integration detail when a connection shows Needs reconnect — this happens when a token expires or the provider revokes it — and follow the reconnect action to renew authorization. Use Disconnect (or Remove, for MCP servers, which also deletes the registration) when Cheqq should no longer access the connection; its tools stop being available immediately.

Use a connection

Connected services make relevant actions available where the product exposes them. The tools available to a chat or automation depend on its current context and configuration — a connected service does not make every provider action available everywhere.

If authorization does not complete, allow the provider popup and see Troubleshooting.

Was this page helpful?