ML Engineering

AI/ML engineering MCP server for Neo — submit tasks, track execution, and retrieve outputs.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "neo-ai-ml-engineering": {
      "command": "uvx",
      "args": [
        "neo-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by ML Engineering.

neo_submit_task

Submit a task to Neo. Returns `thread_id` immediately.

neo_list_tasks

List all running and recent tasks — useful after reopening your editor.

neo_task_status

Check status: `RUNNING` / `COMPLETED` / `WAITING_FOR_FEEDBACK` / `PAUSED` / `TERMINATED`.

neo_get_messages

Read full task output once status is `COMPLETED`. Capped at ~20 000 tokens.

neo_send_feedback

Reply to Neo when it asks a clarifying question (`WAITING_FOR_FEEDBACK`).

neo_pause_task

Pause a running task. Can be resumed.

Documentation Overview

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

Code

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

You describe a task: "Train a fraud detection model on data.csv"
The editor calls neo_submit_task via MCP
Neo's backend processes the task and sends commands to the local daemon
The daemon runs on your machine — writing files, running scripts, installing packages
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

Terminal

pip install neo-mcp

Use pipx install neo-mcp to avoid virtualenv conflicts.

npm

Terminal

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:

Terminal

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

npm:

Terminal

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:

config.json

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

npm:

config.json

{
  "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:

config.json

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

npm:

config.json

{
  "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:

config.json

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

npm:

config.json

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

MCP tools only work in Copilot Agent mode — switch to Agent mode in the chat panel.

Zed

Open the config:

Ctrl+Alt+, (Windows/Linux) or Cmd+Alt+, (Mac) — opens settings.json directly
Or: Command Palette → "zed: open settings"

Add inside ~/.config/zed/settings.json:

pip:

config.json

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

npm:

config.json

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

Changes apply on save — no restart needed.

Continue.dev

Open the config:

Ctrl+L (VS Code) or Ctrl+J (JetBrains) to open the sidebar → click Agent selector above the chat input → click the gear icon
Or edit the file directly: ~/.continue/config.yaml

pip:

yaml

mcpServers:
  - name: neo
    command: neo-mcp
    env:
      NEO_SECRET_KEY: sk-v1-YOUR_KEY

npm:

yaml

mcpServers:
  - name: neo
    command: neo-mcp-daemon
    args:
      - --mcp
    env:
      NEO_SECRET_KEY: sk-v1-YOUR_KEY

MCP tools only work in Agent mode — switch to Agent in the mode selector.

OpenAI Codex CLI

Open the config:

Run codex mcp to manage servers interactively via CLI
Or edit the file directly: ~/.codex/config.json

pip:

config.json

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

npm:

config.json

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

Verify the connection

Claude Code:

Terminal

claude mcp list

You should see neo with a green checkmark. Then open a new session and ask:

"What Neo tools do you have available?"

The assistant should list neo_submit_task, neo_task_status, neo_get_messages, and more.

Tools

Tool	Description
`neo_submit_task`	Submit a task to Neo. Returns `thread_id` immediately.
`neo_list_tasks`	List all running and recent tasks — useful after reopening your editor.
`neo_task_status`	Check status: `RUNNING` / `COMPLETED` / `WAITING_FOR_FEEDBACK` / `PAUSED` / `TERMINATED`.
`neo_get_messages`	Read full task output once status is `COMPLETED`. Capped at ~20 000 tokens.
`neo_send_feedback`	Reply to Neo when it asks a clarifying question (`WAITING_FOR_FEEDBACK`).
`neo_pause_task`	Pause a running task. Can be resumed.
`neo_resume_task`	Resume a paused task.
`neo_stop_task`	Permanently stop and clean up a task.
`neo_list_integrations`	List stored third-party API keys (names only — never the value).
`neo_add_integration`	Register a credential (GitHub, HuggingFace, Anthropic, OpenRouter, OpenAI, AWS S3, Weights & Biases, Kaggle) so Neo tasks can use it as an env var.
`neo_test_integration`	Call the provider's API to confirm a stored key is still valid.
`neo_remove_integration`	Delete a stored key from this machine.

Integration tools store credentials locally — file mode 0o600 under ~/.neo/integrations/ (or native tool files like ~/.aws/credentials, ~/.netrc, ~/.kaggle/kaggle.json), or your OS keyring if NEO_INTEGRATIONS_BACKEND=keyring. Keys never leave your machine. Full guide: docs/INTEGRATIONS.md.

Workflow

Standard (tasks over a few minutes):

Code

neo_submit_task  →  returns thread_id
      ↓
neo_task_status  →  poll until COMPLETED or WAITING_FOR_FEEDBACK
      ↓
neo_get_messages →  read full output

Quick task: Pass wait_for_completion: true to neo_submit_task — it blocks until done and returns output directly. No polling needed.

Mid-task question: When status is WAITING_FOR_FEEDBACK, call neo_send_feedback with your reply. Neo resumes automatically.

Reconnecting after closing your editor:

Code

neo_list_tasks   →  all tasks with live status + thread IDs
neo_task_status  →  check the specific task you care about
neo_get_messages →  read output of any COMPLETED task

Diagnostics (pip)

bash

neo-mcp status      # daemon and key status
neo-mcp doctor      # full health check — identifies common issues
neo-mcp list        # list known threads
neo-mcp logs --source neo-mcp --lines 100   # MCP server logs
neo-mcp logs --source daemon --lines 100    # daemon logs

# JSON output
neo-mcp status --json
neo-mcp doctor --json

Claude Code logs:

Terminal

claude mcp logs neo

Environment variables

Variable	Required	Description
`NEO_SECRET_KEY`	Yes	API key (`sk-v1-...`) from heyneo.com/dashboard → Settings → API Keys
`NEO_DEPLOYMENT_ID`	No	Pin a specific daemon UUID (auto-generated by default)
`NEO_WORKSPACE_DIR`	No	Override workspace directory (useful in Docker or CI)
`NEO_READ_ONLY`	No	`true` = expose only status/message tools — disables submit, stop, and pause

Troubleshooting

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

9d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about ML Engineering

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "ml-engineering": { "command": "uvx", "args": ["neo-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/neo-ai-ml-engineering?style=directory)](https://allmcps.com/mcp/neo-ai-ml-engineering)

HTML Embed

<a href="https://allmcps.com/mcp/neo-ai-ml-engineering"><img src="https://allmcps.com/api/badge/neo-ai-ml-engineering?style=directory" alt="ML Engineering on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

11/16 checks healthy over the last 45d

53Quality signal: Good · 53/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools25/30

Adoption & activity5/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · neo-mcp (PyPI)

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to ML Engineering →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

ML Engineering

AI/ML engineering MCP server for Neo — submit tasks, track execution, and retrieve outputs.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "neo-ai-ml-engineering": {
      "command": "uvx",
      "args": [
        "neo-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by ML Engineering.

neo_submit_task

Submit a task to Neo. Returns `thread_id` immediately.

neo_list_tasks

List all running and recent tasks — useful after reopening your editor.

neo_task_status

Check status: `RUNNING` / `COMPLETED` / `WAITING_FOR_FEEDBACK` / `PAUSED` / `TERMINATED`.

neo_get_messages

Read full task output once status is `COMPLETED`. Capped at ~20 000 tokens.

neo_send_feedback

Reply to Neo when it asks a clarifying question (`WAITING_FOR_FEEDBACK`).

neo_pause_task

Pause a running task. Can be resumed.

Documentation Overview

Neo MCP

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

Code

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

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

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

Install

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

pip

Terminal

pip install neo-mcp

Use pipx install neo-mcp to avoid virtualenv conflicts.

npm

Terminal

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:

Terminal

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

npm:

Terminal

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:

config.json

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

npm:

config.json

{
  "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:

config.json

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

npm:

config.json

{
  "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:

config.json

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

npm:

config.json

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

MCP tools only work in Copilot Agent mode — switch to Agent mode in the chat panel.

Zed

Open the config:

Ctrl+Alt+, (Windows/Linux) or Cmd+Alt+, (Mac) — opens settings.json directly
Or: Command Palette → "zed: open settings"

Add inside ~/.config/zed/settings.json:

pip:

config.json

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

npm:

config.json

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

Changes apply on save — no restart needed.

Continue.dev

Open the config:

Ctrl+L (VS Code) or Ctrl+J (JetBrains) to open the sidebar → click Agent selector above the chat input → click the gear icon
Or edit the file directly: ~/.continue/config.yaml

pip:

yaml

mcpServers:
  - name: neo
    command: neo-mcp
    env:
      NEO_SECRET_KEY: sk-v1-YOUR_KEY

npm:

yaml

mcpServers:
  - name: neo
    command: neo-mcp-daemon
    args:
      - --mcp
    env:
      NEO_SECRET_KEY: sk-v1-YOUR_KEY

MCP tools only work in Agent mode — switch to Agent in the mode selector.

OpenAI Codex CLI

Open the config:

Run codex mcp to manage servers interactively via CLI
Or edit the file directly: ~/.codex/config.json

pip:

config.json

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

npm:

config.json

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

Verify the connection

Claude Code:

Terminal

claude mcp list

You should see neo with a green checkmark. Then open a new session and ask:

"What Neo tools do you have available?"

The assistant should list neo_submit_task, neo_task_status, neo_get_messages, and more.

Tools

Tool	Description
`neo_submit_task`	Submit a task to Neo. Returns `thread_id` immediately.
`neo_list_tasks`	List all running and recent tasks — useful after reopening your editor.
`neo_task_status`	Check status: `RUNNING` / `COMPLETED` / `WAITING_FOR_FEEDBACK` / `PAUSED` / `TERMINATED`.
`neo_get_messages`	Read full task output once status is `COMPLETED`. Capped at ~20 000 tokens.
`neo_send_feedback`	Reply to Neo when it asks a clarifying question (`WAITING_FOR_FEEDBACK`).
`neo_pause_task`	Pause a running task. Can be resumed.
`neo_resume_task`	Resume a paused task.
`neo_stop_task`	Permanently stop and clean up a task.
`neo_list_integrations`	List stored third-party API keys (names only — never the value).
`neo_add_integration`	Register a credential (GitHub, HuggingFace, Anthropic, OpenRouter, OpenAI, AWS S3, Weights & Biases, Kaggle) so Neo tasks can use it as an env var.
`neo_test_integration`	Call the provider's API to confirm a stored key is still valid.
`neo_remove_integration`	Delete a stored key from this machine.

Integration tools store credentials locally — file mode 0o600 under ~/.neo/integrations/ (or native tool files like ~/.aws/credentials, ~/.netrc, ~/.kaggle/kaggle.json), or your OS keyring if NEO_INTEGRATIONS_BACKEND=keyring. Keys never leave your machine. Full guide: docs/INTEGRATIONS.md.

Workflow

Standard (tasks over a few minutes):

Code

neo_submit_task  →  returns thread_id
      ↓
neo_task_status  →  poll until COMPLETED or WAITING_FOR_FEEDBACK
      ↓
neo_get_messages →  read full output

Quick task: Pass wait_for_completion: true to neo_submit_task — it blocks until done and returns output directly. No polling needed.

Mid-task question: When status is WAITING_FOR_FEEDBACK, call neo_send_feedback with your reply. Neo resumes automatically.

Reconnecting after closing your editor:

Code

neo_list_tasks   →  all tasks with live status + thread IDs
neo_task_status  →  check the specific task you care about
neo_get_messages →  read output of any COMPLETED task

Diagnostics (pip)

bash

neo-mcp status      # daemon and key status
neo-mcp doctor      # full health check — identifies common issues
neo-mcp list        # list known threads
neo-mcp logs --source neo-mcp --lines 100   # MCP server logs
neo-mcp logs --source daemon --lines 100    # daemon logs

# JSON output
neo-mcp status --json
neo-mcp doctor --json

Claude Code logs:

Terminal

claude mcp logs neo

Environment variables

Variable	Required	Description
`NEO_SECRET_KEY`	Yes	API key (`sk-v1-...`) from heyneo.com/dashboard → Settings → API Keys
`NEO_DEPLOYMENT_ID`	No	Pin a specific daemon UUID (auto-generated by default)
`NEO_WORKSPACE_DIR`	No	Override workspace directory (useful in Docker or CI)
`NEO_READ_ONLY`	No	`true` = expose only status/message tools — disables submit, stop, and pause

Troubleshooting

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

9d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about ML Engineering

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "ml-engineering": { "command": "uvx", "args": ["neo-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/neo-ai-ml-engineering?style=directory)](https://allmcps.com/mcp/neo-ai-ml-engineering)

HTML Embed

<a href="https://allmcps.com/mcp/neo-ai-ml-engineering"><img src="https://allmcps.com/api/badge/neo-ai-ml-engineering?style=directory" alt="ML Engineering on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

11/16 checks healthy over the last 45d

53Quality signal: Good · 53/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools25/30

Adoption & activity5/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · neo-mcp (PyPI)

★ Featured

AllMCPs Server

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to ML Engineering →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients