marketnow-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKETNOW_MEMORY_HOME | No | Override the base directory for storage. Defaults to `~/.marketnow-memory/`. | ~/.marketnow-memory |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_bootstrapA | Load relevant memories to bootstrap a new session: top rules and preferences by importance, plus recent memories and optional query matches. Call at session start. |
| memory_searchA | Semantic search over stored memories (local TF-IDF cosine similarity, boosted by recency and importance). |
| memory_addA | Store a memory: a decision, rule, preference or fact worth remembering across sessions. |
| memory_profileA | Show the full memory profile grouped by topics, with counts by type and topic. Use when the user asks "what do you remember about me?". |
| memory_forgetA | Remove specific memories by id, or by semantic query (dry-run by default; pass confirm:true to delete). |
| memory_clearA | Wipe ALL memories. DANGER ZONE: requires confirm:true. Suggest memory_export first. |
| memory_statusA | Service health: storage path, counts, search backend, version. No parameters. |
| memory_exportA | Export all memories as JSON or Markdown for backup or portability. |
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 8 tools
Each tool targets a distinct memory operation: bootstrap, search, add, profile, clear, forget, status, and export. Even memory_bootstrap and memory_search are clearly separated by purpose and description.
All tools follow a consistent memory_<action> pattern, making the tool set predictable and easy to navigate. The two noun-like names (profile, status) still read as actions in context and do not break the pattern.
Eight tools is well-scoped for a memory service, covering retrieval, storage, deletion, inspection, export, and health checks without redundancy. Each tool earns its place.
The core memory lifecycle is covered: add, search, forget, clear, profile, export, and bootstrap. Minor gaps exist around updating an existing memory in place and importing memories back after export, but these can be worked around.