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 five tabs: Apps, Channels, MCP Servers, Connections, and Mail 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.
Built in: web research
Some capabilities need nothing connected. The agent can always search the web, read a public page in full, list a site's pages, or crawl a site when a task needs that much coverage — in chat, without an account or a key.
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 catalog shows three states: Connected, Reconnect, and not yet connected (shown as Connect). A connection shows Reconnect when its token expires, the provider revokes it, or an MCP server asks you to sign in again — until you reconnect, Cheqq treats it as unusable.
Connections: one model for workflows and the agent
A Connection is a saved way of calling a REST API — base URL, how it authenticates, and any fixed headers. It is deliberately a single object shared by both halves of the product: a workflow's API call step selects a connection, and the endpoints you save on it load as tools your agent can call in chat. Anything you can automate against an API, you can also just ask for.
A connection authenticates in one of four ways: through an OAuth app you register, through a provider Cheqq manages, with a stored key, or not at all. Endpoints can be typed in by hand or imported from an OpenAPI spec.
Read-only by default
Every connection starts read-only. Writes must be enabled per connection, and in chat each request that changes something goes through tool approval — asked for in Manual, answered for you in Auto.
A connection's key only ever goes to that connection's own address. A request to anywhere else is refused before the key is read, and a redirect never carries it to another site.
Keys belong to the connection that signs with them rather than living in a list of their own, so rotating a key happens where the connection is. The one secret that isn't an API's key — an SMTP login — has its own tab, because sending mail from your own address is a different job from calling an API.
A provider Cheqq can't reach isn't offered
Some presets depend on credentials Cheqq holds at the platform level. Where one of those isn't in place, the preset is absent from the catalog entirely — along with any Wapp built on it — rather than offered as a connection that can't complete.
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. In chat, Cheqq runs in Auto by default and goes ahead without asking; switch to Manual to approve each call yourself — see Control tool approval.
Continue with Connect and manage integrations, or browse the catalog to see what each service can do.