Developer docs

Build on GroZro

Everything the dashboard does is available programmatically. Three surfaces — a REST API, a CLI, and an MCP server — all authenticate with the same tenant API key.

Getting started

Create an API key in Dashboard → Settings → Developer access. The key is shown once — treat it like a password. Keys carry the scopes api:read, api:write, and mcp:use (all three by default).

REST API

Base URL: https://api.grozro.com. Pass the key as a Bearer token:

curl -H "Authorization: Bearer ak_…" \
  https://api.grozro.com/api/v1/growth/items?status=drafted

Machine-readable spec: GET /api/v1/openapi.json (no auth).
The same routes serve the web app with session JWTs — behavior is identical.

CLI

The grozro CLI drives the full drafting and approval loop from your terminal. Log in once with an API key; config lives in ~/.grozro/config.json.

grozro login --api-key ak_…       # store credentials
grozro queue                       # drafted items awaiting approval
grozro approve <id> [--body "edit"]
grozro reject <id> --reason "off-voice"
grozro batch --count 6 --focus "launch week"
grozro audit                       # analytics audit from synced metrics
grozro post <id>                   # post an approved item now
grozro calendar | grozro learnings | grozro whoami

Point it at a different stack with --api-url https://….

MCP

A Streamable-HTTP MCP server exposes GroZro's capabilities as tools for Claude Code, Cursor, and other AI clients. It requires a key with the mcp:use scope:

claude mcp add grozro --transport http \
  https://api.grozro.com/api/v1/mcp \
  --header "Authorization: Bearer ak_…"