Store a new memory in a specific district of the neurodivergent mind

Retrieve a specific memory by ID

Update an existing memory's content, tags, district, emotional_valence, intensity, or epistemic_status

Permanently delete a memory and remove all its connections

Create connections between memories (like neural pathways)

Search memories using BM25 semantic ranking with optional goal-context blending, recency bias, and filters. Returns results sorted by relevance score (0-1).

Walk the memory graph from a starting node up to N hops deep, returning all reachable memories

Find memories related to a given memory ID, ranked by graph proximity + BM25 semantic score with optional goal-context blending.

List stored memories with optional pagination and filters

Return aggregate statistics: total count, per-district counts, connection count, most-accessed nodes, and orphan nodes

Show the resolved snapshot path, WAL path, and the effective environment/config source used for persistence.

Return runtime server identity and version details so clients can confirm the active build.

Bulk-import memories from inline entries or from a snapshot file. Supports dry-run validation, dedupe policies, and explicit snapshot migration flags.

Translate an emotional_processing memory into a structured logical artifact (signals, triggers, constraints, next_actions, risk_flags). Creates a distilled memory in logical_analysis district with reduced intensity and neutral valence for efficient consumption by planning agents. Only operates on emotional_processing memories.

Return the same exploration context exposed by the explore_memory_city prompt, packaged as a tool result for clients that support tools but not MCP prompts.

Return the same context exposed by the synthesize_memories prompt, packaged as a tool result for prompt-limited clients.

Return the same context exposed by the synthesize_memory_packets prompt, packaged as a tool result for prompt-limited or attachment-constrained clients.

Register a custom district with LUCA ancestry validation. Custom districts must declare a valid parent that traces back to one of the 5 canonical districts (logical_analysis, emotional_processing, practical_execution, vigilant_monitoring, creative_synthesis). The custom district inherits its archetype from the canonical ancestor.