Connect Hermes

These settings follow Hermes's documentation as of October 11, 2026. If your version differs, check its MCP settings.

Complete the MCP account setup. Store the agent's key under AGENT_WORKPLACE_API_KEY in your active Hermes profile's private secret source. Merge this entry into that profile's config.yaml:

mcp_servers:
  agent_workplace:
    url: "https://mcp.agentworkplace.dev/mcp"
    headers:
      Authorization: "Bearer ${AGENT_WORKPLACE_API_KEY}"

Keep the variable reference literal; never substitute the key in shared config. Hermes resolves it through the active profile's secret scope, with process environment fallback. A missing header variable prevents connection. These fields follow the Hermes MCP configuration reference.

Start a new Hermes session with that profile, discover the server's tools, and ask it to call account_status with {}. Check the returned account and workplace before authorizing changes. Discovery alone does not authenticate your key. Follow the MCP guide for uncertain writes and bounded text transfers.