F
licenseNot graded
qualityB
maintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.
-
hermes-agent-mcp
Related Servers
Alternatives to hermes-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables MCP-based interaction with a local Hermes Agent installation, providing file read/search, skill management, and optional sandboxed write, terminal, and memory tools.9MIT
- AlicenseNot gradedqualityBmaintenanceExposes ReadyAgents' local workflow engine and built-in tools over MCP stdio, enabling MCP clients to define, run, inspect, and approve YAML/JSON agent workflows.919 PyPIApache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a stdio MCP server for single-user local operation of the otaman platform, enabling agent orchestration, slash commands, and skill management within Claude Code without a remote bridge daemon.2AGPL 3.0
- 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 gradedqualityCmaintenanceEnables MCP agents to delegate tasks to a local Hermes Agent for terminal, file, browser, and coding operations, and schedule recurring jobs.MIT
TDQS
B3.4/5.0
Scored across 16 tools
Disambiguation4/5
Most tools target distinct concerns (cron vs config vs gateway), but hermes_status, doctor, config_get, and model_info all provide overlapping status/configuration information, requiring careful description reading.
Naming Consistency2/5
Naming patterns are mixed: single nouns (doctor, shell), noun_noun compounds (hermes_status, model_info), and noun_verb constructions (cron_create, config_get) appear without a consistent convention. Some tools have domain prefixes while others do not.
Tool Count3/5
At 16 tools, the set sits at the heavy end of the reasonable range. The breadth of domains (agent execution, gateway, cron, config, skills, sessions, shell) mostly justifies the count, but it feels slightly sprawling for a single server.
Completeness3/5
Core agent interaction and inspection are well covered, and cron has rich lifecycle support, but notable gaps exist: no cron_delete, no skill management beyond listing, and session support stops at listing with no resume or detail operations.
Maintenance
ActivityNo data
ResponsivenessNo issues