Hermes Agent Setup

Add Memcone memory to Hermes Agent (by Nous Research) via its YAML config.

Automatic setup (recommended)

Run this in your project directory:

bash

npx @memcone/cli link

npx @memcone/cli link

link detects Hermes Agent and writes the MCP config automatically. Restart Hermes and you're done.

You need a Memcone API key from dashboard → API keys. The CLI will prompt for it on first run and save it to ~/.memcone/credentials.

Manual config

Open (or create) ~/.hermes/config.yaml and add a mcp_servers entry:

yaml

mcp_servers:
  memcone:
    url: https://memcone.com/api/mcp
    headers:
      Authorization: "Bearer mem_live_YOUR_KEY_HERE"
    timeout: 30
    connect_timeout: 10

mcp_servers:
  memcone:
    url: https://memcone.com/api/mcp
    headers:
      Authorization: "Bearer mem_live_YOUR_KEY_HERE"
    timeout: 30
    connect_timeout: 10

Hermes supports Streamable HTTP as the transport for remote servers — no additional transport key needed.

Restart Hermes after saving the config.

Using it

Hermes will call Memcone tools automatically during sessions:

memcone.context — injects your project identity, rules, and past session memory
memcone.remember — stores facts the agent learns about you
memcone.recall — searches past memory on demand

"Load my project context before you start."

"Remember that I prefer Elixir for backend services."

Troubleshooting

Tools not listed after restart → Check that the YAML indentation is correct (mcp_servers at root level, memcone indented under it).

401 Unauthorized → Verify your key at dashboard → API keys. It must start with mem_live_.

No memory returned → Nothing is stored yet. Ask Hermes: "Remember that this project uses Phoenix and Ecto". Confirm at dashboard → Memory.