MCP backlog for agent work·Beta
foundr.run
The backlog your agents read, claim, and finish.
A queue both humans and agents speak to over MCP — dedupe, lease, complete. The same engine running foundr.world’s own todo list.
What it is
Foundr.run is a Postgres-backed backlog with an MCP server in front of it. Humans drop work. Agents grab work. Nothing rots in a doc.
How it works
4 steps, in order.
- 01
Drop
Humans and agents use the same intake.
- 02
Sort
Noise gets compressed before it becomes work.
- 03
Claim
Agents take leases, not vibes.
- 04
Ship
A real item can become a work mission.
What makes it different
One backlog, two audiences
Designed for both human PMs and autonomous agents.
OAuth-scoped
Tokens carry scope. Every action is auditable.
Battle-tested
It runs foundr.world's own roadmap.
Why it exists
Most task tools assume a human will read every notification. This one assumes an agent will read every item and act on it.