mcpField
C
Cursor Delegate

Cursor Delegate

Local
github.comAI & Agents9Updated 6d ago

About Cursor Delegate

Cursor Delegate is an MCP server that lets AI coding clients hand implementation work to Cursor's CLI agent. It returns a structured result for review and supports planning, codebase Q&A, and resumed sessions when clarification is needed.

Key features

  1. 01Delegate implementation to Cursor's CLI agent
  2. 02Return changed files and session details as JSON
  3. 03Review a plan before implementation
  4. 04Ask questions about the codebase
  5. 05Resume a session after clarification

Use cases

  1. 01Delegate multi-file edits while retaining review in the originating agent
  2. 02Approve a proposed implementation plan before execution
  3. 03Ask codebase questions through Cursor's agent

MCP support

Exposes the delegation bridge over MCP stdio to MCP clients. A client sends a brief to Cursor's CLI agent and receives its result.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"andreilungeanu-cursor-delegate": {
"command": "npx",
"args": [
"-y",
"cursor-delegate-mcp"
]
}
}
}
Run commandnpx -y cursor-delegate-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmcursor-delegate-mcp2.6.0

Tools

3

Saved tool list · updated 6d ago

ParameterTypeRequiredDescription
fastbooleanNoFast tier; higher cost — only when the user asks.
modeenumNoagent implements; plan and ask are instructions to the agent, not limits.agent | plan | ask
specstringYesTask brief: goal, scope, fixed decisions quoted exactly, acceptance criteria. Sent as written. Point at files to read rather than pasting code, or attach them with contextFiles.
modelstringNoBare ACP family id, version included: composer-2.5, grok-4.5, claude-opus-5, gpt-5.6-sol. doctor deep:true lists every id.
effortstringNoExact Cursor thinking-effort value for the selected model. Values differ per model and some expose no effort option; invalid values fail before the prompt and name the accepted set. Pass only when the user asks for Cursor effort — the host's own reasoning setting is unrelated.
contextstringNoContext window size; gpt-5.x accepts 272k and 1m. Do not pass speculatively.
workspacestringYesThe agent's working directory, not a limit. Smallest directory holding the task's files; with no such directory the project root is the floor. Must already exist; never create one for the call.
contextFilesarrayNoPaths to attach instead of pasting contents into spec. Text becomes references the agent may open; images (png/jpg/gif/webp, <5MB) are sent inline. Relative paths resolve against workspace but are not limited to it. Skips are reported in protocolWarnings, never fatal.
resumeSessionIdstringNoContinue an existing ACP session.

Details

From the project README

Cursor Delegate

Stop burning your frontier agent's limits on boilerplate.

Delegate edits to Cursor's CLI agent — your agent writes the brief and reviews the diff.

npm version npm downloads MCP Registry cursor-delegate-mcp MCP server node license: MIT tests

Cursor Delegate logo

Use your best coding agent where its judgment matters most: understanding the task, shaping the plan, and reviewing the result.

Cursor Delegate is the MCP bridge that lets Claude Code, ChatGPT/Codex, Copilot — or any MCP client — hand implementation to Cursor's CLI agent, then get a clean, structured result back for review.


Demo

🧠 Frontier quality, kept

Your assistant does what frontier models are for: understands the task, writes a precise brief, reviews the finished diff. Composer 2.5 runs the implementation loop under that brief. The bundled skill puts the review step in the loop — the agent that scoped the work reads the changed files back before reporting.

⚡ Done faster

Composer 2.5 is built for throughput on multi-file edits. The whole delegation is one call — brief in, result out — so you review a finished diff instead of babysitting edits landing file by file.

🔋 Your limits stop being the bottleneck

Composer and Grok draw from the Cursor Models usage pool, separate from third-party model usage on supported Cursor plans. Your Claude or Codex subscription handles the brief and review while Cursor runs the implementation. If you pay per token on API, implementation moves onto the Cursor capacity you already have.

You and your agent plan and review; the MCP delegate tool hands the brief to cursor-agent (Composer 2.5), which implements and edits your workspace; a clean result comes back with what changed, which files, and the plan, for your agent to review

Delegate result payload

