Modes MCP Server

What is Modes MCP Server?

An MCP server for managing Roo's custom operational modes, providing programmatic control over mode configuration and management. It is intended for users who need to create, update, list, delete, and validate custom modes.

How to use Modes MCP Server?

Clone the repository, install dependencies with npm install, and build with npm run build. Configure the environment variable MODES_CONFIG_PATH (defaults to a Roo settings path), create a custom modes JSON file, and add the server configuration to your MCP settings file. Tools are then available via MCP to manage modes.

Key features of Modes MCP Server

• Full CRUD operations for custom modes
• Schema validation with Zod
• File system watching for config changes
• Error handling with standard MCP error codes
• Atomic file operations

Use cases of Modes MCP Server

• Programmatically create, update, list, delete, and validate custom modes
• Manage Roo's mode configuration without manual file editing
• Integrate mode management into CI/CD or automated workflows
• Enforce mode‑specific workflows and tool groups

FAQ from Modes MCP Server

What environment variable configures the modes file path?

MODES_CONFIG_PATH; default is %APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json.

How can I validate a mode configuration without saving it?

Use the validate_mode tool, passing the complete mode configuration object.

What tools does Modes MCP Server provide?

list_modes, get_mode, create_mode, update_mode, delete_mode, and validate_mode.

What error codes are used?

InvalidParams (invalid input or mode not found), MethodNotFound (unknown tool), and InternalError (file system or other internal errors).

What is the recommended mode transition flow?

Planning → Research → Implementation → Integration → Quality Control → Analytics → Troubleshooting → Documentation → Planning.