What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

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

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	7492
title	Refactor to Direct MCP Tool Definitions
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 15, 2025, 12:29 PM
updatedAt	Oct 15, 2025, 12:35 PM
githubUrl	https://github.com/neomjs/neo/issues/7492
author	tobiu
commentsCount	0
parentIssue	7477
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 15, 2025, 12:35 PM

Refactor to Direct MCP Tool Definitions

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.0.0 enhancementai

tobiu commented on Oct 15, 2025, 12:29 PM

As per the official Model Context Protocol (MCP) specification, tools are defined with a specific JSON Schema-based structure (name, description, inputSchema, etc.).

Our current implementation uses an openapi.yaml file as a source of truth, which is then parsed by toolService.mjs to generate the MCP-compliant tool definitions. This is an unnecessary layer of abstraction.

This ticket covers the refactoring of the GitHub Workflow MCP server to define tools directly in code, aligning with the MCP specification and simplifying the architecture.

Acceptance Criteria

The openapi.yaml file is deleted.
A new module is created (e.g., ai/mcp/server/github-workflow/tools.mjs) that exports an array of tool definitions, strictly following the MCP Tool schema.
toolService.mjs is refactored to import the tool definitions directly from the new module instead of parsing the OpenAPI spec.
All Express-related files (index.mjs, app.mjs, config.mjs, and the routes and middleware directories) are deleted.
The ai:server-github-workflow-mcp script in package.json is verified to work correctly with the refactored server.

tobiu assigned to @tobiu on Oct 15, 2025, 12:29 PM

tobiu added parent issue #7477 on Oct 15, 2025, 12:29 PM

tobiu added the enhancement label on Oct 15, 2025, 12:29 PM

tobiu added the ai label on Oct 15, 2025, 12:29 PM

tobiu referenced in commit 6b0ac23 - "Refactor to Direct MCP Tool Definitions #7492" on Oct 15, 2025, 12:34 PM

tobiu closed this issue on Oct 15, 2025, 12:35 PM

tobiu referenced in commit b9e5d04 - "Refactor to Direct MCP Tool Definitions #7492" on Oct 15, 2025, 1:02 PM