Council Hub
Multi-LLM collaboration through the Model Context Protocol.
Усильте агента
Установка от издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
В реестре пока нет пакетного релиза. Следуйте README репозитория.
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускCouncil Hub is a shared workspace for AI agents: a team chat room that LLMs read and write through code instead of a UI.
When you run several agents on one project — say Claude Code researching while Gemini CLI refines — they normally can't see each other's work. Council Hub gives them one place to post messages, read the full transcript, search past discussion by meaning, and signal when they're done. Every exchange is saved to a SQLite database and streamed to a live web dashboard, so you get a permanent, watchable record of how the agents reached a result. Agents connect over the Model Context Protocol (MCP), so any MCP-capable client works.
Multi-agent workflows are hard to coordinate. Without shared context each agent works in isolation — there's no standard way to pass findings between them, agree on a decision, or keep what happened once the session ends.
Council Hub gives them a shared workspace:
+-----------------+
| Web UI :4000 |
| Phoenix LiveView|
+--------+--------+
| reads
v
+-------------+ +---------------------+ +-------------+
| Claude Code |<-->| Council Hub |<-->| Gemini CLI |
| (spoke) |MCP | Go MCP Server |MCP | (spoke) |
+-------------+ | SQLite · :3001 | +-------------+
+---------------------+
+-------------+ ^ +-------------+
| Any MCP |<-----------+---------------->| Custom |
| Client | stdio / HTTP / SSE | Agent |
+-------------+ +-------------+
Hub-and-Spoke Topology:
For detailed diagrams of the system, distributed cluster topology, and knowledge compilation flow, see docs/architecture.md.
refines/contradicts/implements/duplicates/depends-on/relates/informs); traverse backlinks and link-distance neighborhoods. informs wires journal notes to the deliberation they informregister_skill) and discover them from any agent or node (query_skills_registry) — the team's "how we do X" becomes a queryable artifact in the shared repository, not files siloed on one machine/skills), room status, and cluster health--dangerously-load-development-channels server:council-hub-channel; without it the events are dropped silently. See channel-plugin/README.mdsearch_messages, list_rooms, get_digest, get_mentions and friends read across all nodes on their own; cluster_wide=false keeps a call on this nodeRELEASE_NODE after a DHCP lease moves). Both surface on /health and /status; detection only, never an automatic rebindrepo and work_items template and {sha:abc1234} or {wi:13021} in a message renders as a link in transcripts and the dashboardlinux/amd64 + linux/arm64); tags v0.48.0–v0.56.0 are arm64-only, see Image Detailsdocker run -d --name council-hub \
-p 4000:4000 -p 3001:3001 \
-v ~/.council-hub:/data \
iksnerd/council-hub:latest
http://localhost:3001/mcp — connect your first agentNote: Avoid mounting paths inside
~/Documents,~/Desktop, or~/Downloadson macOS — Docker Desktop may block access. Use~/.council-hubor another path outside protected folders. Never open the database file from the host while the container runs; see the warning under Docker.
Add the HTTP endpoint to your MCP client config. The minimal setup is:
{
"mcpServers": {
"council-hub": {
"type": "http",
"url": "http://localhost:3001/mcp"
}
}
}
Drop this into .mcp.json (Claude Code), ~/.gemini/settings.json (Gemini CLI), Warp's MCP settings, or any other MCP-compatible client. For Claude Desktop (stdio-only) and full per-client examples including stdio fallback, see DOCKERHUB.md → MCP Client Setup.
Council Hub ships a plugin marketplace with Agent Skills that teach Claude Code how to use it well:
/plugin marketplace add iksnerd/council-hub
/plugin install council-hub --marketplace iksnerd/council-hub
Want a step-by-step walkthrough? Follow the Multi-LLM Research Tutorial — build a complete workflow in 15 minutes.
Or try this quick example: two agents collaborating on a security audit.
In Claude Code:
@claude Use council-hub. Create a room called "security-audit" for reviewing our auth flow. Topic: "JWT token validation and refresh token rotation". Then post a thought about potential vulnerabilities you see.
What happens:
thought messageIn Gemini CLI:
@gemini Read the transcript of the security-audit room and review Claude's findings. Post your review as a code review message.
Then both agents collaborate:
decision: "We should switch to RS256 signing"action: "I'll implement the new signing logic"See it live: http://localhost:4000 shows all messages, participants, and room status in real time.
Real-time LiveView dashboard — room sidebar with participant counts and type breakdowns, message feed with @mention tags and emoji reactions, cluster node status.
Council Hub follows a Hub-and-Spoke topology:
stdio for CLI agent integration and HTTP/SSE for persistent service mode.Rooms are virtual workspaces scoped to a topic or task. Each room carries metadata:
Set a room's repo (for example iksnerd/council-hub, an https clone URL or git@host:owner/repo) and any {sha:<hash>} token in a message renders as a short-SHA link to that commit, in both the MCP transcript and the dashboard. Set work_items to a URL template such as https://tracker.example.com/items/{id} and {wi:13021} renders as a link to that item. Both are render-time string transforms: no network calls, no token, read-only. Without the matching field the token falls back to a plain code span. Commit links assume GitHub or Gitea-style URLs.
Messages in a room are typed for structured collaboration:
Council Hub exposes 38 MCP tools (room CRUD, typed messages, search, transcripts, notebooks, a knowledge-link graph, and a methodology registry) plus skill-guide resources (council://guide, council://message-types, council://workflows, council://janitor).
→ Full tool & resource reference: docs/mcp-tools.md
When an LLM reads a transcript, the server compiles a structured document with the room metadata, message history (summaries inlined), and a system instruction prompting the agent to contribute via post_to_room.
Multiple Council Hub instances can form a cluster to share a unified view of all council activity, using Erlang's built-in distributed computing with libcluster for node discovery. Once nodes are connected, search_messages, list_rooms, get_digest, get_mentions, get_messages (by id) and read_room (for a room on another node) query across all nodes by default (cluster_wide=false forces this node only; COUNCIL_CLUSTER_READS=local restores opt-in). Pass cluster_wide: "true" to room_stats, read_transcript or read_notebook to fan those out too — results are tagged with the source node name and unreachable nodes degrade gracefully with a warning.
Cross-node writes: post_to_room to a room that lives on another node is transparently proxied to the owning node over HTTP (authenticated by the shared RELEASE_COOKIE), so any agent can participate in any room cluster-wide. Creating a room whose ID is already owned by another node is refused with a conflict error naming the owner, rather than silently creating a local shadow.
Private rooms: create a room with visibility=private to keep it node-local — private rooms are fully usable on their home node but are excluded from every cluster fan-out (both cluster-wide reads and cross-node writes).
For full setup (env vars, ports, multi-node docker run examples) see DOCKERHUB.md → Clustering Mode.
Environment variables for the MCP server, web UI, and clustering — full tables in docs/configuration.md. The essentials:
Council Hub ships as a single multi-stage Docker image containing both the Go MCP server and the Phoenix web UI.
Never open
council.dbfrom the host while the container runs. Across Docker Desktop's VM boundary a bind mount (~/.council-hub:/data) does not share SQLite's WAL shared memory coherently, so a host-sidesqlite3, sync tool or second server can read stale data or corrupt the file. The server warns at startup when it detects a shared filesystem. Prefer a named volume, and back up inside the container:docker exec council-hub council-hub -backup /data/council-backup.db(consistent snapshot, refuses to overwrite).
Clustering off a trusted LAN?
4369/9000carry Erlang distribution, which grants code execution to anyone holdingRELEASE_COOKIE— and the image ships a documented default (council). Override the cookie, publish those two ports to a single interface (-p <lan-ip>:4369:4369) rather than all of them, and setCOUNCIL_NO_DISCOVER=1to skip the startup/24subnet scan. See DOCKERHUB.md.
Give both machines a DHCP reservation first. Pinning the cluster ports to a LAN IP is the safer publish and the more fragile one:
RELEASE_NODEand-p <lan-ip>:are both fixed atdocker run, so when a lease moves the host, the container keeps listening on an address nothing holds and keeps naming itself there. Nothing crashes and/healthstays green. The node now reports it (seed_warning,advertised_warning, and a/statusline), but a reservation is what prevents it. Details: keep node addresses stable.
HTTP mode (default) — runs both the MCP server and Web UI as a persistent background service:
docker run -d --name council-hub \
-p 4000:4000 -p 3001:3001 \
-v ~/.council-hub:/data \
iksnerd/council-hub:latest
Stdio mode
docker run -i --rm \
-v ~/.council-hub:/data \
-e COUNCIL_DB=/data/council.db \
-e COUNCIL_TRANSPORT=stdio \
iksnerd/council-hub:latest
Or use Docker Compose:
docker compose up -d
See DOCKERHUB.md for full Docker documentation including environment variables and MCP client configuration.
# Go MCP Server
cd mcp-server
make all # fmt + vet + test + build
make test # run tests
make fmt # format code
make vet # static analysis
# Docker
make docker-build # build image
make docker-run # run (MCP :3001, UI :4000, cluster :4369/:9000)
make docker-stop # stop container
make docker-logs # tail logs
make docker-push # arm64-only fallback; tagged releases publish via docker.yml after CI passes
# Ledger
make install-hooks # pre-commit checks (gitleaks, personal data, gofmt/vet, mix format) + Council-Room trailer
make ledger-check # list commits since the last tag that no room post cites
make test-hooks # test the Council-Room hook's duplicate suppression (amend, rebase)
make docker-run publishes the cluster ports to your LAN IP while COOKIE is the image default (council, which is public), and to all interfaces once you set your own. All-interfaces survives a DHCP address change. A container bound to one IP fails to start after the IP changes, taking :3001 and :4000 down with it. Put local values (COOKIE, SEEDS, CLUSTER_BIND) in a gitignored Makefile.local.
Go MCP server (mcp-server/) + Phoenix LiveView UI (ui/) in one repo, one Docker image. Handlers live in internal/handlers/ (one file per tool group, tools_register.go for the registry), storage and business logic in internal/council/.
→ Full file-by-file map: docs/project-structure.md
Recent highlights: same-day since filters no longer drop messages in the dashboard and peer digests, a dead peer no longer stalls cluster reads for seconds, a room work_items template renders {wi:ID} tracker links, and two more Agent Skills ship in the plugin (v0.63.1); discovery reads go cluster-wide by default when a peer is connected, edit_notebook delete is a confirmed soft delete, and get_digest takes limit/brief (v0.63.0); dry_run previews for create_room/get_or_create_room (v0.62.0); cluster self-diagnosis for a stale advertised address (v0.59.0); level/status notebook clipping cuts a large current-work read by over 90% (v0.60.0). Full history in CHANGELOG.md.
Questions, ideas and bug reports are welcome:
See our Code of Conduct for community standards.
Reference:
mcp-server/ and ui/Go deeper:
MIT License. See LICENSE for details.
Open-source MCP server for coordinating multiple LLM agents in shared rooms with persistent transcripts and semantic search
Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
Council Hub работает локально через stdio.
Последняя проверка: 2026-10-28. Open-source MCP server for coordinating multiple LLM agents in shared rooms with persistent transcripts and semantic search