What problem does it solve?
It solves the problem of manually wiring external tool servers into Hermes Agent by automatically connecting to MCP servers and registering their tools for immediate use.
Core Features & Use Cases
- Automatic tool discovery at startup: Hermes connects to configured MCP servers, calls list_tools(), and registers returned tools into the agent’s tool registry.
- Multiple transports (stdio and HTTP): Supports local stdio MCP servers launched via command/args and remote MCP servers via URL (including optional HTTP headers).
- Collision-free tool naming: Exposes tools with the naming pattern mcp_{server_name}_{tool_name} (hyphens/dots normalized) so multiple servers can coexist safely.
- Production-minded operations: Persistent background connections, reconnection with exponential backoff, per-tool-call timeouts, and optional sampling support for server-initiated LLM requests.
Quick Start
Add your MCP server(s) to ~/.hermes/config.yaml under mcp_servers, restart Hermes Agent, and then ask it to call a discovered MCP tool like “get the current time using the MCP time tool.”