crossmem
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 |
|---|---|
| mem_searchA | Search across all project memories. Use this to find patterns, decisions, and solutions from past projects. Multi-word queries use AND logic. Use quoted phrases for exact matches. Args: query: Search terms (e.g. "credential masking", "docker sidecar") project: Optional project name to filter results limit: Max number of results (default 10) |
| mem_recallA | Recall relevant memories for a project at session start. Returns the project's own memories plus cross-project patterns (knowledge validated across multiple projects). Call this at the beginning of a coding session to load context. If no project is given, auto-detects from the working directory by matching path segments against known project names. Args: project: Project name to recall memories for (auto-detected if omitted) cwd: Working directory path for auto-detection (defaults to os.getcwd()) |
| mem_saveA | Save a memory during a coding session. Use this when you discover something worth remembering: patterns, decisions, gotchas, architecture notes, debugging insights, or any knowledge that would help future sessions. The memory is immediately searchable via mem_search. Args: content: The memory content to save (be specific and actionable) section: Category heading (e.g. "Security", "Architecture", "Gotchas") project: Project name (auto-detected from cwd if omitted) cwd: Working directory for auto-detection (defaults to os.getcwd()) |
| mem_forgetA | Delete a memory by ID. Use this to remove stale, wrong, or duplicate memories. Find the ID via mem_search first, then pass it here. Args: memory_id: The ID of the memory to delete (shown in search results) |
| mem_ingestA | Refresh the memory index by re-ingesting all memory files. Reads Claude Code and Gemini CLI memory files and updates the searchable index. Run this when you know memory files have changed. |
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 5 tools
Each tool targets a distinct memory operation: searching, recalling context, saving, ingesting index, and deleting. No overlaps.
All tools follow a consistent 'mem_' prefix with descriptive snake_case verbs (search, recall, save, ingest, forget).
With 5 tools, the set covers core memory lifecycle operations without being excessive or insufficient for the domain.
CRUD-like operations are present (save, search, recall, forget), and ingest handles index refresh. Lacks an explicit update tool, but save can potentially overwrite.