The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.
Hubd MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.
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.
Once Hubd is connected, these are the calls the assistant has available:
Code — the npm package. Update like any global CLI:Data — HUBD_DIR (default ~/.hubd): plain markdown + JSONL, yours to keepQueues — per-role message queues. Send work; an agent blocks on waitHarvest — one prompt turns any working dialog into project digests, tasksBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hubd's toolset — Code, Data, Queues and 1 more — is a fair guide to whether it matches your workflow. It is maintained by bzdOS; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Code | the npm package. Update like any global CLI: |
| Data | HUBD_DIR (default ~/.hubd): plain markdown + JSONL, yours to keep. |
| Queues | per-role message queues. Send work; an agent blocks on wait |
| Harvest | one prompt turns any working dialog into project digests, tasks |
{
"mcpServers": {
"hubd": {
"command": "npx",
"args": ["-y", "@bzdos/hubd"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.