技能潮 SkillTide 提交收录
官方说明7 个来源MCP 服务8 天前
bzdOS/hubd

bzdOS/hubd

Files-first project hub for humans and AI agents: shared journal, cr
在 GitHub 查看 ↗直链 · 无中转页
配置模板(请按你的客户端调整)
claude mcp add hubd -- npx -y hubd
这是根据仓库名生成的可粘贴骨架,命令行参数与包名请以该项目 README 为准。
★ 数取值
1 ★ · bzdOS/hubd · 取自 GitHub 搜索 API · (2026-10-16 20:00:20 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成
综合分 703 · 1 ★ · 7 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 bzdOS/hubd;我们收录于 2026-10-09;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

hubd

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

**The project tracker for teams of humans and AI agents — in plain files.**
You run two, three, five agent sessions — different tools, different vendors —
across your projects. Each one is brilliant, and each one has no idea the
others exist. You are the coordination layer: copy-pasting context,
re-explaining state, discovering on Monday what an agent did on Friday.
hubd replaces you in that job with the most boring technology available:
**plain files**. A shared headquarters for your whole team — agents *and*
humans: a card that says where each project stands, a journal of what everyone
did, tasks and queues every agent can wait on, heads that accept or reject their
workers' work, rules the team learns from its own turns, and a read-only board to
watch it all. All markdown and JSONL, in a folder you own; git carries it between
machines.
*hub serve on the demo hub. Each track's goal and work in hand; what its head
accepted, rejected, and why; what is blocked and on what; an escalation that waits
for your answer; a machine whose disk is nearly full.*
**Not a runner.** Orchestrators launch your coding agents and stream their
output — that's making coding faster. hubd manages the *work*: which projects,
what's next, who does it and when, what already happened. An orchestrator can
run your agents; hubd runs your projects. They compose.
Try it in a minute
hub demo writes an invented week of a small team into a folder of its own and
prints the commands to look at it: the board on a port beside your own,
hub board, hub agenda, the rules about to become laws, hub recall. Your own
hub is not read or written. Run it again for a fresh week; delete the folder when
you are done.
What it does, one level at a time
Start at the top; take the next level when you need it. Each level is a
tutorial of ten or fifteen minutes, with the real output
of every command.
| Level | What you get | Start with |
|---|---|---|
| **1. Memory** | An agent that opens a project knows where it stands: a card per project (a short digest, then sections), a journal of who did what, and a report at the end of each turn that files decisions, facts and next steps in their place. A session resumed after a compaction asks the hub, not its summary. | hub_context, hub report, hub recall, hub whereami |
| **2. Work and decisions** | Tasks across projects with owners, deadlines and dependencies; claims on paths that warn before two agents edit one file; the one task to do next, and why it won; the day split into what agents can do and what waits for you. | hub task add, hub now, hub agenda, hub plan, hub claim |
| **3. Addressable agents** | A queue per role: send it work, and an agent waiting on it wakes when something arrives, with no polling. An id names one message in the whole hub; an ack says it was done, not only read. In work mode a role's open tasks are its queue. | hub queue send, hub queue wait, hub_queue_ack |
| **4. Several machines** | One hub in a git repository that every machine syncs. Each node appends to logs of its own, so they never conflict; cards merge by section; hub doctor says when a node is behind or has gone quiet. | scripts/mesh-sync.sh, hub card merge-driver, hub doctor |
| **5. A team with roles** | Roles are cards with a rank: workers, a head for each project, a fleet role above the heads. The board shows each track, the head's verdicts, the escalations waiting for you, each machine's disks and relays. Each kind of role runs by one template of rules. | hub resource set, hub board, hub serve, hub prompts render |
| **6. A team that learns** | Each turn ends with a reflection: what it tried, what stood in the way, what rule would have helped. A rule that keeps coming back is a candidate; the head accepts it, and every role of the project gets it as a law. | hub reflect, hub reflect --promote |
| **7. A service** | The same hub over MCP on HTTP, token-gated and multi-tenant, for agents anywhere; each journal entry to a chat, a mail or a script as it lands. | hubd --http, hub watch --exec |
The words in this table — card, track, head, law — are defined in
来源
awesome · https://github.com/bzdOS/hubd
按领域浏览
MCP 服务
Traction
1 ★
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引