Hermes Agent

Availability

The pinned release documents this integration once listed; it does not establish that the catalog entry is available. Confirm the listing in the platform before using a catalog installation route. The upstream integration guide describes the submission and its constraints.

Use MCP without waiting for a listing

Install the binary with the local quickstart. Add this entry to your Hermes MCP configuration, preserving any existing servers:

mcp_servers:
  agentfeedback:
    command: agentfeedback
    args: [mcp]

The Hermes process must be able to find agentfeedback on PATH. This uses the local inbox unless the client is configured for a server.

Plugin route when listed

hermes plugins install agentfeedback

Hermes installs portable packages disabled; enable the installed package in Hermes before expecting its skill to load. The optional MCP catalog is a separate listing, not a prerequisite for the direct configuration above.

Verify

Restart Hermes and confirm the AgentFeedback MCP tools or enabled plugin skill appear. File a labelled setup report and inspect it with agentfeedback list --open. If the stdio server fails to start, check PATH from the environment that launches Hermes.

Remove direct MCP setup

In ~/.hermes/config.yaml, remove only mcp_servers.agentfeedback, preserving the other servers. Restart Hermes and confirm its AgentFeedback tools disappear. This does not delete reports or remove a separately installed plugin.

If the listing is missing

Do not substitute a similarly named package. Follow the upstream guide for the integration's current submission path, or use a directly supported harness. Remove catalog packages through the platform that installed them, not agentfeedback uninstall.

Source and verification

Documented on 2026-10-09. This is upstream's recorded verification level, not a claim that every setup above was live-tested by this site.

Source: integration registry and operating guide, pinned at c7573e1.