Writbase
Coordinate tasks across multiple coding agents with MCP-native permissions and provenance instead of a shared Notion board the bots cannot write to safely.
Overview
WritBase MCP is an MCP server for the Build phase that manages tasks for AI agent fleets with scoped permissions and provenance.
What is this MCP server?
- MCP-native task management for multi-agent fleets with scoped permissions
- Provenance on task operations for accountability across agents
- Stdio via npx writbase plus optional Supabase streamable-http remote
- Requires WRITBASE_URL and WRITBASE_AGENT_KEY (wb_<key_id>_<secret>)
- npm package writbase at version 0.1.3
- Optional remote pattern https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp
- GitHub repository Writbase/writbase
Community signal: 6 GitHub stars.
What problem does it solve?
Several agents stepping on the same todo list without scoped keys turns into duplicated work, leaked secrets, and no record of who changed what.
Who is it for?
Indie operators orchestrating multiple Claude/Codex workers on one product who need a writable task plane built for agents.
Skip if: Single-agent hobby projects with a one-line TODO.md, or teams that only need human-centric Jira with no MCP surface.
What do I get? / Deliverables
After setup, agents create and complete tasks through MCP with permission boundaries and provenance you can trace per agent key.
- Fleet task queue manipulable via MCP tools
- Per-agent scoped permissions on task operations
- Provenance-backed task history for multi-agent runs
Recommended MCP Servers
Journey fit
Fleet task boards and scoped agent keys are built when you add agent-tooling infrastructure, not when you first sketch an idea. Agent-tooling is the shelf for MCP servers that manage how agents claim, complete, and audit work—not frontend components.
How it compares
Agent fleet task MCP, not a markdown planning skill or generic GitHub Issues integration.
Common Questions / FAQ
Who is WritBase MCP for?
Builders running agent fleets or parallel automation jobs who need scoped agent keys and MCP-accessible task state.
When should I use WritBase MCP?
During Build agent-tooling when coordination and provenance matter more than a static plan document.
How do I add WritBase MCP to my agent?
Set WRITBASE_URL and WRITBASE_AGENT_KEY, run npx writbase for stdio—or configure the Supabase streamable-http remote with Authorization Bearer wb_<key_id>_<secret>.