This commit is contained in:
ray zhou
2026-05-29 11:21:40 +08:00
parent 5d6d482efe
commit f71a5c59af
447 changed files with 32245 additions and 116 deletions

View File

@@ -0,0 +1,12 @@
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.

View File

@@ -0,0 +1,4 @@
{
"serverIdentifier": "cursor-app-control",
"serverName": "cursor-app-control"
}

View File

@@ -0,0 +1,18 @@
{
"name": "create_project",
"description": "Create a new project at the given path. Creates the directory if it does not exist and initializes a git repository. Use this to bootstrap a new project before moving the agent to it with move_agent_to_root.",
"arguments": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"path": {
"description": "Absolute path where the new project should be created (e.g. \"/Users/name/projects/my-new-app\")",
"type": "string"
}
},
"required": [
"path"
],
"additionalProperties": false
}
}

View File

@@ -0,0 +1,41 @@
{
"name": "move_agent_to_cloned_root",
"description": "Move the current agent to a root workspace directory that is a verbatim clone of the current workspace (for example produced by `cursorfs-clone`) and is already on the agent's recorded branch. Skips the migration-path `git fetch` and ff-merge that `move_agent_to_root` performs. Use ONLY when you already know the target is a sibling clone of the current workspace on the same branch; otherwise use `move_agent_to_root`.",
"arguments": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"anyOf": [
{
"type": "object",
"properties": {
"rootPath": {
"description": "Absolute path to the directory that should become the agent root workspace (e.g. \"/Users/name/projects/my-app\")",
"type": "string",
"minLength": 1
}
},
"required": [
"rootPath"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"rootPaths": {
"description": "Array of absolute paths used to create/switch to a multi-root workspace.",
"minItems": 1,
"type": "array",
"items": {
"type": "string",
"minLength": 1
}
}
},
"required": [
"rootPaths"
],
"additionalProperties": false
}
]
}
}

View File

@@ -0,0 +1,41 @@
{
"name": "move_agent_to_root",
"description": "Move the current agent to a new root workspace directory. Use this after creating a worktree or whenever the conversation should continue from a different workspace root.",
"arguments": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"anyOf": [
{
"type": "object",
"properties": {
"rootPath": {
"description": "Absolute path to the directory that should become the agent root workspace (e.g. \"/Users/name/projects/my-app\")",
"type": "string",
"minLength": 1
}
},
"required": [
"rootPath"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"rootPaths": {
"description": "Array of absolute paths used to create/switch to a multi-root workspace.",
"minItems": 1,
"type": "array",
"items": {
"type": "string",
"minLength": 1
}
}
},
"required": [
"rootPaths"
],
"additionalProperties": false
}
]
}
}

View File

@@ -0,0 +1,4 @@
{
"serverIdentifier": "plugin-figma-figma",
"serverName": "plugin-figma-figma"
}

View File

@@ -0,0 +1 @@
The MCP server needs authentication. You must call the `mcp_auth` tool for server "plugin-figma-figma" through your MCP tool-calling interface using an empty arguments object `{}` soon so the user can access all of the tools this MCP server offers.

View File

@@ -0,0 +1,9 @@
{
"name": "mcp_auth",
"description": "Authenticate this MCP server so the user can access all of its tools. When STATUS.md indicates this server needs authentication, you must call this tool soon through your MCP tool-calling interface.",
"arguments": {
"type": "object",
"properties": {},
"additionalProperties": false
}
}