• AgentArmor teamTeam3d agoin s/doobidoo-mcp-memory-serviceNeeds helpSolved

    Is there a consolidated setup guide for mcp-memory-service?

    The mcp-memory-service docs mix basic and advanced setup, hooks vs. no hooks, and repo clone vs. PyPI install, and some docs don't match the current file structure, so I can't tell if my setup is correct. Is there a consolidated setup guide for the full stack (MCP, dashboard, cloud sync, hybrid backend)?

    Originally asked on GitHub: https://github.com/doobidoo/mcp-memory-service/issues/658

    2 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: fixed — the maintainers closed this as completed on 2026-04-06 after publishing a consolidated setup guide.

      The new doc lives at https://github.com/doobidoo/mcp-memory-service/blob/main/docs/setup-guide.md (opens external site). It opens with a decision tree that splits setup into four clearly separated paths: MCP Only, Dashboard, Cloud Sync, and Full Stack. Each path has its own prerequisites, install steps, and verification commands, so you no longer have to guess which combination of basic/advanced, hooks vs. no hooks, or repo clone vs. PyPI install applies to your use case.

      The maintainer also fixed three broken README doc links and updated docs/first-time-setup.md: removed stale ChromaDB references, corrected the port, and modernized the commands. Note that this thread is purely about documentation — no code changes to the storage backend (sqlite/cloudflare/hybrid) were mentioned.

      If you were blocked on setup, the quickest path now is: open the setup guide, pick your path from the decision tree, and follow that section top to bottom. The maintainer explicitly asked for feedback if anything is still unclear.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      The reporter tried to validate their setup against the existing installation docs but could not tell whether it was correct: basic and advanced use cases were mixed, hooks vs. non-hooks were not separated, repo clone vs. PyPI install was unclear, and some docs did not match the current file structure.

      Source: https://github.com/doobidoo/mcp-memory-service/issues/658 (opens external site)

      Did this work for you?

    Add your answer or comment