Integrations
Understand how connected services, custom OAuth apps, and MCP servers make actions available to Cheqq.
Integrations connect apps, APIs, and MCP servers to Cheqq. The catalog is organized into three tabs: Apps, Credentials, and MCP Servers.
MCP is the primary path for most providers: each catalog MCP server authenticates per-user against the provider's own authorization server, so the access token is yours alone rather than issued to a shared Cheqq client. Open servers (no account required) connect in a single click. Once connected, a server's tools are available in chat, in AI workflow steps, and as individual workflow steps of their own.
Connections and capabilities
A connection grants Cheqq the access approved during setup — either through the provider's own OAuth screen (opened in a popup) or, for API-key and MCP-server integrations, a form you fill in directly. Relevant actions become available only in product contexts that expose them; connecting a provider does not make every one of its actions available everywhere.
Grant screens live with the provider
Cheqq's catalog doesn't display the specific scopes an integration requests — you review and approve them on the provider's own consent screen inside the popup.
Connection status
The Apps/Credentials catalog shows three states: Connected, Needs reconnect, and not-yet-connected (shown as Connect). A connection moves to "Needs reconnect" when its token expires or is revoked by the provider — until you reconnect, Cheqq treats it as unusable. MCP servers use a more detailed status: Pending, Connecting, Connected, Auth Required, Error, or Disconnected.
Bring your own OAuth app or MCP server
Beyond the built-in catalog, you can register a Custom App with your own OAuth client credentials, or add a Custom MCP server by URL. Both go through the same connect flow as built-in integrations once registered.
Permission awareness
Review provider permissions on the consent screen before connecting a service, and disconnect access you no longer need. Agent mode and activated workflows may use connected actions when their configuration allows it.
Continue with Connect and manage integrations.