Neo.ai.Client missing handlers for get_namespace_tree, get_neo_config, and check_namespace

Context While working on a new application in a separate repository (port 8083), using Neo.mjs v13 and the Neural Link MCP server, several basic inspection tools failed because the client is missing the corresponding handler methods.

The Problem The Neural Link MCP server (neo-mjs-neural-link) attempts to call methods that are missing from Neo.ai.Client in v13, causing socket messages to fail. This breaks core inspection and scaffolding tools for agents.

Errors observed in the browser console:

App.mjs:389 Neo.ai.Client: Failed to handle message Error: Unknown method: get_namespace_tree
App.mjs:389 Neo.ai.Client: Failed to handle message Error: Unknown method: get_neo_config
App.mjs:389 Neo.ai.Client: Failed to handle message Error: Unknown method: check_namespace

The Architectural Reality The Neo.ai.Client class lacks implementations for get_namespace_tree, get_neo_config, and check_namespace. These methods are assumed to be present by the neo-mjs-neural-link MCP server, suggesting a mismatch between the MCP server's expected API and the v13 client's actual API.

The Fix Implement the missing handlers in Neo.ai.Client:

• get_namespace_tree
• get_neo_config
• check_namespace

Acceptance Criteria

• get_namespace_tree is implemented in Neo.ai.Client and returns the expected namespace structure.
• get_neo_config is implemented in Neo.ai.Client and returns the application's config.
• check_namespace is implemented in Neo.ai.Client and correctly validates if a namespace exists.
• The neo-mjs-neural-link MCP server can successfully execute these tools without throwing Unknown method errors.

Origin Session ID Origin Session ID: 41eff379-6084-47b1-bbef-07467f80f591