hermes-mcp
Related Servers
Alternatives to hermes-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables controlling a Hermes Agent instance from any MCP client, exposing a broad set of Hermes CLI operations over MCP Streamable HTTP with bearer auth.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that allows Claude Desktop and other MCP clients to delegate tasks to a local Hermes Agent for automation and persistent operations.49 PyPI61Apache 2.0
- FlicenseAqualityCmaintenanceMCP server that integrates Conductor Cloud with Hermes Agent, enabling Hermes to create sandboxed coding workspaces, dispatch tasks to developer agents (Claude, Codex, Cursor, ACP), and monitor or retrieve session results via MCP tools.8-
- AlicenseCqualityDmaintenanceMCP sidecar for Hermes Agent exposing operator tools (cron, skills, config, workspace) with tiered read-only/operator/owner modes and dry-run by default for safe local development.431MIT
- AlicenseNot gradedqualityBmaintenanceA control-plane MCP server for launching and supervising hcom-managed agents, running as a single persistent HTTP server to coordinate multiple sessions.1MIT
- AlicenseNot gradedqualityCmaintenanceBridges a self-hosted Hermes agent to remote MCP clients over Streamable HTTP, exposing kanban and vault tools via its REST API. It enforces strict security through Cloudflare Access JWT validation and prevents the agent from approving its own work.MIT
TDQS
Scored across 17 tools
Most tools target distinct resources and actions, but health/status and describe_api/detect_routes have overlapping purposes; descriptions generally mitigate confusion.
Mix of single-word nouns (health, status, logs, metrics) and verb_noun forms (get_task, send_task, set_config); the pattern is readable but not consistently applied.
At 17 tools, the set sits at the borderline upper end of typical scope; some redundancy (health/status, describe_api/detect_routes) adds bulk, but each tool has a clear role.
The surface covers lifecycle, monitoring, task management, configuration, and API introspection, with a request fallback for gaps; minor redundancy but no major missing operations.