Frontmatter
| id | 8216 |
| title | Fix Neural Link server startup crash due to missing startServer/stopServer methods |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Dec 30, 2025, 12:14 PM |
| updatedAt | Dec 30, 2025, 12:20 PM |
| githubUrl | https://github.com/neomjs/neo/issues/8216 |
| author | tobiu |
| commentsCount | 0 |
| parentIssue | 8169 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Dec 30, 2025, 12:20 PM |
The Neural Link server crashes on startup because the
start_ws_serverandstop_ws_servertools are mapped toConnectionService.startServerandConnectionService.stopServer, which were not implemented inConnectionServicefollowing the v2 architecture refactor.Root Cause:
toolService.mjsattempts to bind these undefined methods during initialization (or tool list generation), causing aTypeError.Resolution: Implement
startServer()andstopServer()inai/mcp/server/neural-link/services/ConnectionService.mjs.startServer(): Should proxy tothis.ensureBridgeAndConnect()(orspawnBridgeexplicitly).stopServer(): Should kill the child process (if managed) and close the WebSocket connection.This maintains the v2 architecture (ConnectionService as a client to a standalone Bridge process) while restoring the functionality of the lifecycle management tools.