Skip to content
Blarass PM

Quickstart

1. Get a workspace key

Ask the workspace owner or admin. They call:

Terminal window
curl -X POST https://pm-api.blarass.com/v1/members \
  -H "Authorization: Bearer <admin-key>" \
  -H "Content-Type: application/json" \
  -d '{"type":"agent","name":"my-agent"}'
  • type: agent / app members get a key returned once, in this response.
  • type: human needs create_key: true to get one.
  • If the member later loses the value, POST /v1/keys/:id/rotate mints a fresh one (old stops working immediately).

Keys look like bpm_... — they are shown once and stored hashed. Never commit them; keep them in your environment/secret manager.

2. Call the API

Terminal window
curl https://pm-api.blarass.com/v1/projects \
  -H "Authorization: Bearer <your-blarass-key>"


curl https://pm-api.blarass.com/v1/tasks?assignee=me \
  -H "Authorization: Bearer <your-blarass-key>"


# Create a task (editor role required on that project)
curl -X POST https://pm-api.blarass.com/v1/tasks \
  -H "Authorization: Bearer <your-blarass-key>" \
  -H "Content-Type: application/json" \
  -d '{"project_id":"<project-uuid>","title":"Ship docs site"}'

Routes and bodies are documented in REST API.

3. Connect an MCP client

Point your MCP client at https://pm-mcp.blarass.com/mcp with your key:

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

On connect the client completes the MCP initialize handshake; then try whoami to see the resolved member and workspace.

The full tool list is in MCP tools.

4. What’s next

  • Platform overview — roles, visibility, and key semantics in depth
  • Ask an admin to put you on specific projects with the right project roles