Writbase MCP Server

MCP-native task management for AI agent fleets with scoped permissions and provenance.

Remote serverstreamable-http

What is the Writbase MCP server?

Writbase MCP server exists for a simple reason — assistants are far more useful when they can act on Writbase directly instead of describing what you should do. MCP-native task management for AI agent fleets with scoped permissions and provenance.

What you get

A control plane for AI agents and human supervisors. Persistent task registry with scoped permissions, inter-agent delegation, and full provenance — all accessible via MCP.

  • One source of truth — — Tasks live in Postgres, not scattered across files and chat threads
  • Scoped permissions — — Each agent gets exactly the access it needs, nothing more
  • Full provenance — — Every change is recorded: who, what, when, and why
  • Inter-agent delegation — — Agents can assign tasks to each other with depth limits and cycle detection
  • MCP-native — — Agents connect via the Model Context Protocol, no custom integration needed

What the assistant can call

Once Writbase is connected, these are the calls the assistant has available:

  • info — Agent identity, permissions, and system metadata
  • get_tasks — List tasks with filtering, pagination, and full-text search
  • add_task — Create a task in permitted scope
  • update_task — Update a task with optimistic concurrency control
  • manage_agent_keys — Create, update, deactivate, rotate agent keys
  • manage_agent_permissions — Grant/revoke permissions with subset enforcement
  • get_provenance — Query the append-only audit log
  • manage_projects — Create, rename, archive projects
  • manage_departments — Create, rename, archive departments
  • subscribe — Register webhooks for task event notifications
  • discover_agents — Find agents by capability and skill

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Writbase's toolset — info, get_tasks, add_task and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Writbase; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Writbase's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Writbase.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the writbase mcp server does with a few real requests.

Available tools

ToolWhat it does
infoAgent identity, permissions, and system metadata
get_tasksList tasks with filtering, pagination, and full-text search
add_taskCreate a task in permitted scope
update_taskUpdate a task with optimistic concurrency control
manage_agent_keysCreate, update, deactivate, rotate agent keys
manage_agent_permissionsGrant/revoke permissions with subset enforcement
get_provenanceQuery the append-only audit log
manage_projectsCreate, rename, archive projects
manage_departmentsCreate, rename, archive departments
subscribeRegister webhooks for task event notifications
discover_agentsFind agents by capability and skill

How to install the Writbase MCP server

{
  "mcpServers": {
    "writbase": {
      "command": "npx",
      "args": ["-y", "writbase"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Writbase to info.
  • Use Writbase to get tasks.
  • Use Writbase to add task.

Frequently asked questions

It connects Writbase to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (info, get_tasks, add_task, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Writbase directly.