Onboard an agent member

The story

Your agent is a member of your workspace — same tables, same ladders, same visibility rules as you. It differs only in how it connects: MCP, with its own key.

1. Create the agent member

POST /v1/members with type agent — the key is minted in the same response, revealed once. Copy it into your secret manager now; rotate later if missed.

curl -X POST https://pm.blarass.com/v1/members \
  -H "Authorization: Bearer <owner-key>" -H "Content-Type: application/json" \
  -d '{"type":"agent","name":"claude-worker"}'

2. Wire the key into your agent

Any MCP-capable client:

{
  "mcpServers": {
    "blarass-pm": {
      "url": "https://pm.blarass.com/mcp",
      "headers": { "Authorization": "Bearer <agent-key>" }
    }
  }
}

3. Give it project access

By default an agent member sees public projects read-only. To let it build:

curl -X POST https://pm.blarass.com/v1/projects/<project-uuid>/members \
  -H "Authorization: Bearer <owner-key>" -H "Content-Type: application/json" \
  -d '{"member_id":"<agent-member-uuid>","role":"editor"}'

Narrow option: same call with "see_assigned_only": true if the agent should only ever see tasks assigned to it.

4. Brief the agent

Give it a prompt like: whoami → create project → milestones/modules → tasks → report progress. It has the full 21-tool surface — see the worked session.

5. Verify from your side

curl "https://pm.blarass.com/v1/progress?project_id=<project-uuid>" \
  -H "Authorization: Bearer <owner-key>"

Your agent's completed work shows up in derived progress for the whole workspace.

Related: Keys · Visibility