RESOLVING ROUTEFollowing the evidence boundary…
Choose the host you already use. The cockpit gives you the published path, the runtime checks that matter, and the boundary the integration does not cross.
Hook-capable hosts can participate in lifecycle events. MCP-and-rules hosts expose explicit tools and guidance without pretending a rules file is a hidden hook.
Copy the current Hermes general plugin from a canonical checkout, enable it, and register semantic-memory-mcp directly with the bounded agent profile.
Choose the environment that will actually launch Hermes Agent. The selector never invents an unsupported translation.
Installed with the plugins and MCP command groups available.
Keep a checkout because the richer kit expects hermes/ and shared/ as siblings.
Used to install the published semantic-memory-mcp binary.
The current published copy-and-enable recipe is written for bash/zsh.
Environment note: The upstream Hermes guide currently publishes a POSIX copy recipe. A native PowerShell plugin-install sequence is not documented; use a supported POSIX environment or follow the canonical Hermes guide rather than translating paths by guesswork.
The exact MCP package pin matches the current published server snapshot used by this site.
git clone https://github.com/RecursiveIntell/agent-memory-kits
cd agent-memory-kits
cargo install semantic-memory-mcp --locked --version '=0.5.4'Run from the agent-memory-kits checkout. Keep --args last because it consumes the remaining arguments.
cp -R hermes "$HOME/.hermes/plugins/semantic-memory-mcp"
hermes plugins enable semantic-memory-mcp
hermes mcp add semantic_memory --command semantic-memory-mcp \
--args --memory-dir "$HOME/.local/share/semantic-memory" --tool-profile agent
hermes mcp test semantic_memory
hermes mcp configure semantic_memory