https://api.memorycrystal.ai/mcp. Its server exposes 23 tools. The stdio server exposes those tools plus crystal_edit and six research tools, for 30 tools. Raw HTTP endpoints are a separate interface; their JSON is not always the JSON shown by an MCP client.
Shared conventions
Pass your resolvedagentId where supported. Supply channel for the intended conversation scope and projectId or repoSlug on tools that support project context. Omitting scope does not grant unrestricted transcript access. Scope partitions data within an account; use separate accounts and API keys for separate security boundaries.
The five stores are sensory, episodic, semantic, procedural, and prospective. Categories are decision, lesson, person, rule, event, fact, goal, skill, workflow, and conversation.
Use the IDs returned by the service. Examples containing <memory-id> or other placeholders require substitution. MCP tools return text content blocks, which may contain JSON, formatted text, or both. Inspect isError as well as the text.
Durable writes schedule embedding and salience work after saving. Standard KB imports await that work for each chunk. Neither response promises synchronous graph construction.
For direct HTTP calls, start with authentication and the endpoint map.
When to use
Start with the question or action. Retrieve before you write a duplicate, and save a durable outcome when it matters beyond the current conversation. Use transcript tools for wording, memory tools for distilled knowledge, and KB tools for named references.A practical session
- Read a wake briefing to orient yourself.
- Query a known reference corpus, or recall relevant conversational knowledge.
- Read a truncated result with get memory. Investigate its source with trace when needed.
- Before a consequential action, use preflight to review prior guidance.
- Save a new durable outcome with remember; correct or supersede an existing one when appropriate.
Parameters
Each linked tool reference gives its complete parameters. Common retrieval inputs are:Examples
Callcrystal_recall to find a saved procedure:
Retrieve context
Request body:Retrieval and cost
Recall can use a query embedding, lexical matches, and recent transcript context. Identifier shortcuts and reduced retrieval can skip vector work. Search/recent read transcripts without embedding the query. Stats, listing, trace, and checkpoint creation do not generate an LLM answer. Explicit durable writes and KB imports have separate enrichment work. Supported host hooks capture completed turns automatically. Deliberate tools remain useful whether recall injection is enabled or disabled. Supported hook-based hosts can opt into injection withMEMORY_CRYSTAL_INJECT_RECALL=true; check your integration page for host-specific behavior.