AgentHub
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AgentHubspawn a worker named Alice to refactor the auth module"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AgentHub
AgentHub is a local MCP agent-team runtime for coding projects. An external orchestrator (Cursor, Codex, Claude, a custom MCP client, etc.) spawns named workers, delegates scoped tasks, waits for results, and resumes sessions. The human watches a read-only board; they do not drive the team from provider tabs.
North star: docs/MUST-DO-DIRECTION.md
What you get
Piece | Role |
MCP server ( | Primary product contract — session lifecycle, workers, delegation, updates |
Daemon + HTTP | Same runtime for TUI board and automation |
Read-only TUI ( | Dynamic worker board; legacy operator UI behind |
| Durable mailbox, sessions, team state on disk |
Implementation: agenthub-daemon (TypeScript) + agenthub-tui (Rust).
Related MCP server: Orchestration MCP
Provider support (V1)
Provider | Level | Resume in board |
Codex |
| Yes — adapter-tested |
Cursor |
| Yes — adapter-tested headless |
Grok |
| No — use for scoped tasks; live two-turn resume not proven |
OpenCode |
| No — use for cost/model routing; permission server not wired |
Details: docs/PROVIDER-SUPPORT-MATRIX.md
Per-provider CLI evidence and orchestrator notes: docs/PROVIDER-KNOWLEDGE.md
Experimental providers: Grok and OpenCode may spawn and delegate, but AgentHub does not claim durable resume (runtimeCanResume: false). Prefer Codex or Cursor when restart-safe work matters.
V1 release status
Core V1 is release-ready when the local release gates are green: build, daemon tests, TUI tests, package validation, packed install smoke, and the final dogfood transcript.
Current status: docs/STATUS.md
Final dogfood: docs/V1-DOGFOOD-2026-06-06.md
Release notes: docs/RELEASE-NOTES-V1.md
Install
Requires Node.js 20+. No Rust/MSVC at install time.
Installer channel (irm / curl)
The live stoyanco.com channel currently publishes the Windows x64 artifact.
irm https://stoyanco.com/agenthub/install.ps1 | iexmacOS/Linux use the same channel after their platform artifacts are built and uploaded:
curl -fsSL https://stoyanco.com/agenthub/install.sh | bashMaintainer build/upload flow: docs/INSTALLER-CHANNEL.md
npm package
npm install -g @agenthub-mcp/cli
agenthub doctor
agenthub init .
agenthub mcpConnect your orchestrator to agenthub mcp (stdio MCP). Typical flow:
create_session → get_session_state → spawn_worker → delegate_to_worker
→ wait_for / get_updates → recover_session (after daemon restart)Target name | MCP tool |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also: agenthub_list_sessions, agenthub_get_runtime_manifest (includes providerCapabilities + knowledge doc paths).
Full orchestrator guide: docs/AGENTHUB-SKILL.md
Read-only board
agenthub launch .Starts the daemon and TUI board (worker tabs, ops queue, settings). Default UX is read-only observation — orchestration stays in MCP.
Requires a prebuilt TUI binary when installed from npm (
vendor/tui/<platform>-<arch>/).Legacy / debug (not V1 product path): provider-first tabs (
/debug on), Home slash orchestration, F2/F3 writer lock, conductor MCP tools. See docs/LEGACY-RETIREMENT.md.
Dev checkout
git clone <repo-url>
cd agenthub
npm install
npm run build
agenthub doctor
agenthub mcpCursor MCP (dev checkout)
This repo ships .cursor/mcp.json so Cursor loads AgentHub automatically for this workspace (bin/agenthub.js mcp with AGENTHUB_PROJECT=${workspaceFolder}). After npm run build, reload MCP servers in Cursor settings.
Smoke test (mock adapters, no provider credits):
npm run smoke:mcpWindows TUI builds need MSVC (npm run build:tui). See docs/RELEASE-CHECKLIST.md.
HTTP API (optional): agenthub daemon on port 4367.
Docs map
Doc | Purpose |
Current snapshot, tests, V1 verdict | |
Machine-readable support contract | |
CLI evidence, models, permissions, risks | |
MCP orchestrator workflow | |
Provider CLI flags | |
File-backed mailbox protocol | |
Build/test gates |
Adapter overrides (optional)
$env:AGENTHUB_CODEX_ARGS="-m gpt-5.4-mini"
$env:AGENTHUB_CURSOR_ARGS="--model composer-2.5"
$env:AGENTHUB_GROK_ARGS="-m grok-build-0.1"
$env:AGENTHUB_OPENCODE_ARGS="-m opencode-go/kimi-k2.6"See docs/CLI-FLAGS.md and provider knowledge files for launch templates and resume behavior.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/itsstoyan/agenthub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server