Feature Request: Expose Hermes Control Interface as a native MCP server - stdio transport - Related to Ticket 29

[githb-ac]

Feature Request

Expose the Hermes Control Interface as a native MCP server using stdio transport, so that any MCP-compatible agent or client — including Hermes Agent and Claude Desktop — can query and control the interface directly without opening the browser.

Why stdio Transport

• stdio is the standard transport in the Claude ecosystem and is natively compatible with Claude Desktop and other MCP clients
• stdio is required for compatibility with mcp2cli, which routes MCP tool calls without loading the full schema into context — delivering approximately 99% token usage savings on every turn. This is a significant cost and performance benefit for production swarms making frequent tool calls
• Aegis already implements this pattern successfully at ws://localhost:8080/mcp-audit, exposing an MCP server with tools that map directly to its internal API

What the MCP Server Should Expose

Every panel and action in the Control Interface should have a corresponding MCP tool:

1. Agent status — query agent status, quality scores per agent
2. Cost and token tracking — query 7-day cost, monthly pace, budget remaining
3. VPS health — query live CPU, RAM and disk usage
4. Hallucination alerts — list active alerts, dismiss alerts, set thresholds per agent
5. Team management — view teams and agents, roles, model assignments
6. Live event stream — query recent tool calls, errors, successes and warnings per agent
7. Model health — compare models by quality score and hallucination rate
8. Heartbeat status — check whether the agent process is alive and when it was last seen

Sequencing

Read-only tools should land first (VPS health, heartbeat, cost, event stream). Write tools (dismiss alerts, update thresholds) should follow once auth gating is confirmed, using the same authentication the Control Interface already uses for its existing write operations.

Why This Is the Right Architecture

Hermes Agent already speaks MCP natively. If the Control Interface exposes an MCP server, Hermes Agent can push data to it and query it directly using the same protocol it already uses for everything else — no new protocol work required on the agent side. Claude Desktop and any other MCP-compatible client can also query and control the swarm via natural language without opening the browser.

Reference

• Aegis MCP server (working example of this pattern): https://github.com/Justin0504/Aegis
• mcp2cli: https://github.com/knowsuchagency/mcp2cli