LearnNewsExamplesServices
Frontmatter
id9720
titleFix Memory Core MCP Initialization Error ('N' character parsing)
stateClosed
labels
bugai
assigneestobiu
createdAtApr 5, 2026, 3:24 PM
updatedAtApr 5, 2026, 3:25 PM
githubUrlhttps://github.com/neomjs/neo/issues/9720
authortobiu
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtApr 5, 2026, 3:25 PM

Fix Memory Core MCP Initialization Error ('N' character parsing)

Closedbugai
tobiu
tobiu commented on Apr 5, 2026, 3:24 PM

The neo-mjs-memory-core MCP server was failing to initialize with an invalid character 'N' looking for beginning of value JSON parsing error on standard output.

We identified isolated console.log statements inside ai/graph/Database.mjs ("NEW EDGES BEING ADDED: 0") that polluted the MCP stdio JSON-RPC transport stream.

Resolution:

  • Cleaned up leftover console.log traces in Database.mjs.
  • Cleaned up redundant Ollama fetch failure traces in DreamService.mjs and Ollama.mjs.
  • Added missing 'dummy embedding function' warning bypass inside ChromaManager.mjs.
  • Fixed missing namespace bootstrapping in CollectionBug.spec.mjs.
tobiu added the bug label on Apr 5, 2026, 3:24 PM
tobiu added the ai label on Apr 5, 2026, 3:24 PM
tobiu assigned to @tobiu on Apr 5, 2026, 3:25 PM
tobiu referenced in commit 0e08665 - "fix: Resolve MCP invalid character 'N' startup failure by removing stray console.log traces (#9720)" on Apr 5, 2026, 3:25 PM
tobiu
tobiu Apr 5, 2026, 3:25 PM

Removed stray console.log traces causing stdio pollution. Verified MCP initializes gracefully. Fix pushed to dev branch.

tobiu closed this issue on Apr 5, 2026, 3:25 PM