hermes-platform-mcp
Related Servers
Alternatives to hermes-platform-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceOperates a local Hermes Agent install from any MCP client over stdio, enabling task delegation, cron management, config changes, gateway restarts, health checks, and skill or session inspection without exposing the agent to the network.16MIT

GenieOS MCP Serverofficial
AlicenseAqualityCmaintenanceStdio bridge for editors to connect to the GenieOS MCP server, enabling AI agents to interact with GenieOS via Streamable HTTP transport.6416 npmMIT- AlicenseNot gradedqualityCmaintenanceActs as a stdio-to-HTTP proxy for Modus Brain, enabling MCP-compatible AI clients to access an organization's knowledge base in ModusOp.39 npmCryptographic Autonomy 1.0 (Combined Work Exception)
- AlicenseBqualityBmaintenanceEnables IDE and DeepSeek Harness agents to control an agent-kernel instance over stdio, exposing tools for auth, projects, assignments, runs, scheduler nudges, and executor settings.12MIT
- FlicenseNot gradedqualityCmaintenanceBridges Claude Cowork/Desktop to a local Hermes Agent, exposing hermes_delegate, hermes_check_run, and hermes_health tools for task delegation, status polling, and health checks.1-
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
TDQS
Scored across 12 tools
Each tool targets a distinct concept (analytics, briefs, signals, memory, context, feedback, ping) with clear descriptions that differentiate them. There is no overlap in purpose among the 12 tools.
Most tools follow a consistent 'noun_verb' pattern (e.g., analytics_get, briefs_get, signals_get). Only 'ping' deviates as a standalone verb, but it is a standard health-check tool and does not disrupt overall consistency.
With 12 tools, the set is well-scoped for a platform handling signals, briefs, feedback, memory, analytics, and connection verification. Each tool serves a clear purpose without being excessive.
The tool surface covers core operations (CRUD for signals and briefs, memory, analytics, feedback, context retrieval). Minor gaps like missing delete or update for briefs exist, but the main workflows are supported.