Hermes Agent × Nowledge Mem
Cross-tool knowledge in every Hermes session. Your decisions, procedures, and context travel with you.
mcp_servers:
nowledge-mem:
url: "http://127.0.0.1:14242/mcp"
timeout: 120Hermes Agent by Nous Research has its own memory system. Nowledge Mem adds knowledge from every other tool you use: decisions made in Claude Code, preferences set in Cursor, insights from ChatGPT. One knowledge graph, accessible through MCP.
Before You Start
- Nowledge Mem running locally (installation)
- Hermes Agent installed
nmem status # Nowledge Mem is running
hermes --version # Hermes is availableSetup
Add the MCP server to your config
Open ~/.hermes/config.yaml and add the Nowledge Mem MCP server:
mcp_servers:
nowledge-mem:
url: "http://127.0.0.1:14242/mcp"
timeout: 120Restart Hermes
Close and reopen Hermes so it picks up the new MCP server.
Verify the connection
Ask Hermes something that depends on your past work:
What decisions have I made recently?If you have existing knowledge in Nowledge Mem, Hermes should find it through memory_search. That's success: Hermes can now see knowledge from your other tools.
Update
The MCP server runs inside Nowledge Mem. When you update the desktop app, all tools update automatically. No changes to your Hermes config needed.
What You Can Do
Find knowledge from other tools
Ask "what did we decide about the database?" and Hermes searches across decisions you made in Claude Code, insights from ChatGPT, notes from Cursor, not just this session.
Save knowledge for everywhere
When you reach a conclusion in Hermes, memory_add stores it so your next Claude Code session, Cursor project, or ChatGPT conversation can find it too.
Start with today's context
read_working_memory gives Hermes your daily briefing: focus areas, priorities, and recent activity. No repeating yourself across tools.
Trace how ideas evolved
memory_neighbors and memory_evolves_chain show how a decision changed over time, which tools you discussed it in, and what source documents back it up.
Search past conversations
thread_search finds past conversations by keyword across every tool. Then thread_fetch_messages retrieves the full exchange with pagination.
MCP Tools
| Tool | What it does |
|---|---|
memory_search | Search knowledge from all your tools. Supports label and date filters. |
memory_add | Save a decision, insight, or preference so any tool can find it. |
memory_update | Update an existing memory with new content or metadata. |
memory_delete | Delete a memory by ID. |
list_memory_labels | List all labels in your knowledge graph. |
read_working_memory | Read today's Working Memory: focus areas, priorities, recent activity. |
memory_neighbors | Explore how a piece of knowledge relates to others across tools and time. |
memory_evolves_chain | Trace how a decision or idea changed over time. |
thread_search | Search past conversations from any tool. |
thread_fetch_messages | Fetch full messages from a conversation with pagination. |
thread_persist | Save the current conversation as a searchable thread. |
Behavioral guidance (optional)
For richer memory behavior, add guidance that tells Hermes when to search, save, and use Working Memory. Hermes discovers HERMES.md files by walking from the working directory upward, so you can place guidance at two levels:
Global (all sessions). Create ~/HERMES.md with the behavioral guidance from the integration source. When Hermes runs outside a git repository, it walks all the way to ~, so this file covers every session: research, writing, planning, coding, anything.
Project-level. Append the guidance to your existing project HERMES.md or AGENTS.md. Do not overwrite your project context; merge the memory guidance into it.
Configuration
No config needed for local use. If you prefer environment variables, add them to ~/.hermes/.env:
| Env Variable | Default | What it does |
|---|---|---|
NMEM_API_URL | (local) | Remote Nowledge Mem server URL |
NMEM_API_KEY | (none) | API key for remote access |
Remote access
For a remote Nowledge Mem server, update the MCP URL in your config:
mcp_servers:
nowledge-mem:
url: "https://your-server/mcp"
headers:
Authorization: "Bearer your-key"
timeout: 120See Access Mem Anywhere.
Troubleshooting
Cannot connect to Nowledge Mem. Confirm the server is running with nmem status. Check that the URL in config.yaml matches the address shown by nmem status.
Tools not appearing. Restart Hermes after editing config.yaml. Verify the mcp_servers block is valid YAML (correct indentation, no tabs).
Slow responses. Increase the timeout value in config.yaml. Large knowledge graphs may take longer for complex searches. If the issue persists, check nmem status for server health diagnostics.
Related
- Integrations overview
- Claude Code · Pi · OpenClaw · Alma · Bub
- Source: nowledge-mem MCP server