WritBase
VerifiedMCP-native control plane for persistent task tracking across AI agent fleets.
What is WritBase?
WritBase acts as a central task registry and permission layer for fleets of AI agents. Tasks are stored durably in Postgres rather than ephemeral memory, and every update carries full audit details including actor, timestamp, and reason.
Agents interact through standard MCP endpoints after receiving narrowly scoped keys. Delegation between agents includes cycle detection and depth limits, while managers can adjust permissions or create new projects without touching code.
It suits engineering teams running multiple specialized agents that need coordinated workflows, such as CI systems, code reviewers, and operations managers working inside the same workspace.
What you can build with WritBase
CI failure tracking
A CI bot receives a scoped key limited to the devops department and automatically creates tasks when builds fail.
Agent triage workflow
A review agent scans open tasks across departments, adds comments, and updates priority without write access to production projects.
Permission management
An operations manager uses a workspace-wide key to issue or revoke agent credentials and adjust department boundaries.
Install WritBase
npx writbase initnpx writbase init # Interactive setup — configures Supabase credentials
npx writbase migrate # Apply database schema
npx writbase key create # Create your first agent key- 1Run npx writbase init to configure Supabase credentials interactively.
- 2Execute npx writbase migrate to apply the required database schema.
- 3Create an initial agent key with npx writbase key create.
- 4Deploy the MCP edge function using the Supabase CLI.
- 5Add the generated endpoint and bearer token to your MCP client configuration.
WritBase: pros & cons
Pros
- +Single Postgres source of truth prevents agents from losing task context between sessions.
- +Fine-grained keys and department scoping reduce blast radius of compromised agents.
- +Built-in provenance and delegation rules improve auditability and safety.
- +Works directly with existing MCP clients like Claude Code and Cursor.
Cons
- –Requires a Supabase project and Node 18+ environment for initial setup.
- –Edge function deployment adds an extra operational step compared to local-only tools.
- –All task data lives in a single Postgres instance, creating a central dependency.
Frequently asked questions
No, the free tier is sufficient for most small fleets and testing.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…