Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key used for embeddings and LLM-powered query generation. | |
| TURSO_AUTH_TOKEN | Yes | The authentication token for your Turso database. | |
| TURSO_DATABASE_URL | Yes | The URL of your Turso database or libSQL-compatible endpoint (e.g., libsql://your-db.turso.io). |
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 |
|---|---|
| rememberC | Store a new memory. Describe what you want to remember in plain English. The system will figure out how to store it based on the table structure. |
| forgetC | Delete or modify existing memories. Describe what you want to forget or change in plain English. |
| recallA | Recall memories without modifying them. Describe what you want to remember in plain English. |
| processB | Review and refine existing memories. Analyzes all stored memories for quality, duplicates, and gaps, then asks clarifying questions. Call again with answers to apply refinements. |
| process_answersC | Provide answers to questions raised by the process tool. Pass the original questions and your answers; the system will apply memory refinements based on the answers. |
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 5 tools
Most tools have distinct purposes: remember/recall handle memory storage and retrieval, forget handles deletion/modification, and process/process_answers handle refinement. However, process and process_answers are closely related and could be confused as a single operation, creating minor ambiguity in the workflow.
All tool names follow a consistent verb-based pattern in lowercase (forget, process, process_answers, recall, remember). The naming is uniform and predictable, with process_answers logically extending the process tool without breaking the convention.
With 5 tools, this server is well-scoped for memory management. Each tool serves a clear function in the CRUD lifecycle (create, read, update, delete), and the count is neither too sparse nor bloated, fitting the domain appropriately.
The tool set covers core memory operations: remember (create), recall (read), forget (delete/update), and process/process_answers (refine/update). A minor gap exists in direct update without refinement, but agents can work around this using forget or process, making it largely complete for the domain.