What problem does it solve?
It eliminates the manual setup required to connect external MCP servers and make their tools available inside Hermes Agent.
Core Features & Use Cases
- Automatic MCP server discovery at startup: Reads your MCP server configuration, connects, lists remote tool schemas, and registers them without a separate bridge workflow.
- First-class tool registration with safe naming: Exposes discovered tools to the agent as
mcp_{server_name}_{tool_name} and normalizes names for LLM compatibility.
- Transport support for stdio and HTTP: Runs local stdio-based MCP servers (e.g., via npx/uvx) or connects to remote HTTP/StreamableHTTP MCP endpoints.
- Security-minded execution: Filters inherited environment variables for stdio subprocesses and redacts credential-like values from tool errors to reduce leakage risk.
- Optional server-side LLM sampling: Supports MCP
sampling/createMessage so MCP servers can request model completions during tool execution.
Quick Start
Configure your MCP servers in ~/.hermes/config.yaml under mcp_servers, then restart Hermes Agent so it connects, discovers tools, and registers them as mcp_{server}_{tool}.