AI and MCP

Connect Claude

Use Growth Dept Creator from Claude and other MCP clients with an API key.

Connecting

The MCP server is at https://creator.growthdept.ai/api/mcp. Use an API key as the bearer token. In Claude Code:

claude mcp add --transport http growth-dept-creator https://creator.growthdept.ai/api/mcp \
  --header "Authorization: Bearer gdc_..."

The server is stateless Streamable HTTP: one JSON-RPC request per POST, plain JSON answers, no sessions. GET /api/mcp answers 405.

Who can do what

A key acts as the person who created it, with that person's current role. Everyone can use the read tools. A full key created by a person can also make a few everyday changes; an owner or admin with a full key can make every change. A key with no person behind it only reads, and a key stops working when its person leaves the organization. The tool list a client sees already leaves out what the key cannot call.

Changes need a confirmation

A tool that changes something first answers with a preview and a confirmation_token. Nothing changes until the client calls the same tool again with the same arguments and that token. A token works once and expires after 10 minutes. Every change runs through the same operation as the REST API and is recorded in the brand's activity log.

Limits

60 units a minute and 1,000 an hour per key, separate from the REST API. A read costs 1 unit, a change 3, a heavy report 5. Past the limit, the tool answers with the seconds to wait.

Tools

See every tool with who can call it and what it costs.