Modes MCP Server
An MCP server for managing Roo's custom operational modes, providing programmatic control over mode configuration and management.
Features
- 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
Installation
Configuration
1. Environment Variables
Copy
.env.example to .env and adjust as needed:Available environment variables:
MODES_CONFIG_PATH: Path to custom modes configuration file (default:%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json)
2. Custom Modes Configuration
Create a JSON file for your custom modes configuration. See
examples/modes.example.json for the format:3. MCP Settings
Add the server configuration to your MCP settings file (typically at
%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json). See examples/mcp-settings.example.json for the format:Operational Modes Framework
The server manages a comprehensive set of operational modes:
Core System Modes
- Planning Mode
- Analytics Mode
- Research Mode
- Implementation Mode
- Troubleshooting Mode
- Quality Control Mode
- Integration Mode
- Documentation Mode
- Session Management Mode
Specialized Modes
- Trade Ops Manager
Mode Transition Flow
Available Tools
list_modes
Lists all custom modes currently configured.
get_mode
Get details of a specific mode by its slug.
Parameters:
slug: The unique identifier of the mode
create_mode
Create a new custom mode.
Parameters:
slug: Unique identifier (lowercase letters, numbers, and hyphens)
name: Display name for the mode
roleDefinition: Detailed description of the mode's role and capabilities
groups: Array of allowed tool groups
customInstructions: (optional) Additional instructions for the mode
update_mode
Update an existing custom mode.
Parameters:
slug: The unique identifier of the mode to update
updates: Object containing the fields to update (name, roleDefinition, groups, customInstructions)
delete_mode
Delete a custom mode.
Parameters:
slug: The unique identifier of the mode to delete
validate_mode
Validate a mode configuration without saving it.
Parameters:
mode: Complete mode configuration object to validate
Mode Configuration Schema
Development
- Make changes to the source code in
src/
- Build the project:
- Start the server:
Best Practices
- Mode Selection
- Mode Transitions
- Configuration Management
Error Handling
The server uses standard MCP error codes:
InvalidParams: Invalid input parameters or mode not found
MethodNotFound: Unknown tool requested
InternalError: File system errors or other internal issues
Testing
See TESTING.md for comprehensive test cases and validation procedures.
Contributing
- Fork repository
- Create feature branch
- Submit pull request
- Follow coding standards
License
MIT License - see LICENSE for details
Modes MCP Server
An MCP server for managing Roo's custom operational modes, providing programmatic control over mode configuration and management.
Features
- 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
Installation
Configuration
1. Environment Variables
Copy
.env.example to .env and adjust as needed:Available environment variables:
MODES_CONFIG_PATH: Path to custom modes configuration file (default:%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json)
2. Custom Modes Configuration
Create a JSON file for your custom modes configuration. See
examples/modes.example.json for the format:3. MCP Settings
Add the server configuration to your MCP settings file (typically at
%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json). See examples/mcp-settings.example.json for the format:Operational Modes Framework
The server manages a comprehensive set of operational modes:
Core System Modes
- Planning Mode
- Analytics Mode
- Research Mode
- Implementation Mode
- Troubleshooting Mode
- Quality Control Mode
- Integration Mode
- Documentation Mode
- Session Management Mode
Specialized Modes
- Trade Ops Manager
Mode Transition Flow
Available Tools
list_modes
Lists all custom modes currently configured.
get_mode
Get details of a specific mode by its slug.
Parameters:
slug: The unique identifier of the mode
create_mode
Create a new custom mode.
Parameters:
slug: Unique identifier (lowercase letters, numbers, and hyphens)
name: Display name for the mode
roleDefinition: Detailed description of the mode's role and capabilities
groups: Array of allowed tool groups
customInstructions: (optional) Additional instructions for the mode
update_mode
Update an existing custom mode.
Parameters:
slug: The unique identifier of the mode to update
updates: Object containing the fields to update (name, roleDefinition, groups, customInstructions)
delete_mode
Delete a custom mode.
Parameters:
slug: The unique identifier of the mode to delete
validate_mode
Validate a mode configuration without saving it.
Parameters:
mode: Complete mode configuration object to validate
Mode Configuration Schema
Development
- Make changes to the source code in
src/
- Build the project:
- Start the server:
Best Practices
- Mode Selection
- Mode Transitions
- Configuration Management
Error Handling
The server uses standard MCP error codes:
InvalidParams: Invalid input parameters or mode not found
MethodNotFound: Unknown tool requested
InternalError: File system errors or other internal issues
Testing
See TESTING.md for comprehensive test cases and validation procedures.
Contributing
- Fork repository
- Create feature branch
- Submit pull request
- Follow coding standards
License
MIT License - see LICENSE for details