native-mcp

Add an entry under mcp_servers in ~/.hermes/config.yaml with either a command (stdio) or url (HTTP), then restart the agent. It connects at startup, discovers tools, and registers them with the mcp_{server}_{tool} prefix.

Use stdio transport by setting command to npx or uvx with the package in args, for example command: uvx and args: ["mcp-server-time"]. Node.js is required for npx servers and uv for uvx servers.

Yes, HTTP/StreamableHTTP transport is supported by setting a url and optional headers such as Authorization. Your installed mcp package must include mcp.client.streamable_http, otherwise the server fails with an ImportError.

Check that servers are listed under the mcp_servers key with correct YAML indentation and that the mcp package is installed. Tools are prefixed as mcp_{server}_{tool}, so search for that pattern in startup logs.

Stdio subprocesses receive only a filtered baseline environment (PATH, HOME, XDG_*, etc.), not your full shell environment. Secrets must be explicitly passed via the env config key, and credential patterns are redacted from error messages.

The client automatically reconnects with exponential backoff (1s up to 60s cap) for up to 5 retries. If the server remains unreachable, it gives up, while other configured servers continue operating normally.