search_memory

3 MCP servers expose a search_memory tool: hmem — Humanlike Memory for AI Agents, MemoryPilot and WorkingMemory. Their input schemas differ, so compare them below before picking one.

Servers exposing search_memory

• hmem — Humanlike Memory for AI AgentsA · 85stdio

  From the publisher:FTS5 full-text search with sub-node attribution

  Install hmem — Humanlike Memory for AI Agents →
• MemoryPilotB · 76stdio

  From the publisher:Hybrid BM25 + jina RRF search, boosted by importance, graph links, and file watcher context. Batched triple scoring.

  Install MemoryPilot →
• WorkingMemoryD · 33HTTP

  From the publisher:Search the user's Working Memory for relevant past notes and facts. Use this when the user references something they may have stored earlier, or to find related context before answering. Always include your conversation id in client.conversation_id.

  Parameter	Type	Description
  query*	string	Semantic query.
  k	number	Max results (1–20). Defaults to a sensible value.
  conversation_id	string	Optional. Restrict results to notes stamped with this conversation_id at save_memory time. Empty / whitespace-only values are treated as absent.
  dedupe_recent	boolean	Optional. When false, semantic matches that are also recent are still returned in `relevant` (raw semantic results rather than RAG-deduped). Defaults to true.
  client	object	Context about the CURRENT client session. Pass your conversation/thread id as `conversation_id` — it identifies this session for cross-session memory instrumentation and does NOT filter results (use t

  Install WorkingMemory →

Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.