This ticket covers the first phase of the "Integrate Neo.mjs Core into MCP Servers" epic. The goal is to refactor the ai/mcp/server/memory-core/services/chromaManager.mjs into a singleton class that extends Neo.core.Base. This will serve as a proof of concept to evaluate the viability and benefits of using the Neo class system for our MCP server architecture.
Acceptance Criteria
- The
chromaManager.mjs module is refactored into a ChromaManager class.
- The
ChromaManager class extends Neo.core.Base and is configured as a singleton.
- State variables (e.g.,
client) are moved into the Neo config system (e.g., client_).
- Existing functions are converted into class methods.
- The
onConstructed lifecycle hook is used for initialization logic, such as creating the ChromaDB client.
- The
memory-core server's entry point (mcp-stdio.mjs) is updated to initialize the Neo core.
- Service handlers that depend on
chromaManager are updated to use the new singleton instance.
- The
neo-memory-core__healthcheck tool and other related tools continue to function correctly after the refactoring.
This ticket covers the first phase of the "Integrate Neo.mjs Core into MCP Servers" epic. The goal is to refactor the
ai/mcp/server/memory-core/services/chromaManager.mjsinto a singleton class that extendsNeo.core.Base. This will serve as a proof of concept to evaluate the viability and benefits of using the Neo class system for our MCP server architecture.Acceptance Criteria
chromaManager.mjsmodule is refactored into aChromaManagerclass.ChromaManagerclass extendsNeo.core.Baseand is configured as a singleton.client) are moved into the Neo config system (e.g.,client_).onConstructedlifecycle hook is used for initialization logic, such as creating the ChromaDB client.memory-coreserver's entry point (mcp-stdio.mjs) is updated to initialize the Neo core.chromaManagerare updated to use the new singleton instance.neo-memory-core__healthchecktool and other related tools continue to function correctly after the refactoring.