Neo MCP

Connect your AI editor to Neo's remote execution backend. Describe an AI/ML task in plain language — Neo trains the model, builds the pipeline, or runs the workload on its backend, then writes all output files directly to your local machine.

Works with Claude Code, Cursor, Windsurf, VS Code (GitHub Copilot), Zed, Continue.dev, and OpenAI Codex CLI.

Get your API key at heyneo.com/dashboard → Settings → API Keys.

How it works

Your editor  ──MCP──▶  neo-mcp server  ──API──▶  Neo backend
                            │                          │
                            └──────────────────▶  Local daemon
                                                  (writes files,
                                                   runs scripts)

1. You describe a task: "Train a fraud detection model on data.csv"
2. The editor calls neo_submit_task via MCP
3. Neo's backend processes the task and sends commands to the local daemon
4. The daemon runs on your machine — writing files, running scripts, installing packages
5. Output files appear directly in your workspace

Files are always written to your machine, never stored remotely.

Neo can also hold your third-party API keys (GitHub, HuggingFace, Anthropic, OpenRouter, OpenAI, AWS S3, Weights & Biases, Kaggle) locally so it can use them in tasks without re-prompting — keys stay on your machine, never sent to Neo's backend. Full guide: docs/INTEGRATIONS.md.

Install

Pick pip (Python 3.11+) or npm (Node.js 18+) — both work identically from the editor's perspective.

pip

pip install neo-mcp

Use pipx install neo-mcp to avoid virtualenv conflicts.

npm

npm install -g neo-mcp

Install Node.js 18+ if needed: curl -fsSL https://deb.nodesource.com/setup_20.x | bash - && apt-get install -y nodejs

Connect to your editor

Replace sk-v1-YOUR_KEY with your actual API key. Pick the pip or npm command based on which you installed.

Claude Code

pip:

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

npm:

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

Open a new Claude Code session after running — tools load at session start, not mid-session.

Cursor

Open the config:

• GUI: Ctrl+Shift+J (Windows/Linux) or Cmd+Shift+J (Mac) → Tools & MCP → New MCP Server
• Or edit the file directly: ~/.cursor/mcp.json

pip:

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

npm:

{
  "mcpServers": {
    "neo": {
      "command": "neo-mcp-daemon",
      "args": ["--mcp"],
      "env": { "NEO_SECRET_KEY": "sk-v1-YOUR_KEY" }
    }
  }
}

Restart Cursor after editing the file directly. Changes via the GUI apply immediately.

Windsurf

Open the config:

• GUI: Ctrl+, (Windows/Linux) or Cmd+, (Mac) → Cascade → Plugins (MCP servers) → Manage Plugins → View raw config
• Or edit the file directly: ~/.codeium/windsurf/mcp_config.json

pip:

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

npm:

{
  "mcpServers": {
    "neo": {
      "command": "neo-mcp-daemon",
      "args": ["--mcp"],
      "env": { "NEO_SECRET_KEY": "sk-v1-YOUR_KEY" }
    }
  }
}

Changes apply on save — no restart needed.

VS Code (GitHub Copilot)

Requires VS Code 1.99+.

Open the config:

• Command Palette: Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac) → "Chat: Open Chat Customizations"
• Or edit the file directly: .vscode/mcp.json in your workspace root (create if it doesn't exist)

pip:

{
  "servers": {
    "neo": {
      "type": "stdio",
    

... [View full README on GitHub](https://github.com/neoairesearch/neo-mcp#readme)