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	11768
title	GitLab-workflow MCP server scaffold
state	Closed
labels	enhancementaiarchitecture
assignees	neo-gpt
createdAt	May 22, 2026, 4:15 PM
updatedAt	May 22, 2026, 7:37 PM
githubUrl	https://github.com/neomjs/neo/issues/11768
author	neo-gemini-pro
commentsCount	2
parentIssue	11404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 22, 2026, 7:37 PM

GitLab-workflow MCP server scaffold

Closed v13.0.0/archive-v13-0-0-chunk-13 enhancementaiarchitecture

neo-gemini-pro commented on May 22, 2026, 4:15 PM

Context

Epic #11404 establishes the need for a GitLab-equivalent MCP server, parallel to the github-workflow server, deployed strictly for client projects. This ticket handles the first sub-task: the initial server scaffold and tool registry.

The Problem

To support GitLab-based clients without polluting the core Neo.mjs repo's GitHub dependencies, we need a standalone gitlab-workflow MCP server. The server must mirror the github-workflow surface area so agents can interact seamlessly across forges.

The Architectural Reality

This touches ai/mcp/server/gitlab-workflow/. Following ADR 0001 (single-writer) and ADR 0004 (Regeneratable-Cache), this substrate will exist parallel to github-workflow with its own server.mjs and openapi.yaml.

The Fix

Create ai/mcp/server/gitlab-workflow/server.mjs
Create ai/mcp/server/gitlab-workflow/openapi.yaml
Register the mirrored MCP tools: healthcheck, list_issues, list_merge_requests, get_local_issue_by_id, create_issue, manage_issue_comment, manage_issue_labels, manage_issue_assignees.

Acceptance Criteria

server.mjs is created and correctly mounts the mcp-server express instance.
openapi.yaml defines the corresponding tool schemas (adjusted for GitLab naming).
Registered tools match the scope defined above.

Out of Scope

Actually implementing GitLabClient abstraction (Sub-task 2).
Implementing the syncer services (Sub-task 3).
Test implementation (Sub-task 4).

Parent Epic: #11404

tobiu reopened this issue on May 22, 2026, 4:42 PM

tobiu closed this issue on May 22, 2026, 7:35 PM

tobiu reopened this issue on May 22, 2026, 7:35 PM

tobiu referenced in commit f25f509 - "feat(mcp): scaffold GitLab workflow tool registry (#11768) (#11773) on May 22, 2026, 7:37 PM

tobiu closed this issue on May 22, 2026, 7:37 PM