What problem does it solve? Integrating external MCP servers into an agent normally requires custom bridge code and manual tool wiring. This Skill configures Hermes Agent's built-in MCP client so server tools are discovered at startup and registered as first-class tools alongside built-in ones. ## Core Features & Use Cases - Stdio and HTTP Transports: Run local MCP servers via npx/uvx commands or connect to remote StreamableHTTP endpoints with custom headers. - Automatic Tool Discovery: On startup, tools are discovered and registered with the mcp_{server}_{tool} naming pattern, then injected into all platform toolsets. - Security Controls: Environment variable filtering prevents credential leakage to subprocesses, and credential-like patterns are redacted from error messages. - Use Case: Add a GitHub MCP server with a personal access token in ~/.hermes/config.yaml, restart the agent, and immediately call tools like mcp_github_list_issues in any conversation. ## Quick Start Add an MCP server entry under the mcp_servers key in ~/.hermes/config.yaml and restart the agent to make its tools available.