Published: 2026-06-02
Summary

Hermes MCP Update: Install AI Tools from a Reviewed Catalog in One Command

Chapters / key moments (click to jump — plays here on the page)

Hermes has shipped a significant MCP update: instead of manually digging through documentation, copying config files, and hoping nothing breaks, there is now a reviewed MCP catalog you browse like a menu and install with a single command. The update also adds granular per-tool action controls, automatic updates while Hermes runs, and the ability for Hermes itself to act as an MCP server for other agents.

Source video

"NEW Hermes MCP Agent Update" by Julian Goldie SEO — Watch on YouTube →

Key Takeaways

A new MCP catalog ships with Hermes — a curated, reviewed list of tools you browse and install without touching config files.
Installing a tool from the catalog takes one command and one Enter keystroke; no manual JSON editing or terminal restarts.
Per-tool action whitelisting lets you control exactly which actions each MCP is allowed to take — whitelist what you want, block what you don't.
The video says tools auto-update while Hermes runs. The Hermes docs say the opposite — MCPs are never auto-updated; re-run hermes mcp install <name> after a Hermes update.
Hermes can now expose itself as an MCP server, letting other agents call Hermes as a tool in their own pipelines.

Why This Matters

Before this update, connecting an MCP tool to Hermes meant finding the right documentation, locating and editing a config file, restarting Hermes, and debugging whatever broke. For non-technical users this was a significant barrier; even experienced users found it tedious for each new tool.

The catalog approach mirrors how package managers work: everything reviewed and available from one place, installed with a standard command. The security model is also improved — instead of an all-or-nothing tool connection, you now define a whitelist of specific actions each MCP can perform, limiting blast radius if a tool behaves unexpectedly.

New Capabilities Summary

MCP catalog: Browse reviewed tools in a menu; one command installs to your Hermes instance.
Action whitelisting: Per-tool permissions — specify exactly which tool actions are allowed.
Updates: not automatic, per the Hermes docs — re-run hermes mcp install <name> to refresh an entry.
Parallel safe tools: Tools flagged as safe can run in parallel, speeding up multi-tool workflows.
Hermes as MCP server: Other agents can now call Hermes as a tool, enabling multi-agent orchestration pipelines where Hermes handles specific subtasks.

Related Hermes Guides

Hermes Setup Guide — install and configure Hermes from scratch
Hermes MCP Tools Guide — full reference for connecting MCPs to Hermes
Hermes Security & Hardening — permission models and safe deployment practices

What you can actually set up from this

Extracted from the video's own transcript — the specifics the original summary left out.

Commands & Code Shown

hermes mcp

Purpose: Interactive picker for the reviewed MCP catalog (per the Hermes docs).

When to use: Browsing what is available.

hermes mcp catalog

Purpose: Plain-text, scriptable list of catalog entries.

When to use: Scripts, or messaging apps where there is no picker.

hermes mcp install <name>

Purpose: Install a catalog entry by name, e.g. hermes mcp install deepwiki.

When to use: Adding a tool; re-run it to refresh an entry after a Hermes update.

Gotchas

The video says catalog tools auto-update. The Hermes docs say the opposite: "MCPs are never auto-updated." Re-run hermes mcp install <name> after a Hermes update if a manifest version changed.
Use the per-tool allow/deny controls the video mentions to limit what each MCP server can do, rather than enabling every tool it exposes.