Connect Cursor

Connected to Cheqq, Cursor's agent can read and change your records and Wapps, build automations, and edit your Apps' code while you work.

Add Cheqq

{
  "mcpServers": {
    "cheqq": {
      "url": "https://cheqq.ai/api/mcp?tools=records,structure",
      "headers": { "Authorization": "Bearer cqk_your_key_here" }
    }
  }
}

If the file already has other servers, add cheqq beside them.

Keep the tool list short

Cursor works best with a small set of tools, and with every scope Cheqq offers well over a hundred. Narrow it in the address:

• ?tools= keeps only some groups: records, structure, workflows, documents and apps. For example, ?tools=apps for working on a site.
• ?wapp= adds one Wapp's own tools, which know its collections and fields. Combine it with ?tools=records to get just that Wapp's record tools and the general ones.

{
  "mcpServers": {
    "content-studio": {
      "url": "https://cheqq.ai/api/mcp?wapp=content-studio&tools=records",
      "headers": { "Authorization": "Bearer cqk_your_key_here" }
    }
  }
}

A key with fewer scopes also offers fewer tools: a tool the key can't use is never listed.

Keep the key out of your repository

A project's .cursor/mcp.json is easy to commit by accident. Put Cheqq in your user-level ~/.cursor/mcp.json instead, or add the project file to .gitignore. If a key ends up somewhere it shouldn't, revoke it in Settings → Developer and create another.

What to expect

Everything Cursor does is done as you and shows in each Wapp's history with "(API)", so you can undo it. Cheqq's own approval prompts don't appear over MCP, so keep Cursor asking before it runs tools, or leave delete and publish scopes off the key. See MCP tools.