Features

  • 🤝 Native plugins — install into Claude Code, ChatGPT/Codex, or GitHub Copilot CLI and just say "delegate this to Cursor". The shared skill teaches your agent how to delegate well.
  • 💬 No stalled runs — if Cursor needs to clarify, it ends the turn and returns the question as a normal result. Your agent reads it and answers by resuming the same session — nothing blocks on a modal waiting for input.
  • 📦 Clean, named results — final answer, changed files, session id, and the plan, returned as one compact JSON payload. Nothing to scrape.
  • 📋 Plan first — plan mode: Cursor drafts a plan, you review it, then the same session implements it.
  • 🔍 Ask anything — ask mode: Q&A over your codebase.
  • 🩺 Self-diagnosing — a doctor tool that tells you exactly what's missing if setup isn't right.
  • 🔌 Portable — plain stdio MCP, so it runs anywhere: VS Code, JetBrains, Windsurf, Visual Studio, OpenCode, Antigravity, and more.

plan and ask are instructions to the agent, and workspace is its working directory — Security and the delegate reference spell out what the bridge enforces and what it reports back.

Install

You need Node.js 20+ and the Cursor CLI, logged in (cursor-agent login).

Claude Code
/plugin marketplace add andreilungeanu/cursor-delegate-mcp
/plugin install cursor-delegate@cursor-delegate-mcp

Then just ask:

Delegate to Cursor: migrate src/api from callbacks to async/await and update the tests, then walk me through what changed.

That's the whole loop — Claude writes the brief, Cursor grinds through the files, Claude walks you through the diff.

ChatGPT desktop / Codex
codex plugin marketplace add andreilungeanu/cursor-delegate-mcp
codex plugin add cursor-delegate@cursor-delegate-mcp
GitHub Copilot CLI
copilot plugin install andreilungeanu/cursor-delegate-mcp
Any other MCP client
{
  "mcpServers": {
    "cursor-delegate": {
      "command": "npx",
      "args": ["-y", "cursor-delegate-mcp"]
    }
  }
}
Client-specific config locations
VS Code — one-click install, or .vscode/mcp.json

Install in VS Code Install in VS Code Insiders

Or add it manually:

{
  "servers": {
    "cursor-delegate": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "cursor-delegate-mcp"]
    }
  }
}

Or run Chat: Install Plugin From Source with this repository's URL.

JetBrains AI Assistant — Settings → Tools → AI Assistant → MCP

Under Settings → Tools → AI Assistant → Model Context Protocol (MCP), add a server with command npx and arguments -y cursor-delegate-mcp.

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

Same mcpServers block as the generic snippet above. Cascade caps you at 100 tools across all servers.

Visual Studio 2022 / 2026 — %USERPROFILE%\.mcp.json

Same servers + type: "stdio" shape as VS Code. Requires Visual Studio 2026, or 2022 17.14+. Note the top-level key is servers, not mcpServers. Visual Studio also discovers .mcp.json next to the solution, plus .vscode/mcp.json.

OpenCode — ~/.config/opencode/opencode.json or project opencode.json

OpenCode does not use mcpServers. Local servers go under mcp, with type: "local" and command as one array:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cursor-delegate": {
      "type": "local",
      "command": ["npx", "-y", "cursor-delegate-mcp"],
      "enabled": true
    }
  }
}
Google Antigravity — ~/.gemini/config/mcp_config.json or workspace .agents/mcp_config.json

Same mcpServers block as the generic snippet above. In the IDE: … on the agent panel → MCP Servers → Manage MCP Servers → View raw config. Antigravity 2.0, IDE, and CLI share the Gemini config file. You may need to approve the server's tools on first run.

Kiro — .kiro/settings/mcp.json or ~/.kiro/settings/mcp.json

Same mcpServers block as the generic snippet above. Workspace file wins when both exist.

Kilo Code — kilo.jsonc (mcp key, not mcpServers)

Same shape as OpenCode: type: "local" and command as one array. In the VS Code extension: Settings → MCP → Add Server → Local (stdio). On Windows, if npx is not found, use command cmd with arguments /c, npx, -y, cursor-delegate-mcp.

Zed — Settings → AI → MCP Servers, or context_servers in Zed settings
{
  "context_servers": {
    "cursor-delegate": {
      "command": "npx",
      "args": ["-y", "cursor-delegate-mcp"],
      "env": {}
    }
  }
}

Zed's native agent uses this. External ACP agents in Zed read their own MCP config unless you forward Zed's servers.

License

MIT © Andrei Lungeanu

Technical reference · Security · Privacy · Terms · Changelog

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.