The current ai/mcp/server/logger.mjs is a centralized logger that incorrectly imports the debug configuration from github-workflow/config.mjs. This creates a tight coupling and prevents other MCP servers (Knowledge Base, Memory Core) from using their own debug settings.
Furthermore, the long-term vision is to move the GitHub Workflow and Memory Core MCP servers into their own independent npm packages. A centralized logger that relies on a specific configuration path within the neo.mjs repository would hinder this decoupling.
To address these issues, the logger.mjs file should be duplicated into each MCP server's directory. Each server will then have its own logger.mjs that imports its respective config.mjs, ensuring proper debug flag usage and enabling future independence.
Acceptance Criteria
- The
ai/mcp/server/logger.mjs file is deleted.
- A new
logger.mjs file is created in ai/mcp/server/github-workflow/. This file imports ../config.mjs and provides the logging functionality.
- A new
logger.mjs file is created in ai/mcp/server/knowledge-base/. This file imports ../config.mjs and provides the logging functionality.
- A new
logger.mjs file is created in ai/mcp/server/memory-core/. This file imports ../config.mjs and provides the logging functionality.
- All files within the
github-workflow server that previously imported the centralized logger are updated to import ../logger.mjs (or ./logger.mjs if in the same directory).
- All files within the
knowledge-base server that previously imported the centralized logger are updated to import ../logger.mjs.
- All files within the
memory-core server that previously imported the centralized logger are updated to import ../logger.mjs.
The current
ai/mcp/server/logger.mjsis a centralized logger that incorrectly imports thedebugconfiguration fromgithub-workflow/config.mjs. This creates a tight coupling and prevents other MCP servers (Knowledge Base, Memory Core) from using their owndebugsettings.Furthermore, the long-term vision is to move the GitHub Workflow and Memory Core MCP servers into their own independent npm packages. A centralized logger that relies on a specific configuration path within the
neo.mjsrepository would hinder this decoupling.To address these issues, the
logger.mjsfile should be duplicated into each MCP server's directory. Each server will then have its ownlogger.mjsthat imports its respectiveconfig.mjs, ensuring properdebugflag usage and enabling future independence.Acceptance Criteria
ai/mcp/server/logger.mjsfile is deleted.logger.mjsfile is created inai/mcp/server/github-workflow/. This file imports../config.mjsand provides the logging functionality.logger.mjsfile is created inai/mcp/server/knowledge-base/. This file imports../config.mjsand provides the logging functionality.logger.mjsfile is created inai/mcp/server/memory-core/. This file imports../config.mjsand provides the logging functionality.github-workflowserver that previously imported the centralized logger are updated to import../logger.mjs(or./logger.mjsif in the same directory).knowledge-baseserver that previously imported the centralized logger are updated to import../logger.mjs.memory-coreserver that previously imported the centralized logger are updated to import../logger.mjs.