Memorable MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORABLE_API_KEY | No | Optional Bearer token for authentication | |
| MEMORABLE_API_URL | No | Memorable API base URL | http://localhost:3000 |
| MEMORABLE_TIMEOUT_MS | No | HTTP request timeout in milliseconds | 30000 |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memorable_searchB | Unified vector and keyword search across Memorable memories using pgvector cosine similarity or text matching |
| memorable_recall_contextB | Recalls standing pinned memories combined with relevant semantic search matches in one unified context payload |
| memorable_list_memoriesB | List, filter, and paginate memories in Memorable with optional query, mode, and pinned filters |
| memorable_get_memoryB | Retrieve a memory's full Markdown content, embedding status, attachments, and optional rendered HTML |
| memorable_create_memoryB | Create a new memory in Memorable (automatically enqueues vector embedding in the background) |
| memorable_update_memoryC | Update a memory's title, Markdown body, or pinned status in Memorable |
| memorable_append_to_memoryB | Safely append Markdown content to an existing memory without overwriting its prior body |
| memorable_delete_memoryB | Permanently delete a memory and its associated attachments from Memorable |
| memorable_find_neighborsB | Find nearest semantic neighbor memories via 1024-dimensional pgvector cosine distance |
| memorable_generate_embeddingB | Generate or refresh the 1024-dimensional vector embedding for a memory using Ollama (synchronous or async background job) |
| memorable_toggle_pinC | Toggle the pinned status of a memory in the Memorable workspace |
| memorable_reorder_pinnedB | Update the sequential order of pinned memories displayed at the top of the Memorable workspace |
| memorable_list_attachmentsB | List file attachments and download URLs associated with a memory |
| memorable_upload_attachmentB | Upload one or more files to attach to a memory in Memorable (accepts local file paths or base64 data) |
| memorable_delete_attachmentB | Purge and delete an attachment from a memory |
| memorable_render_markdownA | Render Markdown text to sanitized HTML using Memorable's Redcarpet GitHub-flavored markdown pipeline |
| memorable_get_statsA | Get system statistics from Memorable (total memories, pinned memories, and attachments count) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memorable_use_memory_template | Load any Memorable memory or prompt template by ID, substituting {{variables}} into the Markdown body |
| memorable_author_memory | Interactive engineering guide to draft structured AI context, decisions, preferences, or technical knowledge for Memorable |
| memorable_recall_context | Recall standing pinned context and search relevant memories in Memorable to produce a unified context brief |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| memorable_stats | Aggregated Memorable statistics: total memories, pinned memories, and attachments |
| memorable_memories | Index of all active memories saved in the Memorable workspace |
| memorable_pinned | Unified Markdown document combining all pinned memories and standing context |
TDQS
Scored across 17 tools
Most tools have clear, distinct purposes, and the memorable_ prefix plus descriptive names helps selection. There is some intentional overlap between search, list_memories-with-query, and recall_context, and between toggle_pin and update_memory's pinned field, but the descriptions make the boundaries reasonably clear.
All tools use the same memorable_ prefix and snake_case naming convention, typically verb_noun or verb_object. The pattern is highly predictable across memory, attachment, embedding, pin, and utility tools.
Seventeen tools is slightly above the ideal compact range but still reasonable for a memory workspace with search, embeddings, pins, attachments, rendering, and stats. Each tool has a plausible role, though a few convenience tools could be consolidated.
The surface covers the full memory lifecycle: create, read, update, append, delete, search, semantic neighbors, embeddings, pinned ordering, attachments, rendering, and stats. No obvious dead ends remain for core memory-management workflows.