mcp-ariel-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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_hookA | Fire one external lifecycle event (session_started, new_message, ...). Args: event: one of KNOWN_EVENTS (session_started, session_ended, new_message, auto_save_candidate, context_threshold, memory_pressure, post_context_compression). payload: event body. Recognized keys per event: session_ended: {"summary": str}; new_message/auto_save_candidate: {"text": str}; post_context_compression: {"query": str}; session_started: {"text": str?, "budget": int?}. layer: "user" (default) or "agent". user_id: subject user (bound to API key on HTTP transports). ctx: MCP context (injected). Returns: Handler results dict; unknown event raises ValueError (MCP error). |
| thinkC | Universal Primitive: routing thoughts to correct memory layers based on importance and content. |
| dreamC | Universal Primitive: Hybrid search across ALL layers (L3, L4, Wiki, Graph) with context construction. |
| forgetC | Universal Primitive: context-aware forgetting with Shadow Bin support. |
| evolveC | Universal Primitive: update agent personality and triggering evolution. |
| projectC | Universal Primitive: managing project-specific context and file mapping. Projects are global (keyed by name). Structured data (identity, decisions, artifact map, code index) lives in projects.db; large documents go to the Wiki as project_spec pages. |
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 6 tools
Each tool has a different core function—event ingestion, thought routing, search, forgetting, personality update, project context—but memory_hook and think both serve as write/ingestion paths, making it unclear which to use for a new piece of information. The one-line 'Universal Primitive' descriptions don't clarify these edge cases.
The set mixes a prefixed, compound name (memory_hook) with five bare metaphorical verbs (think, evolve, dream, forget, project), with no consistent verb_noun or domain convention. 'project' is also ambiguous as a noun or verb, further weakening the pattern.
Six tools is a reasonable size for a memory service, and each addresses a broad concern such as ingestion, retrieval, forgetting, personality evolution, or project context. The count is not bloated, though the overlap between think and memory_hook makes the set feel slightly less refined.
The surface covers writing (think/memory_hook), searching (dream), and deleting (forget), but there is no explicit update, direct retrieval by identifier, listing, or memory inspection across layers. This will force agents to use awkward workarounds like forget-then-write to alter existing memories.