|
| 1 | +# Nowledge Mem for Hermes Agent |
| 2 | + |
| 3 | +> Cross-tool knowledge, accessible in every Hermes session. Your decisions, procedures, and context travel with you. |
| 4 | +
|
| 5 | +Hermes has its own memory and learning system. Nowledge Mem complements it with knowledge that spans tools: insights from Claude Code, Cursor, Codex, Gemini, and every other environment you work in. One knowledge graph, available everywhere. |
| 6 | + |
| 7 | +## What you get |
| 8 | + |
| 9 | +- **Start every session informed.** Hermes loads your Working Memory briefing: current priorities, recent decisions, open questions. |
| 10 | +- **The agent searches for you.** When past context would improve the answer, Hermes finds it through your knowledge graph without being asked. |
| 11 | +- **Insights stick around.** Key decisions and learnings are saved to Nowledge Mem, ready for any future session in any tool. |
| 12 | +- **Full session history.** Save Hermes conversations as structured threads you can search later. |
| 13 | + |
| 14 | +## Prerequisites |
| 15 | + |
| 16 | +1. **Nowledge Mem desktop app** running (or the server accessible on port 14242) |
| 17 | +2. **Hermes Agent** installed and configured |
| 18 | + |
| 19 | +## Setup |
| 20 | + |
| 21 | +Add the Nowledge Mem MCP server to your Hermes configuration: |
| 22 | + |
| 23 | +```yaml title="~/.hermes/config.yaml" |
| 24 | +mcp_servers: |
| 25 | + nowledge-mem: |
| 26 | + url: "http://127.0.0.1:14242/mcp" |
| 27 | + timeout: 120 |
| 28 | +``` |
| 29 | +
|
| 30 | +Restart Hermes to pick up the new server. |
| 31 | +
|
| 32 | +## Verify |
| 33 | +
|
| 34 | +Start a new Hermes session and ask: |
| 35 | +
|
| 36 | +> Search my memories for recent decisions. |
| 37 | +
|
| 38 | +Hermes should call `memory_search` and return results from your knowledge graph. If Mem is not running, you will see a connection error. |
| 39 | + |
| 40 | +## Update |
| 41 | + |
| 42 | +The MCP server runs inside Nowledge Mem. When you update the desktop app, all MCP tools update automatically. No changes to your Hermes config needed. |
| 43 | + |
| 44 | +## MCP tools |
| 45 | + |
| 46 | +These tools are available to Hermes once the MCP server is connected: |
| 47 | + |
| 48 | +| Tool | Purpose | |
| 49 | +|------|---------| |
| 50 | +| `read_working_memory` | Load your daily context briefing | |
| 51 | +| `memory_search` | Search memories and distilled knowledge | |
| 52 | +| `memory_add` | Save a new memory | |
| 53 | +| `memory_update` | Refine an existing memory | |
| 54 | +| `memory_delete` | Remove a memory | |
| 55 | +| `thread_search` | Search past conversations | |
| 56 | +| `thread_fetch_messages` | Read messages from a specific thread | |
| 57 | +| `thread_persist` | Save a conversation thread | |
| 58 | +| `list_memory_labels` | Browse memory categories | |
| 59 | + |
| 60 | +Additional tools for graph exploration, source analysis, and knowledge processing are available depending on your server configuration. |
| 61 | + |
| 62 | +## Behavioral guidance (optional) |
| 63 | + |
| 64 | +For stronger memory behavior in a specific project, copy the included `AGENTS.md` into your project root as `AGENTS.md` or `HERMES.md`. Hermes reads these files for project-level context. |
| 65 | + |
| 66 | +```bash |
| 67 | +cp AGENTS.md /path/to/your/project/HERMES.md |
| 68 | +``` |
| 69 | + |
| 70 | +This tells Hermes when to search, when to save, and how to use Working Memory. Without it, the MCP tools still work, but Hermes relies on its own judgment for when to call them. |
| 71 | + |
| 72 | +## Remote access |
| 73 | + |
| 74 | +If Nowledge Mem runs on another machine, update the MCP server URL: |
| 75 | + |
| 76 | +```yaml title="~/.hermes/config.yaml" |
| 77 | +mcp_servers: |
| 78 | + nowledge-mem: |
| 79 | + url: "https://your-server:14242/mcp" |
| 80 | + timeout: 120 |
| 81 | +``` |
| 82 | + |
| 83 | +Ensure the remote server has API access enabled. See [Remote Access](https://mem.nowledge.co/docs/remote-access) for setup details. |
| 84 | + |
| 85 | +## Troubleshooting |
| 86 | + |
| 87 | +- **"Cannot connect to MCP server"**: Verify the Nowledge Mem desktop app is running and the server is listening on port 14242. Check with `curl http://127.0.0.1:14242/health`. |
| 88 | +- **Tools not appearing**: Restart Hermes after editing `config.yaml`. Confirm the `mcp_servers` block is properly indented. |
| 89 | +- **Slow responses**: The default timeout of 120 seconds covers deep search. If searches consistently time out, check server performance or network latency for remote setups. |
| 90 | +- **No results from search**: Nowledge Mem may be empty. Add a few memories first through the desktop app or another integration, then try again. |
| 91 | + |
| 92 | +## Links |
| 93 | + |
| 94 | +- [Hermes integration guide](https://mem.nowledge.co/docs/integrations/hermes) |
| 95 | +- [Documentation](https://mem.nowledge.co/docs/integrations) |
| 96 | +- [Discord](https://nowled.ge/discord) |
| 97 | +- [GitHub](https://github.com/nowledge-co/community) |
| 98 | + |
| 99 | +--- |
| 100 | + |
| 101 | +Made with care by [Nowledge Labs](https://nowledge-labs.ai) |
0 commit comments