MCP — Connect Hermes to Thousands of Tools
MCP — Connect Hermes to Thousands of Tools — easy-to-understand guide based on official docs
Think of MCP like a universal power adapter for your AI assistant — one plug that lets Hermes connect to almost any tool you already use, from GitHub to your local files.
What’s the Big Deal?
Normally, if you want Hermes to use a new tool, you’d have to build special code for it. That’s slow and tedious. MCP (Model Context Protocol) changes the game: it’s a standard “language” that tools speak, so Hermes can understand them without custom work.
In plain terms: If a tool supports MCP, Hermes can use it. Period.
The Magic: One Config File
You don’t need to install anything extra — MCP support comes built-in with Hermes. The only thing you need is a simple config file.
Here’s how you connect a filesystem server (so Hermes can read and manage your folders):
# In ~/.hermes/config.yaml
mcp_servers:
filesystem:
command: "npx"
args: ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/projects"]
That’s it. Two lines of config, and you’ve given Hermes a new superpower.
Try It Right Now
- Start Hermes:
hermes chat
- Ask something like:
List the files in /home/user/projects and summarize the repo structure.
Hermes will automatically discover the MCP server’s tools and use them — no extra steps, no coding.
The One-Command Catalog
Hermes also ships with a curated catalog of pre-approved MCP servers (reviewed by the Nous team). These are safe, tested, and ready to go.
Use these commands:
hermes mcp # interactive picker (just press Enter)
hermes mcp catalog # see the full list as plain text
hermes mcp install n8n # install a specific one by name
The picker shows you what’s available and what’s already enabled:
n8n available Manage and inspect n8n workflows from Hermes
linear enabled Linear issue/project management (remote OAuth)
github installed (disabled) GitHub repo + PR tools
Press Enter on any row to install, enable, disable, or remove it.
What You Might Need
Some catalog entries ask for extra setup:
- API keys — Hermes will prompt you and save them securely in
~/.hermes/.env - OAuth login — For services like Google or GitHub, Hermes opens a browser for you to log in
- Remote servers — These connect over the internet, not your local machine
Don’t worry — Hermes walks you through each step at install time.
Pro Tip: Filter What Hermes Sees
You don’t have to expose every tool from a server. If a GitHub server has 50 tools but you only want 3, you can filter them in your config. This keeps Hermes focused and avoids confusion.
The Bottom Line
MCP turns Hermes into a universal remote for your digital life. Instead of waiting for new integrations, you can connect to thousands of existing tools in minutes.
Your practical next step: Run hermes mcp today, pick one server that solves a real problem for you (start with filesystem or github), and ask Hermes to do something with it. You’ll be amazed how easy it is.
📖 Official Docs
This article is based on the official Hermes Agent documentation:Official docs › user-guide/persistent-goals