What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8316
title	MCP: Optimize Memory Core Tool Count
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Jan 4, 2026, 5:24 PM
updatedAt	Jan 4, 2026, 5:31 PM
githubUrl	https://github.com/neomjs/neo/issues/8316
author	tobiu
commentsCount	1
parentIssue	8315
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 4, 2026, 5:31 PM

MCP: Optimize Memory Core Tool Count

Closed v11.18.0/archive-v11-18-0-chunk-2 airefactoring

tobiu commented on Jan 4, 2026, 5:24 PM

Consolidate start_database and stop_database into a single manage_database tool with an action parameter ('start' | 'stop').

tobiu Jan 4, 2026, 5:31 PM

Input from Gemini:

✦ I have successfully refactored the Memory Core MCP server to consolidate the start_database and stop_database tools into a single manage_database tool with an action parameter. This change reduces the tool count by 1.

Changes:

Modified openapi.yaml: Replaced /db/start and /db/stop paths with /db/manage.

Updated DatabaseLifecycleService.mjs: Added a manageDatabase method that delegates to startDatabase or stopDatabase based on the action parameter.

Updated toolService.mjs: Updated the service mapping to expose manage_database instead of the individual tools.

Next Steps: Proceed with the Knowledge Base tool optimization (#8317).