{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "ivenkoolab-loci--share-memory-across-ai-coding-tools",
 "repo": "IvenKooLab/loci",
 "repo_url": "https://github.com/IvenKooLab/loci",
 "repo_slug": "ivenkoolab-loci",
 "title": "Share one memory store across MCP-connected AI tools",
 "page_title": "How to share one memory store across MCP-connected AI tools with Loci",
 "summary": "Point several MCP clients at one LOCI_HOME so they read and write the same memories.",
 "who": "A developer who switches between AI coding tools and keeps re-explaining the same project context.",
 "problem": "Each tool starts without the context gathered in the others, so work gets repeated.",
 "outcome": "Every connected MCP client searches the same index and stores durable memories in one instance directory.",
 "steps": [
  "Complete the setup in the quick start so the instance directory contains config.toml.",
  "Add the Loci server entry to each MCP client config, with command set to loci-mcp and env LOCI_HOME set to the absolute path of the instance directory.",
  "If a client cannot find loci-mcp, replace the command with the absolute path to the executable.",
  "Restart the client and call brain_remember to store a memory, then brain_search to retrieve it from another client."
 ],
 "agent_prompt": "Using the IvenKooLab/loci repo, add a loci entry to the MCP config of <client-name> with LOCI_HOME set to <absolute-instance-path>. Expected output: the client lists brain_search and brain_remember tools. Verify that a memory stored by one client is returned by brain_search in a second client.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says the instance directory must contain config.toml, and every client must point at the same LOCI_HOME for the sharing to work.",
 "category": "Research",
 "tags": [
  "Research"
 ],
 "lang": "python",
 "requirements": [
  "Python 3.11 or newer",
  "git and a terminal",
  "An embedding endpoint that supports /embeddings, plus a chat endpoint (may be a local one)",
  "A notes or project docs directory to index"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/ivenkoolab-loci/share-memory-across-ai-coding-tools/",
 "md": "https://dedupedai.com/use-cases/ivenkoolab-loci/share-memory-across-ai-coding-tools/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/ivenkoolab-loci--share-memory-across-ai-coding-tools.json",
 "api_version": "v1"
}