cursor-ide-wasp-drone — Claude Code subagent: Cursor IDE setup
cursor-ide-wasp-drone — a subagent for Cursor IDE platform configuration: rule file migration, MCP server registration, custom mode authoring, and programmatic automation via @cursor/sdk. Use it to extend Cursor for your project's workflow.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install data-and-ai-tools@wasp-nestWhat cursor-ide-wasp-drone does
Covers the full Cursor IDE configuration stack: migrating legacy .cursorrules to modern .cursor/rules/*.mdc structure, designing rules with proper activation modes, registering MCP servers via mcp.json, writing tools with valid JSON schemas, and automating agents via @cursor/sdk API.
Includes guides on rule architecture and context-budget sizing (hard cap: ~2000 tokens across all alwaysApply rules), config templates, MCP server examples and SDK script patterns, CursorAgentError handling for cloud agents, Agents Window and Cloud Agents support (Cursor 3, April 2026+), custom mode system prompts capped at 300 tokens, and Extension API guard patterns.
Does not own code quality from Cursor agents (language subagents), prompts for external LLMs (mind-wasp-drone), CI/CD pipelines running SDK tasks (devops-wasp-drone owns pipelines), or security audits of MCP credentials (security-wasp-drone).
What it helps with
- Migrate
.cursorrulesto.cursor/rules/without losing functionality - Register a custom MCP server in Cursor with correct tool JSON schemas
- Write a TypeScript script using @cursor/sdk to create and stream agents
- Design a custom Cursor mode with restricted tool access
- Set up Agents Window and Cloud Agents for team collaboration
Example prompts for the agent
- Help me migrate my rules from
.cursorrulesto.cursor/rules/project.mdc - Add an MCP server to
mcp.jsonand write a tool with a valid schema - Write an SDK script that creates an agent via
Agent.createand handlesCursorAgentError
How to install cursor-ide-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install data-and-ai-tools@wasp-nest2Manually: put the files in place
.claude/agents/cursor-ide-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/cursor-ide-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/cursor-ide-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about cursor-ide-wasp-drone
How do I install cursor-ide-wasp-drone in Claude Code?
Run two commands in sequence: first /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install data-and-ai-tools@wasp-nest. The subagent will then be available at .claude/agents/cursor-ide-wasp-drone.md.
What does cursor-ide-wasp-drone do?
It handles Cursor IDE platform configuration: rule file migration between formats, MCP server registration, tool authoring with correct schemas, custom mode design, and agent automation via @cursor/sdk API.
How is cursor-ide-wasp-drone different from language subagents?
It focuses solely on the Cursor IDE platform and its configuration layer: rules, MCP integration, SDK. Code quality from agents is handled by language subagents; external LLM prompts by mind-wasp-drone; CI/CD pipelines by devops-wasp-drone.