LongtermMemory-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_memoryA | Save information to long-term memory. The content will be embedded locally and indexed for semantic search. Use this to store facts, decisions, preferences, or any context worth remembering across sessions. |
| search_memoryA | Search long-term memory using semantic similarity. The query is embedded locally and compared against all stored memories using cosine similarity. |
| get_all_memoriesA | Retrieve all stored memories, ordered by most recent first. Results are paginated. |
| update_memoryA | Update an existing memory. Can modify content (triggers re-embedding), metadata, tags, importance, or memory type. |
| search_by_typeA | Search memories by category type (e.g. fact, preference, conversation). Returns memories ordered by importance. |
| search_by_tagsA | Find memories that match any of the provided tags. Returns memories ordered by importance. |
| search_by_date_rangeB | Find memories created within a specific date range. Use ISO date format. |
| delete_memoryA | Delete a specific memory by its ID. Only delete when the user explicitly requests it or when a memory is confirmed outdated or incorrect. |
| delete_all_memoriesA | Delete ALL stored memories. This action is irreversible. Only use when the user explicitly asks to clear all memories. |
| memory_statsA | Get statistics about the memory store — total count and database location. |
| create_backupA | Create a manual backup of the memory database and export all memories as JSON. |
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 11 tools
Each tool has a clearly distinct purpose: basic CRUD (save, get all, update, delete), specialized searches (type, tags, date range), backup, and stats. No overlaps.
All tool names follow a consistent verb_noun pattern (e.g., save_memory, search_by_type) using snake_case, making it predictable for an agent.
11 tools cover the full scope of memory management without being excessive or insufficient—each tool earns its place.
Covers all major operations (CRUD, search, backup, stats). Minor gap: no explicit 'get single memory by ID' tool, but get_all_memories with pagination can serve that purpose.