$ loading_
Search and save cross-project memories for Claude and Gemini assistants.
This MCP tool is described as providing unified search and storage across Claude Code and Gemini CLI memories, which implies local data access and local code execution. No secrets or remote endpoints are declared, and source code is available, but it comes from a third-party registry with low adoption and unclear maintenance, so the overall posture is cautionary.
The materials explicitly state that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential exposure appears low.
The materials explicitly list no remote endpoints, and the description does not mention sending memory content to external services; based on the available facts, no clear data egress path is disclosed.
The system checks confirm code-execution capability. As an MCP tool, it would typically run a local server process to provide search/save functions. The materials do not show requests for permissions beyond its stated purpose, but local execution should still be treated with caution.
Its stated function is unified search and saving across Claude Code and Gemini CLI memories, which reasonably implies reading and possibly writing related local memory data. The materials do not specify exact paths, scope, or permission boundaries, so this inherent access should still be monitored.
A public source repository exists, which improves auditability and lowers the risk associated with closed-source software. However, it comes from a third-party registry, has no declared license, shows 0 stars, and has unknown maintenance status, leaving trust and maintenance signals relatively weak.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "crossmem" yet — see the docs or source repo.
Use crossmem to search our past discussions in Claude Code and Gemini CLI about the authentication approach, then summarize the final decision, alternatives considered, and why they were rejected.
A cross-tool search result with a clear summary of the decision and its context.
Save this rule to crossmem: all Node.js services must use pnpm, ESLint flat config, and run type checking in CI.
The team convention is stored in shared memory for future projects and assistants.
Use crossmem to retrieve prior knowledge about logging standards and error handling from the last three projects, and produce a reusable best-practices checklist.
A consolidated cross-project summary with actionable best practices and common patterns.
Share persistent memory across AI sessions to improve continuity and collaboration.
Save and reuse AI memory across platforms for more consistent workflows.
Search and filter Claude Code memory files to retrieve relevant context fast.
Preserve research, project state, and decisions for MCP clients with audit history.
Give Claude Code cross-machine, file-first memory with synced full-text search.
Give Claude Code persistent cross-session memory with semantic search and project isolation.