Memo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMO_USE_GPU | No | Enable/disable GPU usage ("true"/"false") | |
| MEMO_RAG_LITE | No | Enable resource-constrained mode ("true"/"false") | |
| MEMO_DATA_ROOT | No | Override the default data directory | |
| MEMO_EMBEDDING_MODEL | No | Custom embedding model name |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add-memoB | Add a new memo entry to your journal collection |
| search-journalA | Search through journal entries using RAG. Perfect for questions like 'how did I do at work this year?' or 'what were my thoughts on AI?' |
| get-journal-statsA | Get statistics about your journal database (document count, chunks, etc.) |
| rebuild-journal-indexA | Rebuild the journal search index (use if you've added new entries) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool addresses a distinct function: adding, searching, managing index, and viewing statistics. There is no overlap in their purposes.
All tools follow a consistent verb-noun pattern with hyphens (e.g., add-memo, search-journal), making names predictable and easy to understand.
With 4 tools, the set is well-scoped for a lightweight journaling server, covering essential operations without unnecessary bloat.
Core actions (add, search, stats, maintenance) are present, but missing read/update/delete operations for individual memos, which may require agents to use search as a workaround.