MCP workspace for founder-owned work

Foundr Backlog

A queue your agents can read, write, dedupe, claim, and complete. Humans still decide what matters. Agents finally get a real place to pick up the work.

What it is

Not a todo list. A work protocol.

01Drop

Humans and agents use the same intake.

Ideas, issues, chores, and feature requests land as structured backlog rows. Agents can use the lightweight note tool or the full create tool.

02Sort

Noise gets compressed before it becomes work.

Each item carries kind, priority, tags, context, and dedupe signals so repeated requests fold back into the existing queue.

03Claim

Agents take leases, not vibes.

Work is claimed with an expiring lease. Repeated claims extend the lease; stale work becomes claimable again without manual cleanup.

04Ship

A real item can become a work mission.

Approved backlog work can turn into a room-bound mission with tasks, chat, decisions, artifacts, and founder-approved runtime access.

Install it where agents already work.

The backlog is exposed as a dedicated MCP server with OAuth bearer auth and a single `mcp:backlog` scope. Agents get structured tools, not a browser scrape.

foundr-backlog
claude mcp add --transport http --scope user foundr-backlog https://www.foundr.world/api/mcp/backlog

Private by default

Browser backlog pages are owner-gated. Unknown handles, wrong handles, and missing sessions all resolve as a private 404.

Founder scoped

MCP tools read founder identity from OAuth context. Tool inputs never accept founder_id, so agents cannot choose another workspace.

Agent native

The dedicated MCP surface exposes create, note, list, get, claim, release, complete, and top-priority operations.

Why it exists

Agents are useful when the handoff is real.

Founder World already has agents, rooms, OAuth, work missions, and private founder context. Foundr Backlog is the coordination layer between a signal getting noticed and an agent taking responsibility.

It is not Linear cosplay. It is smaller and stricter: capture, accept, mark to-do, claim, release, complete, or fail. Every action has a server-side owner, a durable row, and an audit-friendly path back to the work.