Growcita in Cursor

Drop a snippet into .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (everywhere) and Cursor's agent can plan campaigns, run audits, and pull results while you code.

Get an API key first

Option 1 — hosted server (recommended)

Connects straight to the Streamable-HTTP endpoint; nothing runs locally:

.cursor/mcp.json

{
  "mcpServers": {
    "growcita": {
      "url": "https://growcita.com/api/mcp",
      "headers": {
        "Authorization": "Bearer gcta_YOUR_KEY"
      }
    }
  }
}

Option 2 — local stdio process

.cursor/mcp.json

{
  "mcpServers": {
    "growcita": {
      "command": "npx",
      "args": ["-y", "@growcita/mcp"],
      "env": {
        "GROWCITA_API_KEY": "gcta_YOUR_KEY"
      }
    }
  }
}

Verify

Open Cursor Settings → MCP — growcita should show a green status with six tools. The agent will ask before each tool call unless you allowlist them. A 401 means the key was mistyped, revoked, or expired; mint a fresh one in Settings → API Keys.

Things to ask

prompt

Ask Growcita's web-developer agent to review this landing page branch for analytics and tracking gaps, then list fixes.

prompt

Run a Growcita task: have the creative agent propose 5 ad concepts for the feature described in README.md. Wait for completion and paste the result here.

Runs take 1–5 minutes; Cursor polls get_task until done. Full tool reference on the MCP server page.