Modes MCP Server

If you already use Modes, the modes mcp server is the piece that lets your assistant work with it directly. MCP server for managing Roo custom modes.

What the server does

An MCP server for managing Roo's custom operational modes, providing programmatic control over mode configuration and management.

• 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

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• list_modes — The list_modes tool exposed by this server
• get_mode — The get_mode tool exposed by this server
• create_mode — Parameters: - slug: Unique identifier (lowercase letters, numbers, and hyphens) - name: Display name for the mode - roleDefinition: Detailed
• update_mode — Parameters: - slug: The unique identifier of the mode to update - updates: Object containing the fields to update (name, roleDefinition, groups
• delete_mode — Parameters: - slug: The unique identifier of the mode to delete
• validate_mode — Parameters: - mode: Complete mode configuration object to validate

Credentials and setup notes

Configuration is passed through the environment: MODES_CONFIG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Modes's toolset — list_modes, get_mode, create_mode and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ccc0168; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.