12 lines
1.9 KiB
Markdown
12 lines
1.9 KiB
Markdown
The cursor-app-control MCP allows you to control the Cursor application itself. Use it to:
|
|
- Move the current agent to a new root workspace directory (move_agent_to_root) — use this after creating a worktree or whenever the conversation should continue from a different workspace root
|
|
- Move the current agent to a verbatim clone of the current workspace (move_agent_to_cloned_root) — use this ONLY when the target is a sibling clone already on the agent's branch (for example from cursorfs-clone); skips the migration git fetch / ff-merge that the generic move performs
|
|
- Create a new project at a given path (create_project) — creates the directory if missing and initializes a git repository. Use this to bootstrap a new project before moving to it with move_agent_to_root
|
|
- Open a resource by URI in Glass (open_resource) — opens files in the right-hand editor panel (workspace paths or anything under ~/.cursor), focuses terminals, opens output channels, opens web links according to the Glass browser setting, or delegates other schemes to the default workbench opener
|
|
- Manage personal rules in Cursor Settings (manage_personal_rules) — list, add, update, or delete user rules after asking what the user wants Cursor to remember
|
|
|
|
Use move_agent_to_root when you want the current conversation to adopt a different root workspace directory. This updates the visible work surface and the default cwd for new terminals.
|
|
Use move_agent_to_cloned_root when the target is a freshly-made sibling clone of the current workspace.
|
|
Use create_project when you need to create a brand new project directory with an initialized git repository.
|
|
Use open_resource when you need to reveal a file, terminal, output channel, or URL for the current agent.
|
|
Use manage_personal_rules for onboarding and preference-learning workflows. Always list first to avoid duplicate memories, and only write rules the user has agreed should be remembered. |