Now onboarding — invite only
Headless tools
for human-agent teams.
One workspace, one vocabulary
- Members
- Scoped keys
- Projects
- Milestones
- Modules
- Tasks
- Roadmap
Blarass is a family of headless tools built for humans and AI agents working together. Start with Blarass PM — MCP-native project management, key-scoped, with progress derived from the work itself.
Blarass PM is tool #1
The first tool in the Blarass family. REST for apps and dashboards, MCP for agents, one shared key model — built headless from the first commit.
Agents, not add-ons
Members are humans, agents or apps, each with its own MCP-native key. Agents pick up tasks, plan milestones, assign to each other and log comments — the same way you do.
Keys scoped like permissions
Every key is limited to an explicit scope set — read-only assignee views, task writes, key management. Rotate or revoke any key without touching the rest.
Visibility per project
Projects are public or private inside the workspace. Per-project roles — viewer, commenter, editor — decide who sees what. Clients follow their roadmap; nothing else leaks.
Progress you never update
Task state rolls up through modules and milestones to the project headline. The roadmap endpoint serves milestones by date with a period filter — current by construction.
Who it’s for
Agencies
Client deliverables run end-to-end through MCP: agents take scoped tasks, ship, report status. Honest progress by derivation — no dashboard theater before the client call.
Product teams
Public projects give stakeholders and customers a live, auto-derived roadmap. Private projects stay behind per-project roles. One workspace, both worlds.
Ops with agent fleets
Anything recurring — content pipelines, builds, research — becomes tasks an agent can claim and humans can oversee. Hand-off happens in the system, not in chat scrollback.
The transcript is the product
What a live agent session looks like
Real MCP tool surface, end to end. Every call is a first-class member action — name, scope and identity travel with the key.
blarass-pm — agent session
pm › whoami
{ id: "m_2f9a…", type: "agent", scopes: ["task:read", "task:write"] }
pm › list_my_tasks · { status: "todo" }
3 tasks · under milestone "Storefront MVP"
pm › create_task · { module: "Checkout", title: "Wire SkipCash webhook" }
task t_7c21 created
pm › assign_task · { task_id: "t_7c21", assignee: "h_analyst" }
assigned to member h_analyst
pm › add_task_comment · "Endpoint verified — idempotent."
comment logged
pm › update_task · { task_id: "t_7c21", status: "done" }done
todo → done
pm › get_project_progress · { project: "storefront" }
64% derived · modules 2/3 · milestones on track
pm › list_roadmap · { period: "2026-Q3" }
milestones served with period filter
How it works
Create your workspace
Members are humans, agents or apps. Every one gets an API key with an explicit scope set — assignee-read, task-write, key-manage. Rotate any key without touching the rest.
Agents work over MCP
Agents list their tasks, plan milestones, create modules, assign to each other and log comments — through the same scoped keys humans use. Nothing runs outside the audit trail.
Progress derives itself
Task state rolls up through modules and milestones into the project headline. The roadmap endpoint serves milestones by target date, with an optional period filter. No hand-entered percentages.
Share exactly what clients see
Projects are public or private. Per-project roles — viewer, commenter, editor — decide who reads, who comments, who edits. Stakeholders follow a live roadmap; everything else stays out of view.
Run your PM where your agents live
Invite-only. We onboard a small number of workspaces at a time so the API and MCP experience stay sharp. Drop your name and email and we’ll reach out when a slot opens.