ultramem-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ULTRAMEM_API_KEY | Yes | API key for authentication (required if server enforces auth) | |
| ULTRAMEM_API_URL | No | Base URL of your ultramem-server (default http://localhost:8080) | |
| ULTRAMEM_CONTAINER_TAG | No | Namespace for the memory container (default: server default) |
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 |
|---|---|
| recall_searchA | Search the user's memory in natural language. Returns the most relevant documents plus standalone facts distilled from their history. Use this first to ground any answer or action in what the user actually knows. |
| recall_timelineA | List the user's memory items within a recent time window, newest-first — a COMPLETE enumeration (not a relevance ranking). Use it for 'what did I do/save in the last N days' questions. Optionally restrict to one source. |
| add_memoryA | Write a memory back to the user's store — a task outcome, a decision, or something the user just told you. It flows through the same distillation + reconciliation lifecycle as any ingested document. |
| get_profileA | Fetch the standing profile for the namespace — durable facts (static) plus what the user has been doing recently (dynamic). Inject this into your system prompt to start a session already knowing the user. |
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 4 tools
All four tools have clearly distinct purposes: recall_search for semantic search, recall_timeline for chronological listing, add_memory for writing, and get_profile for fetching user profile. No overlap in functionality.
Tool names follow a consistent verb_noun pattern in snake_case: recall_search, recall_timeline, add_memory, get_profile. The verbs 'recall', 'add', and 'get' are used uniformly.
With 4 tools, the server is well-scoped for a personal memory assistant. Each tool serves a distinct operation (search, timeline, add, profile) without unnecessary bloat or deficiency.
The core operations for memory management are covered: retrieval (search and timeline), addition, and profile access. However, deletion or updating of memories is absent, which is a minor gap.