FreshMemory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESH_MEMORY_DB | No | Path to the SQLite database. The default database location is platform-specific. Set FRESH_MEMORY_DB to use an explicit path. | |
| FRESH_MEMORY_SOURCE_ROOTS | No | Allowed source roots for track_source and source-sync features. Use ':' between allowed directories on macOS and Linux, and ';' on Windows. Required only for track_source and source-sync features; without it, FreshMemory can still store and recall memories but refuses to read any source file. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberC | Store a durable fact, assumption, decision, preference, constraint, or observation with freshness metadata. |
| recallB | Search memory. Returns only current, non-conflicted memories by default and reports relevant stale items as warnings. |
| supersedeC | Replace a memory while preserving history. Dependents of the old memory will require review. |
| invalidateB | Mark a memory invalid without deleting its history. Dependents will require review. |
| audit_memoryC | List memories that are expired, superseded, invalidated, conflicted, or need review. |
| explain_memoryC | Explain a memory's state, history, dependencies, dependents, and replacement lineage. |
| track_sourceC | Link an active memory to a local JSON or text file and establish its current value as the baseline. |
| sync_sourcesC | Check tracked local sources now. Structured auto-mode changes replace memory; review-mode changes become pending. |
| review_changesC | List source changes waiting for human or agent review. |
| resolve_source_changeB | Accept or dismiss a pending source change. Text changes require a reviewed replacement statement when accepted. |
| watch_statusC | Show tracked source health, overdue checks, errors, and pending changes. |
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 11 tools
Each tool targets a distinct memory or source lifecycle action, but audit_memory, review_changes, and watch_status all surface review/health information, which could cause minor misselection between listing problems versus listing pending changes.
Mostly snake_case verb_noun (track_source, sync_sources, review_changes), with a few bare verbs (remember, recall, supersede, invalidate) that deviate slightly but remain clear and consistent in style.
11 tools is well-scoped for a memory freshness and source-tracking server; each tool covers a distinct lifecycle stage without obvious redundancy.
Core memory create/read/update/invalidate and source sync are covered, but notable gaps exist: no tool to manage memory dependencies directly, no explicit conflict resolution for memories (audit lists conflicts but doesn't resolve), and no way to untrack a source.