Neo MCP

Use the Model Context Protocol (MCP) to wire your editor to Neo: the neo-mcp package runs the server locally and syncs results into your project folder.

Get your API key

Open API keys in the Neo dashboard (sign in if prompted).
Create a key and copy it. Keys look like sk-v1-… — treat them like secrets and do not commit them to git.

You will paste this value wherever the examples use sk-v1-YOUR_KEY.

Install

Python 3.11+:


pip install neo-mcp

Editor configuration

Replace sk-v1-YOUR_KEY with your real key in the snippet for your editor.

Claude Code configures MCP through the claude mcp CLI (run these in your system terminal, not inside a chat).

1. Register Neo


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

2. Confirm it’s connected


claude mcp list

You should see neo with a green checkmark.

Demo: Run a task through MCP

MCP tools

Tool	What it does
`neo_submit_task`	Start a Neo task; returns a `thread_id`. Optional `wait_for_completion` blocks until finished.
`neo_task_status`	Poll status (`RUNNING`, `COMPLETED`, `WAITING_FOR_FEEDBACK`, etc.).
`neo_get_messages`	Read the task transcript after completion (large output may be capped).
`neo_list_tasks`	List recent or active tasks (e.g. after reopening the editor).
`neo_send_feedback`	Reply when Neo is waiting for input (`WAITING_FOR_FEEDBACK`).
`neo_pause_task` / `neo_resume_task`	Pause or resume a task.
`neo_stop_task`	Stop and tear down a task.

Typical flow: submit → poll status until COMPLETED or feedback → get messages (or use wait_for_completion on submit to skip polling).