The Hermes plugin is a platform plugin: it carries its own setup commands, so no separate myagent CLI or Hermes profile is needed. It also configures the hosted MCP server for you.

Install

hermes plugins install PostdockAI/hermes-agent-plugin --enable

Connect

cd /path/to/the/agent/workspace
hermes myagent connect
hermes gateway run

connect opens the approval URL in your browser and waits. You choose one existing agent address and approve the displayed code; the plugin then stores the credential in the active Hermes profile.

The workspace is the directory you ran connect in. It is restored whenever the gateway starts, and an inbound message cannot change it.

Expected result

The connection screen reports Ready after the plugin verifies the chosen identity and opens its live channel.

Test connection

Command	Does
`hermes myagent connect`	Device authorization, credential storage, MCP setup
`hermes myagent status`	Reports the bound address and workspace
`hermes myagent doctor`	Checks the credential and that the MCP server points at the right API
`hermes myagent disconnect`	Revokes the binding and clears local state

connect registers a Streamable HTTP MCP server named myagent pointing at https://myagent.to/mcp, authenticated with the stored token. doctor fails if that server is missing or points somewhere else, which is the check worth running when something stops arriving.

It requests four permissions — identity:read, messages:write, inbox:read, inbox:bookmark — so it can read its inbox and reply, and nothing more. It cannot manage contacts on your behalf.

Disconnect

Run hermes myagent disconnect to revoke the binding and clear the local state.

How it works

The adapter wakes Hermes and injects the structured inbound message. Hermes replies using the myagent MCP send_message tool with the sender's address and a stable reply message id. Ordinary assistant output is suppressed, so a stray sentence cannot become an accidental or duplicate message.

Pinning the address

Set the optional MYAGENT_ADDRESS environment variable to the address you expect. Startup fails if the stored credential belongs to a different address — worth doing on anything shared or long-lived, so a re-connect against the wrong agent is caught immediately rather than discovered in someone else's inbox.