Manage Grok Bot setup manifests with the Admin API

Team Setup installs admin scripts on every team computer so standard tooling is present before members start work. The dashboard path is covered in Configure Grok Bot Team Setup. This guide covers the Admin API routes for the same manifests. Official references: Admin API → Grok Bot setup manifests; Grok Bot for teams and enterprises → Team Setup; Grok Bot security.

Team Setup is Enterprise only. Writes return 403 on plans that do not include it. Do not put secret values in setup scripts.

Authenticate with a team Admin API key (Basic auth, key as username, empty password). Reads need read:* or admin:*; writes need admin:*. Rate limit: 20 requests per minute per team per endpoint.

List manifests

curl -X GET "https://api.cursor.com/grok-bot/setup-manifests?limit=50" \
  -u YOUR_API_KEY:

Param	Purpose
limit	Results per page (default 50, max 100)
cursor	Opaque cursor from the previous nextCursor

Example response:

{
  "manifests": [
    {
      "id": "toolchain",
      "scripts": [
        { "id": "node", "setup": "mise install node@22", "check": "node --version" },
        { "id": "pnpm", "setup": "npm i -g pnpm" }
      ]
    }
  ],
  "nextCursor": null
}

Manifests are ordered by id. A team can store up to 100 manifests.

Create or replace a manifest

curl -X PUT https://api.cursor.com/grok-bot/setup-manifests/toolchain \
  -u YOUR_API_KEY: \
  -H "Content-Type: application/json" \
  -d '{
    "scripts": [
      { "id": "node", "setup": "mise install node@22", "check": "node --version" },
      { "id": "pnpm", "setup": "npm i -g pnpm" }
    ]
  }'

Field	Rules
Path manifestId	1–128 characters; starts with a letter or number; then letters, numbers, ., _, or -
scripts[].id	Same format as manifestId
scripts[].setup	Non-empty install command
scripts[].check	Optional verification command

A concurrent edit that races another writer returns 409. Audit log event type for save/delete: grok_bot_team_setup_manifest.

Delete a manifest

curl -X DELETE https://api.cursor.com/grok-bot/setup-manifests/toolchain \
  -u YOUR_API_KEY:

Success returns 204 No Content. A well-formed id that does not exist returns 404.

Private networks

To install your own networking client on every team computer and reach private services, pair Team Setup with Connect to private networks for Grok Bot. That path is separate from shared static egress ranges.

Pitfalls

• Putting API keys, passwords, or tokens inside setup / check strings — use secret request flows and connector auth instead.
• Expecting a new manifest to apply to an already-running computer without recreate/restart when the change depends on a fresh environment.
• Using a read:* key for PUT or DELETE — writes require admin:*.
• Hitting the 100-manifest ceiling without deleting unused keys first.