Hermes Official Plugins
Official Hermes Agent plugins: Home Assistant, Spotify, Blender, Snyk, Langfuse, sandboxes and importers for other agents
- 672 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Plugins reach external services: Home Assistant, Spotify, ElevenLabs, X and messaging platforms
- The Blender and TouchDesigner MCP servers run Python inside those programs, and terminal backends change where commands run
- The `mcp-serve` plugin hands your conversations from every connected platform to MCP clients
Install
- Works in
Manual install
hermes plugins searchBrowses the catalog. Installation runs `hermes plugins install <name>`, for example `spotify`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Plugins reach external services: Home Assistant, Spotify, ElevenLabs, X and messaging platforms
- The Blender and TouchDesigner MCP servers run Python inside those programs, and terminal backends change where commands run
- The `mcp-serve` plugin hands your conversations from every connected platform to MCP clients
This is third-party code. Review the repository files before installing.
What it does
Hermes Official Plugins is a repository of first-party plugins for Nous Research's Hermes Agent. The Hermes core holds the agent loop, memory, skills, the gateway and model routing, while anything tied to one product or vendor lives in a plugin. The plugin catalog opens with `hermes plugins search`, `hermes plugins info` and `hermes plugins install`, and the same plugins appear in Hermes Desktop under Capabilities. The repository collects integrations with Home Assistant and Spotify, MCP servers with skills for Blender, Snyk, TouchDesigner and Meshy, Langfuse tracing and sound and music generation through ElevenLabs. There are `bubblewrap` and `singularity` terminal backends that run commands in isolated containers, an `mcp-serve` plugin that hands Hermes conversations to MCP clients, and `agent-importers`, whose `hermes import-agent` command carries over OpenClaw, Claude Code, Codex CLI and Cursor setups. Each folder is a separate plugin with a `plugin.yaml` or `plugin.json` manifest. The catalog installs a plugin from its subfolder at a reviewed commit, so installing Spotify does not download Home Assistant.
Who it is for. Hermes Agent users who want connections to home automation, music, 3D editors and code scanning, and people moving to Hermes from another agent.
Good fit when
- Hermes should react to Home Assistant events and control devices over the REST API
- You want to scan code in Snyk: SAST, dependencies, container images and IaC straight from a conversation
- Every agent turn should be traced in Langfuse with token costs and tool calls
- Agent commands need isolating: the Hermes terminal runs in a `bwrap` sandbox or an Apptainer container
- Settings from Claude Code, Codex CLI or Cursor have to move into Hermes with one command
Not a fit when
- You do not use Hermes Agent: the plugins are written for its catalog and manifests
- You need a plugin from a vendor or community author, which live in their own repositories and enter the catalog after review
- You want a stable plugin rather than an experimental one: for example, the Claude subscription provider is marked experimental
Example request
Install the snyk plugin for Hermes and scan this repository for vulnerabilities, then show a summary by severityLimitations
The plugins work only with Hermes Agent, and some need a version at least as new as the manifest says, for example `advanced-delegation` needs 0.22.5 or later. External integrations need their own accounts and programs: Spotify Premium for playback control, Blender 5.1 or later, Node.js and a Snyk account, paid ElevenLabs credits. The Blender and TouchDesigner plugins run Python inside those programs, so trust only your own projects. The old standalone Home Assistant and Spotify repositories are archived, and after an address change you reinstall a plugin with `--force`.
How to disable. A plugin is disabled and removed with Hermes tools: the `hermes plugins` command for the plugin name or the Capabilities tab in Hermes Desktop. Delete the plugin folder and its environment variables by hand.
FAQ
How do I install a plugin from Hermes Official Plugins?
With `hermes plugins install <name>`, for example `hermes plugins install spotify`. `hermes plugins search` and `hermes plugins info` list and describe them. Hermes Desktop has the same under Capabilities.
How do official plugins differ from community ones?
Nous Research maintains the official ones in this repository, one folder per plugin. Vendor and community plugins live in their own repositories and enter the catalog after review.
How do I move settings from Claude Code into Hermes?
Install `agent-importers` and run `hermes import-agent claude-code`. The command also handles OpenClaw, Codex CLI, Cursor, Grok Bot and OpenBot.
How do I expose Hermes conversations to Claude Code or Cursor?
Install `mcp-serve` and connect the `hermes mcp-serve` command as a stdio MCP server. It exposes 10 conversation tools and the `--tools` flag adds 17 more.
Which plugins run code on my machine?
The Blender and TouchDesigner MCP servers run Python inside those programs, and `bubblewrap` and `singularity` change the environment where the Hermes terminal runs. `hermes plugins info` has the details.
Discussion
No questions or reviews yet.
Related
PluginsA pack of 19 plugins for Hermes Desktop: provider quotas, an iteration meter, a memory review queue, session management and RSS.
Agent Skills by moonlight-lupin
agent-skills
A library of skills and plugins for Hermes Agent covering research, media, scraping, documents, DevOps and agent upkeep.
A pack of practical skills for Hermes Agent: notes, trips, code security, browser automation and interface themes.
A Hermes Agent plugin with a Relay server: chat, voice and a terminal on Android, plus a desktop CLI for the agent's tools
hermes-dreaming stages Hermes memory and skill updates for review and writes them to live state only after approval.
Hermes Agent gains an opencode tool and hands coding tasks to the OpenCode team of agents.
README in short
The README explains the scheme: the Hermes core stays small, and anything tied to a product or vendor lives in plugins. It then describes the plugin catalog with search and install commands, two tiers of entries (official and community) and a list of plugins with their tools. The end has notes for people who used the built-in versions, the repository layout and the testing on Linux, macOS and Windows.