openmem-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_project_scopeB | Read the local project bank mapping and session access policy for a workspace. Makes no memory-provider calls. |
| memory_addA | Store text in the active memory provider (Hindsight bank, mem0 user scope, or Cognee dataset ingest when supported). On Hindsight, defaults to async ingest so the MCP returns before LLM extraction finishes (avoids client timeouts). |
| memory_searchC | Semantic or graph search over memories in the active provider. |
| memory_recallC | Retrieve context for a question (Hindsight recall API; mem0/Cognee use search under the hood). |
| memory_forgetA | Delete a memory by id (mem0) or drop an entire Hindsight bank when bank is set without memory_id. |
| memory_exportA | Export memories as PMM v1 (json/jsonl). Hindsight lists via /memories/list; mem0 GET /memories; Cognee dataset /data. |
| memory_importC | Import PMM v1 payload into the active provider (best-effort cross-provider). |
| memory_provider_statusA | Report active MEMORY_PROVIDER and resolved backend URL (no secrets). |
| memory_reflectB | Synthesize session context for a question. Hindsight uses recall; mem0/Cognee search then optional LiteLLM synthesis (PM_LLM_URL / stack LiteLLM). |
| memory_consolidateD | Provider maintenance: Cognee cognify for a bank/dataset; Hindsight notes LiteLLM route; mem0 skips. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct operations, but memory_recall, memory_search, and memory_reflect overlap in retrieval/synthesis semantics. The descriptions clarify provider-specific behavior, which mostly resolves the ambiguity.
All tools use a consistent snake_case memory_* prefix and clear verb/noun patterns. The naming is predictable across the entire set.
Ten tools is well-scoped for a memory-provider abstraction layer. Each tool covers a meaningful operation such as add, search, export, status, consolidation, or scoping.
The surface covers creation, retrieval, deletion, import/export, provider status, synthesis, consolidation, and project scoping. Minor gaps exist around direct update or get-by-id operations, but core workflows are covered.