Neo Setup

Use this skill to guide a user through installing and configuring the Neo MCP server.

Slash command: /neo-setup

When invoked as /neo-setup, walk the user through the setup flow below.

Setup — pip (recommended)

Step 1 — Install

pip install neo-mcp
# or: pipx install neo-mcp

Step 2 — Register with your editor

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.

Cursor — edit ~/.cursor/mcp.json:

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

Windsurf — edit ~/.codeium/windsurf/mcp_config.json:

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

VS Code — edit .vscode/mcp.json:

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

Step 3 — Submit your first task

The daemon auto-starts on the first task submission. No manual startup needed.

Setup — npm (Node.js, no Python required)

Step 1 — Install

npm install -g neo-mcp

Step 2 — Register with your editor

Claude Code:

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

For other editors, use neo-mcp-daemon as the command with args: ["--mcp"]. See full editor configs at docs/GUIDE.md.

Verifying the connection

claude mcp list   # should show neo with a green checkmark

Then in a new session ask: "What Neo tools do you have available?" — should list neo_submit_task, neo_task_status, etc.

Troubleshooting

# Diagnostics (pip)
neo-mcp status
neo-mcp doctor
claude mcp logs neo