Connect Claude Code

With Cheqq connected, you can ask Claude Code for things like:

• "Add a Channel select field to the ideas in my Content Studio, with Blog, LinkedIn and Newsletter, and group the board view by it."
• "Import the CSV in this folder as records in my Leads collection."
• "Build an automation that emails me every Monday with last week's new invoices, test it, and save it."
• "Change the opening hours on my menu site, check it builds, and show me the diff."

Add Cheqq

claude mcp add --transport http cheqq "https://cheqq.ai/api/mcp" \
  --header "Authorization: Bearer cqk_your_key_here"

Claude Code now has tools for every Wapp in the workspace, your automations, documents and Apps, limited to what the key may do. Ask it to call cheqq_whoami and it will tell you which workspace it's in and what it's allowed to do.

Work on one Wapp

Add ?wapp= and the Wapp's slug to the address, and Claude Code also gets that Wapp's own tools: one for each thing you can do with its records and setup, named after it, such as content_studio_create_record. They read the Wapp's collections and fields as they are now, so Claude Code makes fewer wrong guesses.

claude mcp add --transport http content-studio \
  "https://cheqq.ai/api/mcp?wapp=content-studio" \
  --header "Authorization: Bearer cqk_your_key_here"

A Wapp's slug is in its address in Cheqq, or ask Claude Code to call cheqq_list_wapps. You can add one server per Wapp you work on.

Offer fewer tools

With every scope, Cheqq offers well over a hundred tools. Add ?tools= to offer only some groups: records, structure, workflows, documents and apps.

claude mcp add --transport http cheqq-records \
  "https://cheqq.ai/api/mcp?wapp=content-studio&tools=records,structure" \
  --header "Authorization: Bearer cqk_your_key_here"

cheqq_whoami is always there. An unknown group name is refused, so a typo doesn't leave Claude Code with no tools.

Share it with a project

To give everyone working in a repository the same setup, add the server with --scope project. Claude Code writes it to .mcp.json. Keep each person's key out of the file by reading it from their environment:

{
  "mcpServers": {
    "cheqq": {
      "type": "http",
      "url": "https://cheqq.ai/api/mcp?wapp=content-studio",
      "headers": { "Authorization": "Bearer ${CHEQQ_API_KEY}" }
    }
  }
}

Sign in instead of using a key

Leave the --header off and Claude Code can connect by signing in to Cheqq: run /mcp, choose Cheqq and authenticate. Cheqq asks which workspace to connect and what Claude Code may do, as it does for Claude.ai. It then appears under Connected apps in Settings → Developer.

Teach it the Cheqq way

Install the Cheqq skill too, and Claude Code knows how to work in Cheqq from the first request: it looks before it changes anything, checks an App builds before publishing, and asks you before it deletes.

What to expect

• Changes are yours. Everything Claude Code does is done as you, and appears in the Wapp's history with "(API)" at the end, so you can undo it.
• It may delete without Cheqq asking. Cheqq's own approval prompts don't appear over MCP. Keep Claude Code's permission prompts on for Cheqq's tools, or leave delete and publish scopes off the key. See MCP tools.
• One automation draft at a time. See Automations.