项目介绍
MCP 服务 · 2026-11-09 更新 · 本站尚未实测
WritBase 是面向 AI 智能体(Agent)集群的任务管理“控制面”。根据 README,它把任务存入 Postgres,而不是散落在文件和聊天记录里,并通过 Model Context Protocol(MCP)向智能体暴露任务读写、权限管理和审计能力。它适合由人类监督者管理多个智能体、需要共享任务台账和权限边界的团队。
README 将自身描述为 “MCP-native task management for AI agent fleets”,架构为 MCP 客户端 → Supabase Edge Function(Hono + MCP SDK)→ Postgres,另有 Next.js 16 仪表盘。它本身是一个可自行部署的服务与 MCP 服务器,不是可直接下载的工作流文件。
核心能力
点击能力名称查看输入、输出和原文依据。
- 持久任务注册表:任务保存在 Postgres 中,跨会话保留。
- 作用域权限:按项目、部门授予
can_read、can_create、can_update、can_assign、can_comment、can_archive六类权限。 - 来源审计:提供只追加的审计日志查询(
get_provenance),记录谁在何时做了什么。 - 智能体间委派:README 提到委派带深度限制与环检测;具体规则需查阅其概念文档。
- 动态 MCP 工具模式:工具可见性和参数枚举按智能体角色与权限调整。
- 并发与分页:基于版本号的乐观并发控制、游标分页、按智能体密钥限流与请求日志。
- 工具集:工人工具
info、get_tasks、add_task、update_task;管理工具manage_agent_keys、manage_agent_permissions、get_provenance、manage_projects、manage_departments、subscribe、discover_agents。
实际应用场景
适用场景
- 多个智能体与人类共同维护一份任务清单,例如 CI 失败时由机器人创建任务。
- 需要按项目/部门限制智能体读写范围,并保留操作审计记录。
- 由一个管理型智能体统一管理密钥、权限与项目,再由工人智能体处理具体任务。
- 需要通过 MCP 客户端(Claude Code、Cursor、VS Code/Copilot 等)直接操作任务系统。
安装与接入
README 给出两种方式。其一是 CLI 交互式部署(原文命令):
npx writbase init # Interactive setup — configures Supabase credentials
npx writbase migrate # Apply database schema
npx writbase key create # Create your first agent key
前置条件为 Node 18+、Supabase CLI 和一个 Supabase 项目(README 称免费层可用)。还需部署 Edge Function:
npx supabase functions deploy mcp-server --no-verify-jwt
其二是手动部署(原文命令):
依照仓库手动部署章节逐条执行克隆、安装依赖、关联 Supabase 项目、推送数据库与部署 Edge Function;具体参数保留官方原文。
部署后 MCP 端点为 https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp。随后创建项目与智能体密钥(wb_<key_id>_<secret>,仅显示一次),授予权限,再在客户端中添加该 HTTP 端点并附带 Bearer 密钥。客户端配置见仓库 docs/mcp-config-reference.md。
使用条件与限制
- 是否需要部署
- 需自行准备运行环境,具体要求见正文
- 是否需要注册
- 账号和认证要求见正文;未明确说明的项目仍待核验
- 是否需要 API Key
- 待核验
- 费用与额度
- 费用边界见正文,项目许可不代表模型或托管服务免费
- 所需权限
- 待核验
- 许可证与服务条款
- 待核验
权限费用与限制
- 每个智能体使用独立密钥,权限按项目/部门授予;管理工具仅管理型智能体可用。
- 存在按智能体密钥的请求限流和请求日志,具体阈值待核查仓库文档。
- Supabase 云托管存在免费层与付费层,配额以 Supabase 官方定价页为准;自托管成本由自身基础设施承担。仪表盘可部署到 Vercel,费用同样需核实。
- 本项目的模型能力不包含在内:MCP 只是协议层,所用大模型及其费用由用户自选客户端与模型决定,资料未列出特定模型。
- 仓库未提供托管 SaaS 端点,端点需自行部署 Supabase 后生成。
国内使用情况
网友核验 用户经验分享
与站长实测独立,不代表官方认证或本站已实测。
最近核验:暂无有效核验。参与人数按当前项目有效身份去重;不同核验项分别统计,不合并成用户总结果。仅统计审核通过且未过期的记录。
分项统计、有效期与样本量
| 核验项目 | 有效人数 | 成功 / 部分 / 失败 / 无法判断 | 成功率 | 最近核验 / 有效期 |
|---|---|---|---|---|
| 官方网站访问 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 7 天 |
| GitHub 仓库访问 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 7 天 |
| 安装与运行 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 官方服务国内连接 / MCP 连接 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 国内网络情况 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 7 天 |
| 国内模型兼容性 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 自定义 API | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 海外服务依赖 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 海外账号要求 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 中文界面 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 客户端兼容性 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
| 账号及费用信息 | 0 | 0 / 0 / 0 / 0 | 样本不足 | 暂无 / 30 天 |
成功率 = 成功 ÷(成功 + 部分成功 + 失败);无法判断不计入分母。至少 5 份可判断结果才显示成功率。账号、费用、海外依赖与语言等事实项,成功表示核查结论与资料吻合,具体观察另行统计;不表示免费或没有海外依赖。不同网络、客户端和版本的结果不能直接等同。
最近有效核验
暂无审核通过且未过期的网友核验。欢迎提交真实使用记录。
查看全部有效核验 →国内实测状态:国内可用性待核验。协议兼容和官方资料说明不等于国内网络可用。
- 官方网站访问
- 尚未实测 待核验
- GitHub 仓库访问
- 尚未实测 待核验
- 官方服务国内连接
- 尚未实测 待核验
- 国内网络情况
- 尚未实测 待核验
- 国内模型兼容性
- 尚未实测 待核验
- 自定义 API
- 尚未实测 待核验
- 海外服务依赖
- 尚未实测 待核验
- 海外账号要求
- 尚未实测 待核验
- 中文界面
- 尚未实测 待核验
- 国内最后核验时间
- 尚未实测
许可与国内使用
仓库 LICENSE 为 Apache License 2.0,README 亦标注 Apache 2.0;该许可仅覆盖仓库代码,不覆盖 Supabase 托管服务、第三方模型或其他外部依赖。README 未说明中国大陆网络可访问性、境内部署可行性或备案要求,均待核验。项目未声明归档或停止维护(仓库 metadata 显示 archived=false),但维护活跃度与长期支持需自行评估。
项目资料与来源
字段依据与待核验事项
access:来源确认 · npx writbase init # Interactive setup — configures Supabase credentials
project_type:来源确认 · MCP-native task management for AI agent fleets
原始 README(折叠技术参考)
<div align="center">
# WritBase
**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.
[](LICENSE)
[](https://github.com/Writbase/writbase/actions)
[](https://modelcontextprotocol.io)
<br/>
<img src="docs/assets/demo.svg" alt="WritBase MCP demo — agent creates a task and delegates to another agent" width="100%"/>
</div>
---
## Why WritBase?
AI agents need a shared, persistent task registry — not ephemeral in-memory state that vanishes between sessions. WritBase gives your agent fleet:
- **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
## Getting Started
### Option A: CLI Setup (recommended)
No repo clone needed. Just `npx`:
```bash
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](https://supabase.com/docs/guides/cli), a Supabase project ([free tier](https://supabase.com/pricing) works)
>
> Deploy the Edge Function: `npx supabase functions deploy mcp-server --no-verify-jwt`
>
> See the [CLI README](cli/README.md) for all commands.
### Option B: Manual Setup
<details>
<summary>Clone and deploy manually</summary>
```bash
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 dev`
>
> See the [Deployment Guide](docs/deployment.md) for Vercel hosting and self-hosted Supabase.
</details>
### 2. Create a project and agent key
Via the CLI (`npx writbase key create`), the dashboard, or a manager agent:
1. **Create a project** — e.g., `my-app`. Optionally add departments (`backend`, `frontend`, `devops`)
2. **Create an agent key** — name it, pick the `worker` role, save the key (`wb_<key_id>_<secret>` — shown once)
3. **Grant permissions** — `writbase key permit my-agent --grant --project my-app --can-read --can-create --can-update` (or via dashboard)
### 3. Connect your MCP client
<details>
<summary><strong>Claude Code</strong></summary>
```bash
claude mcp add writbase \
--transport http \
--url https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp \
--header "Authorization: Bearer wb_<key_id>_<secret>"
```
</details>
<details>
<summary><strong>Cursor</strong></summary>
Add to `.cursor/mcp.json`:
```json
{
"mcpServers": {
"writbase": {
"type": "streamableHttp",
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
"headers": { "Authorization": "Bearer wb_<key_id>_<secret>" }
}
}
}
```
</details>
<details>
<summary><strong>VS Code / Copilot</strong></summary>
Add to `.vscode/mcp.json`:
```json
{
"servers": {
"writbase": {
"type": "http",
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp",
"headers": { "Authorization": "Bearer wb_<key_id>_<secret>" }
}
}
}
```
</details>
<details>
<summary><strong>Windsurf / Claude Desktop / Other</strong></summary>
See the [MCP Config Reference](docs/mcp-config-reference.md) for all supported clients.
</details>
### 4. Use it
Ask your agent:
```
"Check my WritBase permissions" → calls info
"Create a task in my-app: Fix login bug" → calls add_task
"Mark it as in_progress" → calls update_task (with version for concurrency)
"Show all high priority tasks" → calls get_tasks with priority filter
```
### 5. Scale up
| Agent | Role | Scoped to | Use case |
|-------|------|-----------|----------|
| `ci-bot` | worker | `my-app/devops` — can_create | CI creates tasks on build failure |
| `triage-agent` | worker | `my-app` (all depts) — can_comment | Reviews tasks, adds notes |
| `ops-manager` | manager | (workspace-wide) | Manages keys, permissions, projects |
Each agent gets its own key with exactly the permissions it needs — nothing more.
> **Full walkthrough**: [Getting Started Guide](docs/quickstart.md) — permissions, departments, troubleshooting
## MCP Tools
### Worker Tools (all agents)
| Tool | Description |
|------|-------------|
| `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 |
### Manager Tools (manager agents only)
| Tool | Description |
|------|-------------|
| `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 |
## Features
- **Multi-tenant workspaces** — Signup auto-provisions an isolated workspace
- **Dynamic MCP schema** — Tool visibility and parameter enums adapt per agent's role and permissions
- **6 permission types** — `can_read`, `can_create`, `can_update`, `can_assign`, `can_comment`, `can_archive`
- **Project + department scoping** — Permissions are granted per (project, department) pair
- **Optimistic concurrency** — Version-based conflict detection prevents silent overwrites
- **Cursor pagination** — Efficient traversal of large task sets
- **Rate limiting** — Per-agent-key request throttling
- **Request logging** — Every MCP call logged with latency, status, and agent context
## Architecture
```
┌─────────────┐ ┌──────────────────┐ ┌──────────────┐
│ MCP Client │────▶│ Edge Function │────▶│ Postgres │
│ (Agent) │◀────│ (Hono + MCP SDK)│◀────│ (Supabase) │
└─────────────┘ └──────────────────┘ └──────────────┘
│
┌──────┴──────┐
│ Next.js 16 │
│ Dashboard │
└─────────────┘
```
- **Backend**: Supabase (Postgres + Edge Functions with Deno runtime)
- **Transport**: Streamable HTTP (MCP SDK)
- **Frontend**: Next.js 16 (App Router) + Tailwind CSS
- **Auth**: Supabase Auth (humans) + SHA-256 agent keys (agents)
## Deployment Options
| | Supabase Cloud (recommended) | Self-Hosted Supabase |
|---|---|---|
| Setup | `npx writbase init` → `npx writbase migrate` → done | Docker Compose (5 containers) |
| Cost | [Free tier](https://supabase.com/pricing): 500MB DB, 50K MAUs | Your infrastructure |
| Dashboard | Deploy to Vercel (free) | Self-host Next.js |
| Updates | Automatic platform updates | Manual |
| Control | Supabase-managed | Full |
See [docs/deployment.md](docs/deployment.md) for detailed setup instructions.
## Documentation
- [Getting Started](docs/quickstart.md) — Deploy, create an agent key, connect your MCP client, and manage tasks
- [CLI Reference](cli/README.md) — `npx writbase init`, `migrate`, `key`, `status`
- [Deployment Guide](docs/deployment.md) — Supabase Cloud, Vercel, and self-hosted setup
- [Core Concepts](docs/concepts.md) — Permissions, provenance, error codes, delegation
- [MCP Config Reference](docs/mcp-config-reference.md) — Client configs for Claude Code, Cursor, VS Code, Windsurf
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and PR guidelines.
## Security
See [SECURITY.md](SECURITY.md) for vulnerability reporting.
## License
Apache 2.0 — see [LICENSE](LICENSE).
历史前置条件说明(补充参考)
Node 18+;Supabase CLI;一个 Supabase 项目(README 称免费层可用);自行部署 Edge Function;智能体密钥 wb_<key_id>_<secret>;MCP 客户端(如 Claude Code、Cursor、VS Code/Copilot);所用大模型与费用由客户端决定,具体模型待核验;国内网络与合规可用性待核验
项目来源与清单版权许可
https://github.com/Writbase/writbase
整理来源:https://github.com/slavakurilyak/awesome-ai-agents
清单版权与许可:
MIT License
Copyright (c) 2024 Slava Kurilyak
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.