Agent Update

Connect

Hermes Agent → Agent Update

Nous Research's terminal agent for the Hermes models, configured from a YAML file in ~/.hermes.

Hermes Agent talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.

Where it goes: ~/.hermes/config.yaml

Setup

~/.hermes/config.yaml
mcp_servers:
  agent_update:
    url: "https://api.tryagentupdate.com/v1/mcp"
    headers:
      Authorization: "Bearer au_live_..."
Verify
hermes mcp test agent_update

Before you file a bug

Omit transport entirely. Streamable HTTP is the default and sse is the only documented value, so naming it can only hurt. Write the token literally. The docs claim ${VAR} resolves inside headers from the environment or ~/.hermes/.env, but issue #11239 requesting exactly that feature is still open, so a published ${AGENT_UPDATE_TOKEN} would ship as a literal string and 401. Cursor's ${env:VAR} syntax is not supported here either. If the connection dies on a content-type check rather than on auth, skip_preflight: true bypasses the probe. /reload-mcp reloads the config in-session.

Check it worked

Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.

Next

The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.

← All docs