Neo MCP

Overview

Neo MCP connects MCP-enabled coding tools to Neo, an autonomous AI engineer focused on AI/ML, LLM, GenAI, data science, and analytics workflows. Users describe a task from an editor such as Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Codex, or compatible MCP client, and Neo plans, builds, runs, evaluates, and writes artifacts into the local repository/workspace.

Install

Install from PyPI with pip install neo-mcp, pipx install neo-mcp, or run directly with uvx neo-mcp. The package requires Python 3.11 or newer. The registry package target uses stdio transport with command uvx and args ["neo-mcp"].

Local Stdio Configuration

The primary validated registry target is local stdio. Configure NEO_SECRET_KEY with a Neo API key from the Neo dashboard. NEO_WORKSPACE_DIR can set the default workspace/project root; otherwise the process uses the current working directory.

Hosted Remote Status

Source material documents https://mcpserver.heyneo.com/mcp as a hosted HTTP MCP endpoint using Authorization and X-Neo-Deployment-Id headers. That endpoint returned Cloudflare 502 for HEAD, GET, OPTIONS, and POST probes during review, so it is not included as a Wardn remote target in this draft. The remote header metadata was removed with the remote target.

CLI

The console script neo-mcp defaults to stdio MCP mode. Source-backed subcommands include setup, doctor, status, list, logs, tail, self-test, daemon, stop, restart, uninstall, and install-service. Several diagnostic commands accept --json; log commands accept --lines and --source; setup accepts --secret-key, --editor, --remote, --scope, and --no-backup; daemon accepts --deployment-id; install-service accepts --workspace; uninstall accepts --purge.

Capabilities

Core tools submit and manage Neo engineering tasks, inspect task status/messages, send feedback, pause/resume/stop tasks, manage local provider integrations, manage BYOK LLM profiles, and expose Postman-oriented MCP prompts and resources.

Security and Storage

NEO_SECRET_KEY is required for authenticated runtime use. Third-party integration credentials are stored locally, either in 0600 files under ~/.neo/integrations/ or in the OS keyring when NEO_INTEGRATIONS_BACKEND=keyring and the optional neo-mcp[keyring] extra is installed.

Limitations

The package is marked beta in PyPI classifiers. Python 3.11+ and a Neo API key are required. MCP tools load at client session start, so clients may need a restart/new session after registration. neo_get_messages is capped at about 20,000 tokens. neo_stop_task is irreversible. The advertised GitHub repository returns 404, so repository metadata is not included; the verified source artifact is the PyPI source distribution.

Registry Metadata Note

The verified PyPI/source package version is 0.5.12. This draft now sets serverJson.version to 0.5.12 because no separate upstream server.json version was found; the prior Wardn 1.0.0 value was not treated as an intentional upstream server version. NEO_HOME is left empty in transport environment metadata because source treats NEO_HOME as a literal path when set and otherwise defaults to Path.home()/.neo.