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	7945
title	Refactor: MCP Client Lifecycle and CLI Runner Renaming
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Nov 30, 2025, 1:50 AM
updatedAt	Nov 30, 2025, 2:13 AM
githubUrl	https://github.com/neomjs/neo/issues/7945
author	tobiu
commentsCount	1
parentIssue	7931
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 30, 2025, 2:13 AM

Refactor: MCP Client Lifecycle and CLI Runner Renaming

Closed v11.14.0/archive-v11-14-0-chunk-1 airefactoring

tobiu commented on Nov 30, 2025, 1:50 AM

Refactor the MCP Client architecture to ensure clear separation of concerns, consistent lifecycle management, and appropriate naming.

Deliverables

Refactor Neo.ai.mcp.client.Client (ai/mcp/client/Client.mjs):
- Lifecycle: Move connection logic from connect() to initAsync(). The client should self-connect during initialization. connect() should be removed or made private.
- Configuration: Add configFile config. Inside initAsync, call ClientConfig.load(this.configFile) if provided, before resolving server details.
- Proxies: Ensure dynamic tool proxies (this.tools) are created during initAsync.
Rename and Refactor CLI Runner:
- Rename: Move ai/mcp/client/mcp-stdio.mjs to ai/mcp/client/mcp-cli.mjs.
- Logic: Update the script to use the new Client lifecycle (await Neo.create(Client, ...).ready()).
- Implementation: Keep the CLI logic (argument parsing, executing client.listTools() or client.tools.x(), logging results) inside this runner script.
- Cleanup: Ensure client.close() is called before exit.
Update package.json:
- Update ai:mcp-client script to point to ai/mcp/client/mcp-cli.mjs.
Refactor Neo.ai.Agent (ai/Agent.mjs):
- Remove the connect() method.
- Move client creation, client.ready() calls, and tool aggregation logic into Agent.initAsync().
- The Agent itself will then be ready when its initAsync completes.
Update ai/agents/mcp-demo-agent.mjs:
- Refactor to use await agent.ready() instead of await agent.connect().
- Verify compatibility.

tobiu assigned to @tobiu on Nov 30, 2025, 1:50 AM

tobiu added the ai label on Nov 30, 2025, 1:50 AM

tobiu added the refactoring label on Nov 30, 2025, 1:50 AM

tobiu added parent issue #7931 on Nov 30, 2025, 1:50 AM

tobiu referenced in commit c541ee2 - "Refactor: MCP Client Lifecycle and CLI Runner Renaming #7945" on Nov 30, 2025, 2:12 AM

tobiu Nov 30, 2025, 2:12 AM

Input from Gemini 2.5:

✦ I have completed the refactoring to align the MCP Client Lifecycle and rename the CLI runner.

Deliverables Completed

Refactor Neo.ai.mcp.client.Client (ai/mcp/client/Client.mjs):

Moved connection logic from the connect() method into initAsync().

Removed the connect() method entirely.

Added configFile config and integrated config loading into initAsync().

The client now correctly self-connects and ensures readiness when await client.ready() is called.

Rename and Refactor CLI Runner:

Renamed ai/mcp/client/mcp-stdio.mjs to ai/mcp/client/mcp-cli.mjs.

Updated the runner script to use the new Client lifecycle (await Neo.create(Client, ...).ready()).

The runner now correctly executes CLI actions and closes the client.

Update package.json:

Modified the ai:mcp-client NPM script to point to ai/mcp/client/mcp-cli.mjs.

Refactor Neo.ai.Agent (ai/Agent.mjs):

Removed the connect() method.

Moved client creation, client.ready() calls, and tool aggregation logic into Agent.initAsync().

Ensured this.clients is correctly populated.

Update ai/agents/mcp-demo-agent.mjs:

Refactored to use await agent.ready() instead of await agent.connect().

Verified all client and agent interactions.

This refactoring ensures architectural consistency across the client and server components and aligns the lifecycle management with Neo.core.Base principles.