Not just vector search — robotmem understands the structure of robot experiences:
Robotmem MCP server exists for a simple reason — assistants are far more useful when they can act on Robotmem directly instead of describing what you should do. Not just vector search — robotmem understands the structure of robot experiences:.
Once Robotmem is connected, these are the calls the assistant has available:
API — Purposelearn — Record physical experiences (parameters / strategies / lessons)recall — Retrieve experiences — BM25 + vector hybrid search with context_filter and spatial_sortsave_perception — Store perception / trajectory / force data (visual / tactile / proprioceptive / auditory / procedural)forget — Delete incorrect memoriesupdate — Correct memory contentstart_session — Begin an episodeend_session — End an episode (auto-consolidation + proactive recall)The server ships on PyPI as robotmem, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Robotmem's toolset — API, learn, recall and 5 more — is a fair guide to whether it matches your workflow. It is maintained by robotmem; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Robotmem's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| API | Purpose |
| learn | Record physical experiences (parameters / strategies / lessons) |
| recall | Retrieve experiences — BM25 + vector hybrid search with context_filter and spatial_sort |
| save_perception | Store perception / trajectory / force data (visual / tactile / proprioceptive / auditory / procedural) |
| forget | Delete incorrect memories |
| update | Correct memory content |
| start_session | Begin an episode |
| end_session | End an episode (auto-consolidation + proactive recall) |
{
"mcpServers": {
"robotmem": {
"command": "uvx",
"args": ["robotmem"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.