Cursor Delegate
Related Servers
Alternatives to Cursor Delegate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code to delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions that resume across calls.12 npmMIT
- FlicenseAqualityBmaintenanceEnables Cursor's main agent to delegate development tasks to Claude CLI subagents via MCP, supporting synchronous, asynchronous, and parallel task execution with monitoring and control.7-
- FlicenseNot gradedqualityDmaintenanceAn MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.-
- AlicenseNot gradedqualityCmaintenanceEnables conversations to delegate natural-language engineering tasks to a local CLI coding agent in operator-approved workspaces via MCP, with sandbox modes, write gating, bounded execution, and redacted results.MIT
- AlicenseNot gradedqualityCmaintenanceEnables programmatic control of Cursor's cloud-based AI agents for automated code generation and repository management via standardized MCP tools.24 npm6MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate tasks to Cursor's headless agent, run adversarial reviews, and verify findings with prosecutor/advocate roles.76 npmMIT
TDQS
Scored across 3 tools
delegate, cancel, and doctor each target a clearly distinct purpose: starting/resuming work, aborting it, and diagnosing setup. There is no overlap between initiating a delegation, cancelling one, and running diagnostics, so an agent can select unambiguously.
All three tools use a single lowercase verb-style command (delegate, cancel, doctor) with no camelCase or underscore mixing. The pattern is predictable and readable throughout.
Three tools is on the slim side but well-matched to a focused delegation wrapper: one action tool, one control tool, one diagnostic. Nothing feels redundant or missing for the core scope, though it sits at the low end of the 3-15 range.
The lifecycle is largely covered: delegate handles start and resume (via resumeSessionId), cancel handles termination with rich status codes, and doctor handles setup failures. The main gap is the lack of a session-listing or status-introspection tool, which agents must work around via the delegate result fields.