Skip to content

API Keys & Agents

Settings → Security → API Keys & Agents is how coding agents connect to GrowthOS. You mint a gos_ API key; the key inherits your user, org, and permissions. No npm install is required for hosted MCP.

From this page (or Connect coding agent on a sprint board) copy Cursor mcp.json or the Claude Code command, copy the sprint prompt, and download SKILL.md. Prod MCP URL: https://mcp.growthos.salesshuru.com/mcp with Authorization: Bearer gos_…

Free includes 1 MCP handoff per org; Pro and above are unlimited. API keys are available on Free; sprint and copilot features may be plan-gated.

  • Create, name, and revoke gos_ keys.
  • Copy MCP config while the secret is visible.
  • Download SKILL.md for the sprint loop, product-context, or Figma design skills.
  • Before asking an agent to work a sprint.
  • When bringing an existing product via agent explore.
  • When running Design in Figma with agent.
  • A signed-in user who can open Settings → API Keys.
  • Pro (or design-partner wedges) for unlimited handoffs and sprint AI where required.
  • Settings → Security → API Keys & Agents (/settings/security/api-keys)
  • Sprint board → Connect coding agent
  1. Open /settings/security/api-keys and create a key.
  2. Copy the Cursor mcp.json or Claude command while the secret is shown.
  3. Download SKILL.md into your code repo (or paste the in-app sprint prompt).
  4. In the agent chat, say: Run the GrowthOS sprint loop for project proj_…
  5. Revoke keys you no longer need.
  • The agent lists your tasks and can claim one after you confirm.
  • The key is stored only where you intended (mcp.json / Claude config).
  • Never commit the raw gos_ secret to a public repo.
  • Use the in-app prompt rather than inventing your own loop.
  • Sharing one key across the whole company instead of per user.
  • Expecting the agent to skip confirmation before claim or advance_sprint.