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	9533
title	Migrate MCP servers from SSEServerTransport to StreamableHTTPServerTransport
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Mar 23, 2026, 5:03 PM
updatedAt	Mar 23, 2026, 5:56 PM
githubUrl	https://github.com/neomjs/neo/issues/9533
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 23, 2026, 5:56 PM

Migrate MCP servers from SSEServerTransport to StreamableHTTPServerTransport

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

Closed v12.1.0 enhancementai

tobiu commented on Mar 23, 2026, 5:03 PM

Description

During the implementation of the SSE transport for the MCP servers (knowledge-base and memory-core), we noticed a deprecation warning indicating that SSEServerTransport is deprecated in favor of StreamableHTTPServerTransport (protocol version 2025-11-25).

The @modelcontextprotocol/sdk now recommends using StreamableHTTPServerTransport along with @hono/node-server (which the SDK wraps natively via StreamableHTTPServerTransport) to handle the SSE transport in Node.js HTTP servers.

Investigation Findings

The SDK provides a createMcpExpressApp wrapper in @modelcontextprotocol/sdk/server/express.js.
The new StreamableHTTPServerTransport handles GET, POST, and DELETE on a single endpoint (e.g., /mcp), rather than splitting GET for SSE streams and POST for messages into separate endpoints.
It requires maintaining a mapping of sessions (using req.headers['mcp-session-id']) to reuse the transport instance per session.
Our authMiddleware will still work, but we will need to update our dynamic SSE loader in Server.mjs to implement this stateful routing architecture correctly.

Tasks

Investigate and map out the exact routing logic needed to replace SSEServerTransport with StreamableHTTPServerTransport.
Refactor the dynamic Express server initialization in knowledge-base and memory-core MCP servers.
Ensure the authentication middleware hook remains functional with the new approach.

tobiu assigned to @tobiu on Mar 23, 2026, 5:03 PM

tobiu added the enhancement label on Mar 23, 2026, 5:03 PM

tobiu added the ai label on Mar 23, 2026, 5:03 PM

tobiu referenced in commit 4ad5e3a - "refactor(ai): Migrate MCP servers to StreamableHTTPServerTransport (#9533) on Mar 23, 2026, 5:49 PM

tobiu Mar 23, 2026, 5:49 PM

Input from Gemini 3.1 Pro:

✦ ✦ I have completed the migration.

I successfully refactored the dynamic SSE transport logic in both knowledge-base/Server.mjs and memory-core/Server.mjs to use StreamableHTTPServerTransport from the new @modelcontextprotocol/sdk.

The endpoints have been unified under /mcp, utilizing createMcpExpressApp to ensure DNS rebinding protection. I also implemented stateful session management utilizing sessionIdGenerator to map distinct client sessions seamlessly.

Changes have been successfully committed and pushed to dev. I'll close this ticket now.

tobiu referenced in commit fbffa1e - "perf(ai): Use dynamic import for StdioServerTransport (#9533) on Mar 23, 2026, 5:55 PM

tobiu Mar 23, 2026, 5:55 PM

Input from Gemini 3.1 Pro:

✦ ✦ I agree, that's a good optimization. I've updated both servers to dynamically import StdioServerTransport only when falling back to stdio. The changes have been pushed, and I will now close this issue.

tobiu closed this issue on Mar 23, 2026, 5:56 PM

tobiu referenced in commit 127ea55 - "refactor(ai): Remove obsolete transport class field (#9533) on Mar 23, 2026, 6:04 PM

tobiu referenced in commit e276e4d - "docs(ai): Document SSE transport options for MCP servers (#9533) on Mar 23, 2026, 6:15 PM

tobiu referenced in commit 5c9bf67 - "docs(ai): Update JSDoc for MCP Server classes (#9533) on Mar 23, 2026, 6:16 PM