Delx Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| memory_agent_manifestA | Machine-readable install and operating instructions for AI agents. Call first when onboarding. Supports privacy_mode documentation for read tools. |
| memory_connection_statusA | Local SQLite path readiness and size without reading entry values. Safe first call every session. |
| memory_data_inventoryA | Static inventory of memory domains, privacy modes and recommended first calls. No live value reads. |
| memory_capabilitiesB | Self-description of this MCP including privacy modes and mutation gating. |
| memory_getA | Exact key lookup. Returns the stored value plus timestamps, ttl, tags, metadata. Returns null if missing or expired. Optional privacy_mode=summary omits full values. |
| memory_listA | List keys with optional prefix, tag, or since (updated_at) filter. Returns keys + timestamps + tags only — call memory_get for values. Scoped by DELX_MEMORY_NAMESPACE when set. |
| memory_searchA | Full-text search across keys, values AND tags. Uses an FTS5 index with bm25 relevance ranking (key-weighted), word-stemming, diacritic folding and prefix matching — so multi-word, partial and accent-insensitive queries all hit, ranked by relevance. Falls back to a LIKE substring scan if the SQLite build lacks FTS5. Returns top N matches with a snippet. Case-insensitive. privacy_mode=summary omits snippets. |
| memory_statsA | High-level stats about the local memory store. Safe to call first on every session to gauge whether the store is empty, small, or large. |
| memory_setA | Create or update a key in memory. Rejects credential-shaped keys or values. Requires explicit_user_intent: true. Returns whether the row was created or updated. |
| memory_forgetA | Delete a single key from memory. Idempotent: returns existed=false if the key was not present. Requires explicit_user_intent: true. |
| memory_forget_by_tagA | Delete every entry carrying the given tag. Returns deleted_count. Requires explicit_user_intent: true. |
| memory_exportA | Dump the memory store as JSON, JSONL, or Markdown. Optional since/until window on updated_at. Use for backup/inspection. Requires explicit_user_intent: true. |
| memory_get_manyA | Batch exact-key lookup (max 50). Missing keys omitted. Respects DELX_MEMORY_NAMESPACE. |
| memory_set_batchA | Upsert up to 50 entries in one SQLite transaction. One explicit_user_intent covers the batch. Rejects secret-shaped keys/values. Namespace-aware. |
| memory_handoffA | Returns store stats + the most recently updated keys (optional values). Designed for session start: one call instead of stats+list+get fan-out. Namespace-aware. |
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 15 tools
Core data operations are distinct, but the six introspection/status tools (agent_manifest, connection_status, data_inventory, capabilities, stats, handoff) overlap in purpose—several report store size or describe privacy modes, and handoff explicitly subsumes stats+list+get. Detailed descriptions mitigate confusion but don't fully eliminate it.
All tools share a consistent memory_ snake_case prefix, but the set mixes noun-style names (memory_stats, memory_handoff, memory_capabilities) with verb-style names (memory_get, memory_set, memory_forget). The prefix keeps it readable, but there is no consistent verb_noun pattern.
15 tools is within the acceptable range for a memory server, and batch/search/export variants earn their place. It feels slightly heavy because several status/introspection tools could be consolidated (e.g., stats vs connection_status vs handoff).
Full lifecycle coverage is present: set/upsert, single and batch get, list/search, forget/forget_by_tag, export, and session-start handoff. Batch operations, namespace awareness, and privacy modes round out the surface with no obvious dead ends.