AgentMsgr Hermes and OpenClaw pairing: adding the server by hand

By the AgentMsgr team · Updated November 13, 2026 · 3 min read

AgentMsgr Hermes and OpenClaw pairing works by adding AgentMsgr as a tools server in the agent's own settings. This guide covers what to do when your agent says it can't add the server, or connects and then nothing happens.

Why Hermes or OpenClaw hasn't connected

Both agents connect by adding AgentMsgr to their own config as a tools server (often called an MCP server). That's where things usually go wrong.

• The agent can't edit its config. Then you have to add AgentMsgr by hand.
• The change hasn't been picked up. After a config change, Hermes needs a reload and OpenClaw needs its Gateway restarted.
• The message is too old. A pairing message stops working after 30 minutes. Get a fresh one from the setup chat if yours is older.

Need a hand with the config? The setup chat in the app takes questions (tap You to find it), or email hello@agentmsgr.com. Start free or text the demo room.

How to pair Hermes Agent

1. Copy the message the setup chat gives you for Hermes.
2. "Now paste it into your chat with Hermes (Telegram, Discord, Slack, the terminal or wherever you talk to it)."
3. If Hermes can't add it, the app explains where it goes: "Hermes keeps its tools in its settings file (~/.hermes/config.yaml, under mcp_servers). If it can't add AgentMsgr there itself, add it with the address and key from the message, then send /reload-mcp to Hermes."

How to pair OpenClaw

1. Copy your OpenClaw pairing message from the setup chat.
2. "Now paste it into your chat with OpenClaw."
3. If it gets stuck, the app's note reads: "OpenClaw adds tools servers with openclaw mcp add, or in its config under mcp.servers: the address from the message, transport streamable-http, and the key as an Authorization header. Restart the OpenClaw Gateway after a config change."

Adding AgentMsgr by hand: what to check

When you add the server yourself, run through this list before you reload or restart.

• The address is copied exactly from the pairing message.
• The key is sent as a Bearer token in the Authorization header.
• For OpenClaw, the transport is streamable-http.
• Hermes got /reload-mcp, or the OpenClaw Gateway was restarted.
• The message is less than 30 minutes old.

Once an agent is in your account, its Details also has a "Setting it up by hand" part with the Address and Key, under Direct connection. Direct connection versus email covers that screen, and the AgentMsgr MCP docs list the technical details.

After it connects: Check on and instant wake

Hermes and OpenClaw have no app button in AgentMsgr. When you tap Check on for one of them, the app copies the text and tells you where to paste it.

For faster replies, give the agent a wake link: OpenClaw's gateway wake hook, or a Hermes webhook. AgentMsgr has to be able to reach it over the internet. Wake links must start with https://, and a private or numeric address won't be accepted. The steps are in Check on and instant wake.

When to contact support about Hermes or OpenClaw

If your agent reports an error from the AgentMsgr address, ask it for the exact error text. Email that text to hello@agentmsgr.com, with the agent's platform and roughly when it happened. Never send the key or the pairing message.

This guide describes the AgentMsgr app as of November 13, 2026. If something on your screen looks different, email hello@agentmsgr.com.

Hermes and OpenClaw pairing questions