hcom-mcp
Click on "Deploy 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., "@hcom-mcplist managed agents"
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.
hcom-mcp
Control-plane MCP server for launching and supervising hcom-managed agents.
Why HTTP, not stdio
MCP servers typically run over stdio — the client spawns one server process per session. For a control-plane server that manages a fleet of agents, that's a problem: ten terminal sessions spawn ten isolated MCP processes with no coordination between them.
hcom-mcp runs as a single persistent HTTP server. Every terminal session, every MCP client, every agent talks to the same endpoint. One process, one source of truth for launches, registries, and lifecycle.
Related MCP server: GRACE Orchestrator MCP
Prerequisites
Install
git clone https://github.com/scchearn/hcom-mcp.git
cd hcom-mcp
npm install
npm run buildRun
Foreground (any OS)
HCOM_MCP_PORT=3111 node dist/index.jsListens on http://127.0.0.1:3111/mcp. Only localhost connections are accepted.
As a daemon
OS | Mechanism | Setup |
Linux | systemd user service |
|
macOS | launchd |
|
Windows | Task Scheduler or nssm | See |
Adjust the ExecStart/ProgramArguments path in the config to match where you cloned the repo.
MCP client configuration
Point any HTTP-capable MCP client at http://127.0.0.1:3111/mcp. Example for Claude Desktop:
{
"mcpServers": {
"hcom-mcp": {
"type": "http",
"url": "http://127.0.0.1:3111/mcp"
}
}
}Configuration
HCOM_MCP_PORT— HTTP port (default:3111)~/.hcom/mcp/config.json— presets, topologies, model catalogs, rescue allowlist~/.hcom/mcp/registry.json— managed agent registry.hcom-mcp.json— optional workspace overlay (see.hcom-mcp.example.json)
Rescue allowlist
unblock and spawn_and_verify only inject input into a blocked agent when
the pending launch_blocked detail matches a pattern in rescueAllowlist.
Defaults cover the known rescuable dialogs (workspace trust, permission mode,
model/provider picker); add patterns for new dialogs without a code release:
{
"rescueAllowlist": {
"enabled": true,
"patterns": ["trust this folder", "permission mode"]
}
}Workspace overlays extend the global patterns; they cannot remove the built-in defaults.
Skills
Install with:
npx skills add scchearn/hcom-mcpOperating guidance ships in skills/:
skills/using-hcom/SKILL.md— messaging, threads, transcripts, event watchingskills/hcom-agent-messaging/SKILL.md— agent-to-agent messaging patterns and gotchas
Tools
Tool | Purpose |
| Launch a headless agent (preset or bare harness+model) |
| Launch + gate on readiness, with optional guarded rescue of blocked agents |
| Launch multiple agents from a topology preset (optional |
| Adopt an external hcom agent into managed lifecycle |
| Stop or kill managed agents (one or more names, or a tag) |
| Guarded PTY rescue for a blocked agent (dry-run by default, config allowlist) |
| Supervise owned agents: poll snapshot with derived flags, or subscribe to life/blocked events |
| Resume a stopped agent or fork a session, registering ownership with a |
| Send an hcom message to one or more agents (request/inform/ack, optional reply_to) |
| List agents managed by this server |
| List all live hcom agents |
| List available models per harness (claude full IDs pass through unverified) |
| List configured agent presets |
| List configured topology presets |
| Inspect an agent's status, transcript, events, or terminal |
| Read agent transcripts, transcript search results, or transcript timeline |
| Get handoff context from a live or stopped agent |
| Remove stale registry records |
| Create a workflow thread |
| Query thread events |
| Server health and orientation (includes |
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP memory and agent control plane for durable conversations, jobs, and operations.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP-first control plane for ProAgentStore agents and private instances.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.60MIT
- FlicenseNot gradedqualityBmaintenanceMCP server orchestrating local multi-agent workflows with gated lifecycle, handoff events, and host-level continuation.-
- FlicenseAqualityCmaintenanceMCP server for controlling a Hermes agent deployment via its HTTP API, enabling health checks, log retrieval, task management, and deployment configuration from MCP clients.17-
- AlicenseNot gradedqualityAmaintenanceA self-hosted MCP control plane and protocol gateway that aggregates and manages multiple MCP servers, exposing them via stable, authenticated MCP endpoints for any client.01MIT