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.
Install the exact server package, select one canonical local store, and expose the bounded agent profile over MCP stdio.
Choose the environment that will actually launch Generic MCP client. The selector never invents an unsupported translation.
A host that can launch a local stdio server and pass arguments.
Stable toolchain with ~/.cargo/bin or its platform equivalent on PATH.
Choose one canonical memory directory and back it up according to your own policy.
The first embedding run may download roughly 550 MB; subsequent use is local.
The version pin is the current published server version represented by this site.
cargo install semantic-memory-mcp --locked --version '=0.5.4'
semantic-memory-mcp \
--memory-dir "$HOME/.local/share/semantic-memory" \
--tool-profile agentAdapt the outer shape to your client and replace ABSOLUTE_MEMORY_PATH. MCP clients do not universally expand ~ or shell variables in argument arrays.
{
"mcpServers": {
"semantic-memory": {
"command": "semantic-memory-mcp",
"args": [
"--memory-dir",
"ABSOLUTE_MEMORY_PATH",
"--tool-profile",
"agent"
]
}
}
}