A file snippet for config.yaml that connects your first MCP server to Hermes Agent: a local file server that can see one folder and cannot write, plus the commands to test it.
You want Hermes to use an outside tool through the Model Context Protocol and want a first connection you understand, can test and can switch off again. Saves about 30 minutes
[SERVER_NAME] | e.g. notes; a short lowercase name, used in tool names and commands |
[FOLDER_PATH] | e.g. /Users/you/Notes; the full path of the one folder the server may see |
Run hermes mcp test after every change to an MCP block. It reports what the server really returned, which is much faster than guessing inside a chat why a tool is missing.
For a hosted MCP server, replace command and args with url: and the server's address, add auth: oauth, then run hermes mcp login with the server name once to sign in through your browser. That keeps tokens out of config.yaml.
Written for Hermes Agent v0.21.x. Check commands against your version with hermes --version. This site is independent and not affiliated with Nous Research.
Get the Hermes Starter Pack: 15 recipes for setup, SOUL.md, memory, skills, scheduled jobs, Telegram and approvals.
More free recipes: Limit Which Tools an MCP Server Exposes in Hermes · A Code Review Skill for Hermes Agent
Need the whole set? The Hermes Agent Cookbook has 100 recipes for $27.