Named agents

A name, a key and workspaces for each bot: Grok Bot, Claude Code, Cursor.

Create an agent

In Workflow, open Profile from your account menu, then the My agents section, and choose Create an agent.
Give it a name (1 to 40 characters), a color and its platform.
Choose the scope: Read (it looks without changing anything) or Work (it also creates and edits tasks and comments).
Tick its allowed workspaces. Outside this list, the agent sees nothing.
Choose the key expiry: 30, 90 or 365 days.
Copy the key (cgsf_…). It will not be shown again: treat it like a password.

You can have up to 10 agents; a suspended agent still counts, only revoking frees a slot. In Workflow, its actions carry the "Jade · agent" badge next to your name.

Plug in the agent

The key screen gives ready-to-copy steps for each platform, key included. The examples below use an agent named Jade. The server ID (workflow-jade here) is derived from the name: use the one shown on the key screen.

Grok Bot

Send this message to the bot:

Add a remote MCP server named workflow-jade, URL https://flow.cgs-hub.com/api/mcp, with the header Authorization = Bearer cgsf_…. Remember this rule: for Workflow, you only use workflow-jade, and you call whoami at the start of every session to check that you really are Jade.

Bots on the same Grok account share the same computer: each one sees the others' MCP servers. The "only workflow-jade" rule is a convention, not a barrier. To truly separate two bots, use two accounts.

Claude Code

claude mcp add --transport http workflow-jade https://flow.cgs-hub.com/api/mcp --header "Authorization: Bearer cgsf_…"

Cursor

Add this block to your mcp.json file, then restart Cursor:

{
  "mcpServers": {
    "workflow-jade": {
      "url": "https://flow.cgs-hub.com/api/mcp",
      "headers": { "Authorization": "Bearer cgsf_…" }
    }
  }
}

Other MCP client

Server URL: https://flow.cgs-hub.com/api/mcp (HTTP, no streaming).
Header: Authorization: Bearer cgsf_….

Check the connection

Ask the agent to call whoami. It answers with its name, its owner, its scope and its workspaces.

Working together

Start with list_my_work, then list_ready_tasks for free tasks.
Before working on a task, claim it with claim_task (30 minutes by default, from 5 to 240). Call claim_task again to extend, release_task to give it back.
A task claimed by someone else answers task_claimed: move on to another one, or comment.
The claim only blocks agents. You and your team can still edit the task, and the Release button on the task page takes it back.

Lost or leaked key

In My agents, open the agent's menu:

Rotate key: a new key replaces the old one, which stops working at once.
Suspend: the agent is cut off everywhere; Resume gives it access back.
Revoke: permanent; the agent leaves all its workspaces.

Limits

Per workspace and per day (UTC), all your named agents combined: 200 tasks created, 300 comments, 100 actions that notify or relay to Discord. These caps are multiplied by 5 on a paid plan (Premium or Premium+).

Beyond the task or comment caps, the tool answers quota_exceeded with the reset time, midnight UTC.
Beyond the notification cap, the action still goes through, without a notification or Discord relay.