cursor-mcp
Related Servers
Alternatives to cursor-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables MCP clients to invoke Cursor SDK's agent runtime, run coding agents, list models, and continue conversations.41-
- AlicenseAqualityCmaintenanceEnables AI assistants and other MCP clients to launch and steer Cursor Cloud Agents on repositories or as repo-less research tasks, including model selection, mid-run follow-ups, cancellation, result retrieval, and run listing. Also exposes authentication checks and per-agent or per-run token usage and cost reporting.9MIT
- 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-
- AlicenseAqualityBmaintenanceEnables AI assistants and MCP clients to launch and manage Cursor Cloud Agents on repositories or without one, select models, follow up mid-run, retrieve or cancel results, and check usage and cost.9MIT
- 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
- AlicenseAqualityAmaintenanceEnables MCP clients like Claude Code and Codex to delegate coding tasks to Cursor's CLI agent, which implements changes in the workspace and returns clean, structured results for review.376 npm4MIT
TDQS
Scored across 5 tools
Each tool targets a distinct operation: starting an agent session, continuing it, listing models, listing sessions, and checking health. The session_id requirement in cursor_reply clearly separates it from cursor_agent, leaving no ambiguity.
All tools share the consistent `cursor_` prefix and snake_case, but suffixes mix nouns (agent, models, sessions, health) with a verb-like action (reply). This minor deviation is still readable and predictable.
Five tools is well-scoped for a Cursor agent wrapper, covering execution, continuation, discovery, and diagnostics without redundancy. Each tool clearly earns its place.
Core workflows for interacting with the Cursor agent are covered: starting, continuing, listing models/sessions, and health checks. Minor gaps like session cancellation or status inspection exist but are not essential for typical use.