Growcita in Claude Code

One command connects the hosted MCP server. From then on, Claude Code can list your workspaces, kick off agent runs, and pull results — without leaving the terminal.

Get an API key first

Option 1 — one command (recommended)

Adds the server to your user-level config so it's available in every project:

bash

claude mcp add --transport http growcita https://growcita.com/api/mcp \
  --header "Authorization: Bearer gcta_YOUR_KEY"

Option 2 — project-scoped .mcp.json

Commit this to a repo to share the connection with your team — each member supplies their own key via the GROWCITA_API_KEY environment variable:

.mcp.json

{
  "mcpServers": {
    "growcita": {
      "type": "http",
      "url": "https://growcita.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GROWCITA_API_KEY}"
      }
    }
  }
}

Option 3 — stdio via npm

Prefer a local process? The npm wrapper proxies stdio to the hosted endpoint:

bash

claude mcp add growcita --env GROWCITA_API_KEY=gcta_YOUR_KEY \
  -- npx -y @growcita/mcp

Verify

Run /mcp inside Claude Code — growcita should be listed as connected with six tools. 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 SEO agent to audit our production domain and summarize the top fixes as a checklist I can turn into issues.

prompt

Have the growth-marketer agent draft a launch plan for the feature in this branch, then save the result to LAUNCH.md.

prompt

List my running Growcita tasks and show the result of the last completed one.

Agent runs take 1–5 minutes; Claude Code polls get_task for you. Full tool reference on the MCP server page.