What problem does it solve? Setting up Model Context Protocol servers involves tricky configuration details — transport selection, credential injection, environment variable filtering, and auth failures that surface as cryptic 401s. This Skill provides the exact config patterns, CLI commands, and diagnostic workflows to get MCP servers running in Hermes and debug them when they fail. ## Core Features & Use Cases - Server Configuration: Add stdio and HTTP MCP servers to ~/.hermes/config.yaml via CLI or direct editing, with correct tool naming (mcp_{server}_{tool}) and timeout settings. - Secret Injection: Inject 1Password secrets into MCP headers using ${VAR} shell-style substitution via secrets.onepassword.env, avoiding hardcoded credentials. - Auth & Connectivity Debugging: Diagnose 401/405/timeout failures with curl-based JSON-RPC probes, distinguish proxy health from upstream OAuth failures, and detect empty-argument tool calls that silently no-op. - Use Case: You add a Gmail MCP proxy and hermes mcp test passes but every tool call returns 401. This Skill walks you through checking op CLI authentication, verifying ${VAR} resolution, and testing the endpoint directly with curl to isolate the failure layer. ## Quick Start Ask the agent to add an HTTP MCP server to Hermes config with a Bearer token injected from 1Password and verify the connection works.