Debuly
WritBase logo

WritBase

WritBase is an open-source, MCP-native task registry that gives AI agent fleets shared tasks, scoped permissions and an audit trail.

Open source

What is WritBase?

WritBase is a control plane for teams that run several AI agents alongside human supervisors. Instead of keeping work in chat threads or in-memory state, it stores tasks in Postgres and exposes them to agents through the Model Context Protocol, so a client such as Claude Code, Cursor or VS Code Copilot connects without custom code. Each agent gets its own key with up to six permission types (read, create, update, assign, comment, archive) granted per project and department. Every change is written to an append-only provenance log, agents can hand tasks off to one another subject to depth limits and cycle checks, and updates use version checks so concurrent edits do not overwrite each other. Setup runs through npx writbase init, migrate and key create against your own Supabase project, with an optional Next.js dashboard. The code is Apache 2.0 licensed, and the README says the Supabase free tier is enough to start.

Use cases

  • Share one task list across AI agents
  • Delegate tasks between agents
  • Restrict each agent to certain projects
  • Audit who changed a task and why
  • Let a CI bot create tasks on build failure
  • Supervise agent work from a dashboard

Who it's for

  • Agent developers
  • AI engineers
  • Platform teams

Why use WritBase

  • Tasks survive between agent sessions because they live in Postgres, not in chat history.
  • Scoped keys mean a CI bot or triage agent only touches the projects and actions it has been granted.
  • The provenance log records who changed what, when and why, which makes agent behavior reviewable.
  • Any MCP-capable client can connect, so there is no custom integration to write for each agent.
  • The Apache 2.0 license lets teams run and modify the code themselves.

WritBase features

  • Persistent task registry stored in Postgres
  • MCP endpoint served from a Supabase Edge Function
  • Six permission types set per project and department
  • Inter-agent delegation with depth limits and cycle detection
  • Append-only provenance log for every change
  • Optimistic concurrency with task versions
  • Cursor pagination and full-text task search
  • Per-key rate limiting and request logging
  • Manager tools for keys, projects, departments and webhooks
  • Optional Next.js dashboard for human supervisors

WritBase integrations

  • Supabase
  • Claude Code
  • Cursor
  • VS Code
  • GitHub Copilot
  • Windsurf
  • Claude Desktop
  • Vercel
  • Postgres

How to get started with WritBase

  1. Run npx writbase init to enter your Supabase credentials, then npx writbase migrate to apply the schema.
  2. Deploy the mcp-server Edge Function to your Supabase project.
  3. Create a project, optional departments and an agent key with the permissions that agent needs.
  4. Add the MCP endpoint and key to your client, such as Claude Code, Cursor or VS Code.
  5. Ask the agent to create, read and update tasks, and review changes in the provenance log or dashboard.

WritBase limitations

  • You host it yourself on a Supabase project
  • Setup needs Node 18 or newer and the Supabase CLI
  • Self-hosted Supabase runs as five Docker containers

WritBase pricing

WritBase is open source, so you can use and self-host it for free.

Prices can change and may vary by country or exclude tax. Check the official pricing page.

WritBase alternatives

The main WritBase alternatives listed on Debuly are CrewAI, LangGraph, Agent Swarm, CREAO, Essia and Lyzr. The table compares pricing and platforms; order is A–Z.

WritBase compared with its alternatives
ToolPricingStarting pricePlatforms
WritBaseOpen source—CLI, Self-hosted
Agent SwarmOpen source—Web, Self-hosted, Docker, Kubernetes
CREAOFreemium$20/moWeb, iOS
CrewAIOpen source—Web, API, CLI, Self-hosted
EssiaPricing unknown——
LangGraphOpen source—Self-hosted, Web, API
LyzrFreemium—Web, Self-hosted
  1. Agent Swarm

    Self-hosted, MIT-licensed system where a lead agent hands work to Docker-isolated Claude Code, Codex and other coding workers.

  2. CREAO

    AI agent builder that turns a chat request into agents that run on a schedule and work inside your tools.

  3. CrewAI

    Multi-agent framework and platform for building AI agent crews in Python or a visual editor, then deploying and monitoring them.

  4. Essia

    Orchestration platform that runs recurring business processes with AI agents and people, with governance and cost tracking

  5. LangGraph

    Low-level open-source orchestration framework and runtime for building stateful, long-running AI agents as graphs.

  6. Lyzr

    Enterprise AI agent platform for building agents in plain language, running them in production and governing them with audit trails and policies.

WritBase FAQ

Is WritBase open source?

Yes. The repository is licensed under Apache 2.0, and you deploy it on your own Supabase project.

How much does WritBase cost?

The software has no listed price. You pay for the infrastructure it runs on, and the README says the Supabase free tier (500MB database, 50K MAUs) works for Supabase Cloud setups.

Which AI clients work with WritBase?

The README gives setup steps for Claude Code, Cursor and VS Code with Copilot, and points to a config reference for Windsurf, Claude Desktop and other MCP clients.

Does WritBase have a dashboard?

Yes, an optional Next.js dashboard that you can deploy to Vercel or self-host, for human supervisors to manage projects, keys and tasks.

Can I self-host WritBase?

Yes. You can use Supabase Cloud or a self-hosted Supabase running in Docker Compose with five containers, as described in the deployment guide.

What are alternatives to WritBase?

Teams sometimes use Linear, Asana or Jira through their MCP servers, or build coordination with agent frameworks such as CrewAI and LangGraph.

Sources & verification

Facts on this page come from the official sources below, each with the date we read it. Written by Debuly; the vendor did not review this page.

SourceTypeAccessed
github.com/Writbase/writbaseofficial

Image credits

  • Logo: from avatars.githubusercontent.com · fetched · Vendor trademark, used only to identify the product; removed on request
  • Cover: none collected yet, so a generated tile is shown.

Spot an error? Report an issue with this listing. We also remove a logo or image on the owner's request.