Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"writbase": {
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
"type": "streamableHttp",
"headers": {
"Authorization": "Bearer wb_<key_id>_<secret>"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'writbase' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked writbase against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / productivity
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP Security Weekly
Get CVE alerts and security updates for io.github.Writbase/writbase and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP-native task management for AI agent fleets
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.
AI agents need a shared, persistent task registry — not ephemeral in-memory state that vanishes between sessions. WritBase gives your agent fleet:
No repo clone needed. Just npx:
npx writbase init # Interactive setup — configures Supabase credentials
npx writbase migrate # Apply database schema
npx writbase key create # Create your first agent key
That's it. Your MCP endpoint is live at:
https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp
Prerequisites: Node 18+, Supabase CLI, a Supabase project (free tier works)
Deploy the Edge Function:
npx supabase functions deploy mcp-server --no-verify-jwtSee the CLI README for all commands.
git clone https://github.com/Writbase/writbase.git
cd writbase && npm install
# Create a free project at supabase.com/dashboard, then:
npx supabase link --project-ref <your-project-ref>
npx supabase db push
npx supabase functions deploy mcp-server --no-verify-jwt
Optional dashboard:
cp .env.example .env.local→ edit with your Supabase URL + anon key →npm run devSee the Deployment Guide for Vercel hosting and self-hosted Supabase.
Via the CLI (npx writbase key create), the dashboard, or a manager agent:
my-app. Optionally add departments (backend, frontend, devops)worker role, save the key (wb_<key_id>_<secret> — shown once)writbase key permit my-agent --grant --project my-app --can-read --can-create --can-update (or via dashboard)claude mcp add writbase \
--transport http \
--url https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp \
--header "Authorization: Bearer wb_<key_id>_<secret>"
Add to .cursor/mcp.json:
{
"mcpServers": {
"writbase": {
"type": "streamableHttp",
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
"headers": { "Authorization": "Bearer wb_<key_id>_<secret>" }
}
}
}
Add to .vscode/mcp.json:
{
"servers": {
"writbase": {
"type": "http",
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
"headers":
... [View full README on GitHub](https://github.com/Writbase/writbase#readme)