Writbase - MCP Task Management for AI Agent Fleets

Created By
Writbase3 months ago
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. Deploy on Supabase free tier in 3 commands.
Overview

Features

  • 12 MCP tools — 5 worker + 7 manager tools
  • 6 permission types — can_read, can_create, can_update, can_assign, can_comment, can_archive
  • Project + department scoping — permissions per (project, department) pair
  • Optimistic concurrency — version-based conflict detection
  • Inter-agent delegation — assignment chains with depth limits and cycle detection
  • Webhook delivery — HMAC-signed Standard Webhooks on task events
  • Full provenance — append-only audit log for every change
  • Dynamic MCP schema — tool visibility and enums adapt per agent's permissions

Quick Start

  1. Deploy: supabase db push && supabase functions deploy mcp-server --no-verify-jwt
  2. Create an agent key in the dashboard
  3. Connect any MCP client (Claude Code, Cursor, VS Code)

Server Config

{
  "mcpServers": {
    "writbase": {
      "type": "http",
      "url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
      "headers": {
        "Authorization": "Bearer wb_<key_id>_<secret>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Writbase
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago