migrate_mcp_config

Transfer configuration and rules between IDEs using this tool to maintain consistent AI assistance across development environments. Automatically uses current directory if project path is omitted or invalid.

Instructions

Migrate MCP configuration between different IDEs.

This tool helps migrate configuration and rules between different IDEs,
ensuring consistent AI assistance across different environments.

Note: If project_path is omitted, not a string, or invalid, the current working
directory will be used automatically.

Input Schema

Name	Required	Description	Default
`from_ide`	No	Source IDE to migrate from. Valid options: cursor, windsurf-next, windsurf, cline, roo, claude-desktop	cursor
`project_path`	No	Path to the project. If not provided or invalid, the current working directory will be used
`to_ide`	No	Target IDE to migrate to. Valid options: cursor, windsurf-next, windsurf, cline, roo, claude-desktop

Input Schema (JSON Schema)

{
  "properties": {
    "from_ide": {
      "default": "cursor",
      "description": "Source IDE to migrate from. Valid options: cursor, windsurf-next, windsurf, cline, roo, claude-desktop",
      "title": "From Ide",
      "type": "string"
    },
    "project_path": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Path to the project. If not provided or invalid, the current working directory will be used",
      "title": "Project Path"
    },
    "to_ide": {
      "default": null,
      "description": "Target IDE to migrate to. Valid options: cursor, windsurf-next, windsurf, cline, roo, claude-desktop",
      "title": "To Ide",
      "type": "string"
    }
  },
  "title": "migrate_mcp_configArguments",
  "type": "object"
}

MCP Agile Flow

migrate_mcp_config

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from MCP Agile Flow

Related Tools

MCP directory API