Cheqq Docs
Developers

Connect Claude.ai

Add Cheqq to Claude as a custom connector, sign in, and choose what Claude may do.

Connect Cheqq to Claude and ask about your work in plain words: "Which invoices are overdue, and who do I chase first?", "Add these three leads from my notes", "Run the weekly report and show me what it found". No key to copy: you sign in to Cheqq and approve what Claude may do.

Add the connector

In Claude, open Settings → Connectors and choose to add a custom connector.
Name it Cheqq and enter the address https://cheqq.ai/api/mcp. Leave the advanced OAuth fields empty.
Select Connect. Claude opens Cheqq; sign in if you aren't already.
On Connect Claude to Cheqq, choose the Workspace it works in and what it can do, then select Approve.

You're back in Claude with Cheqq connected. Turn it on for a conversation from the tools menu in the message box.

On Team and Enterprise plans, an owner may need to add the connector for the organization first; each person then connects their own Cheqq account.

Choose what Claude can do

The approval screen lists what Claude asked for, grouped as in Scopes. Claude asks for everything, so Cheqq starts with what a new API key gets ticked: see everything, add and change records, and run automations. Tick more only if you want Claude to delete, reshape your Wapps, build automations, edit documents or Apps, or publish.

The screen also says Cheqq hasn't verified the app, since apps register themselves, and shows the address your answer goes back to. Check it's Claude's before you approve.

Claude works in the one workspace you choose, as you. If you can only view that workspace, Claude can only look, whatever you tick.

Claude decides when to call a tool

Cheqq's own approval prompts don't appear when Claude acts. Claude marks tools that delete or publish, and you can set Cheqq's tools to ask before they run in the connector's settings. Leave delete and publish permissions unticked if you'd rather do those in Cheqq.

Work on one Wapp

Add ?wapp= and a Wapp's slug to the address, such as https://cheqq.ai/api/mcp?wapp=content-studio, and Claude also gets that Wapp's own tools, which already know its collections and fields. Add one connector per Wapp if you work across several. See MCP tools.

Disconnect

Open Settings → Developer in Cheqq. Connected apps lists every app you connected by signing in, in all your workspaces, with what each can do and when it was last used. Select Disconnect and Claude's access stops at once. To connect again, reconnect from Claude's settings and approve again.

Removing the connector in Claude stops Claude using it; disconnecting in Cheqq makes sure the access itself is gone.

If it doesn't connect

  • "This link can't be used" on the Cheqq page means the request didn't come from where it said it did. Start again from Claude's settings.
  • Claude asks you to connect again. The connection was disconnected in Cheqq, or Claude hadn't used it for 30 days. Connect and approve it again.
  • The tools you expected are missing. Each tool needs its permission: disconnect, reconnect and tick what it needs.

Was this page helpful?