Connect an AI client to GrowFlux.

Create a workspace API key in GrowFlux, grant only the scopes your Agent needs, and add the connection to your MCP client. The full key is shown only once.

{
  "mcpServers": {
    "growflux": {
      "type": "http",
      "url": "https://mcp.growflux.io",
      "headers": {
        "Authorization": "Bearer gf_live_YOUR_KEY"
      }
    }
  }
}

Client configuration formats vary. Keep the endpoint and authorization header the same when adapting this example to Cursor, Trae, or another compatible client.

Do not grant write or publishing scopes to an Agent that only needs reporting and observation.

• Agent guide, project, workflow path, version, manifest, and delivery-route discovery.
• Saved content routines and coordinated run-group operation.
• Test & Tune quote, start, inspect, compare, and save-draft actions.
• Approved production run start and status/event observation.
• Review decisions, exports, publication metrics, and workflow validation.

Exact tool schemas are returned by MCP tools/list. Agents should discover them rather than relying on a copied static list.

MCP is currently an operating interface for existing GrowFlux projects. It does not yet create the first project or author a complete first workflow from zero. OAuth connections remain browser consent flows, and the MCP Worker acts as a protocol adapter rather than accessing the database directly.