Neo MCP — AI engineering, without leaving your editor

Stay in Claude Code, Cursor, or Codex and hand your AI/ML work to Neo — an autonomous AI engineer that plans, builds, runs, and evaluates entire workflows from a plain-English request. neo-mcp is the Model Context Protocol server that connects Neo to the AI coding tools you already use, so you never switch tabs: ask your agent to send a task to Neo, and a local daemon writes the resulting code, models, metrics, and reports straight into your repo — on your machine, nothing stored remotely.

Because Neo is purpose-optimized for AI engineering — not a general-purpose coding assistant — it goes deeper on ML, LLM, and data workflows than a general coding agent can.

📚 Docs: https://docs.heyneo.com/neo-mcp · 🔑 Get an API key: Neo dashboard

What MCP unlocks

• 🧩 Stay in your editor — drive Neo from Claude Code, Cursor, VS Code (Copilot), Windsurf, Zed, Continue, or Codex. No new app, no context switching.
• 🔬 More depth — autonomous planning, experiments, evaluation, and iteration tuned for AI/ML, beyond what a generic coding agent attempts.
• 💾 Local-first — every output file is written to your machine; nothing is stored remotely.

What you can build with Neo

• 🤖 Generative AI & LLMs — RAG & semantic search, agents & chatbots, fine-tuning (Llama, Qwen, Gemma), document analysis
• 🧠 ML & deep learning — PyTorch / TensorFlow / scikit-learn training, architecture search, evaluation
• 📊 Data science & analytics — EDA, feature engineering, forecasting, segmentation, A/B testing, reporting
• 👁️ Computer vision — image classification, object detection, OCR
• 🎤 Speech & audio — speech-to-text, text-to-speech, audio classification
• 🔌 Bring your own keys — GitHub, HuggingFace, Anthropic, OpenRouter, OpenAI, AWS S3, Weights & Biases, Kaggle — stored locally, injected as env vars

For data scientists, ML & LLM engineers, analysts, researchers, and PMs who want results, not boilerplate.

Install

pip install neo-mcp

Requires Python 3.11+ on Linux, macOS, or Windows through WSL. Native Windows cmd.exe/PowerShell execution is intentionally unsupported because Neo commands use POSIX shell and container-path semantics.

Tip: use pipx install neo-mcp to install in an isolated environment and avoid conflicts with your project's virtualenv.

Use Neo from your editor

Neo runs in every major MCP-enabled AI editor — set it up once below. Replace sk-v1-YOUR_KEY with your actual key.

Claude Code

claude mcp add --scope user neo \
  -e NEO_SECRET_KEY=sk-v1-YOUR_KEY \
  -- neo-mcp

Open a new Claude Code session after running this. Neo tools load at session start.

Scope options: --scope user (global, recommended) · --scope project (writes .mcp.json in current repo) · --scope local (this machine only)

Verify it registered:

claude mcp list

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "neo": {
      "command": "neo-mcp",
      "env": {
        "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
      }
    }
  }
}

Restart Cursor after editing.

Windsurf

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "neo": {
      "command": "neo-mcp",
      "env": {
        "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
      }
    }
  }
}

Restart Windsurf after editing.

VS Code (GitHub Copilot)

.vscode/mcp.json in your workspace root (requires VS Code 1.99+):

{
  "servers": {
    "neo": {
      "type": "stdio",
      "command": "neo-mcp",
      "env": {
        "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
      }
    }
  }
}

Zed

~/.config/zed/settings.json:

{
  "context_servers": {
    "neo": {
      "source": "custom",
      "command": {
        "path": "neo-mcp",
        "args": [],
        "env": {
          "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
        }
      }
    }
  }
}

Continue.dev

~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "neo",
      "transport": {
        "type": "stdio",
        "command": "neo-mcp",
        "env": {
          "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
        }
      }
    }
  ]
}

OpenAI Codex CLI

~/.codex/config.json:

{
  "mcpServers": {
    "neo": {
      "command": "neo-mcp",
      "env": {
        "NEO_SECRET_KEY": "sk-v1-YOUR_KEY"
      }
    }
  }
}

Tools

Integration tools store credentials locally (file 0o600 under ~/.neo/integrations/, or OS keyring with NEO_INTEGRATIONS_BACKEND=keyring). Keys never leave your machine. See the full guide at docs/INTEGRATIONS.md.

Environment variables

Troubleshooting