Cursor Agent MCP Server
Related Servers
Alternatives to Cursor Agent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceWraps the cursor-agent CLI to provide cost-effective tools for repository analysis, code search, planning, and editing. Offloads heavy thinking tasks from the host AI to reduce token usage while maintaining precise, scoped workspace operations.75 npmMIT
- AlicenseAqualityAmaintenanceProvides coding agents with repository-aware tools to understand code structure, find existing patterns, and review plans, architecture, and diffs, enabling a consistent engineering workflow across Cursor, Codex, and Claude Code.7MIT
- FlicenseNot gradedqualityAmaintenanceLocal-first MCP toolkit that provides coding agents focused repository context via read_file, search_files, and edit_file tools, reducing token usage and task cost.1-
- AlicenseAqualityBmaintenanceEnables Claude Code to run cursor-agent tasks in isolated git worktrees, manage asynchronous and parallel jobs, review diffs, and safely apply changes back to the repository.1620 npmMIT
- AlicenseAqualityDmaintenanceProvides workspace-scoped file operations and command execution tools for building Cursor-style agents, along with system prompts and tool definitions for LLM integration.5MIT
- AlicenseAqualityDmaintenanceProvides AI coding assistants with context optimization tools including targeted file analysis, intelligent terminal command execution with LLM-powered output extraction, and web research capabilities. Helps reduce token usage by extracting only relevant information instead of processing entire files and command outputs.511 npm62TypeScriptMIT
TDQS
Scored across 7 tools
The tools have some distinct purposes like analyze_files, edit_file, plan_task, and search_repo, but there is notable overlap between cursor_agent_chat and cursor_agent_run (both involve prompting the agent), and cursor_agent_raw is ambiguous as it could duplicate functionality of other tools. Descriptions help differentiate, but an agent might struggle to choose between chat and run for similar tasks.
All tool names follow a consistent snake_case pattern with the prefix 'cursor_agent_' followed by a verb or action (e.g., analyze_files, chat, edit_file). This uniformity makes the set predictable and easy to parse, with no deviations in style or structure.
With 7 tools, the count is reasonable for a server focused on interacting with a cursor-agent, covering analysis, chatting, editing, planning, raw execution, running, and searching. It's slightly lean but well-scoped, as each tool addresses a specific aspect of agent interaction without obvious bloat.
The tool surface covers key operations like analysis, chatting, editing, planning, and searching, but there are gaps in lifecycle coverage—for example, no tools for managing agent sessions, handling errors, or providing feedback on previous actions. The domain is prompt-based agent interaction, and while core workflows are present, the set lacks comprehensive support for advanced or iterative tasks.