About
A Model Context Protocol server that manages the .roomodes JSON file, allowing listing, creation, and updating of custom modes via reliable API calls.
Capabilities
Overview
The Roo Code Custom Mode Editor MCP server is a lightweight service that gives AI assistants direct, safe access to the configuration file used by Roo Code. Rather than having developers manually edit JSON or perform risky file writes, this server exposes a set of high‑level tools that abstract away the low‑level details. It solves the common problem of maintaining consistent, version‑controlled custom mode definitions while still allowing dynamic updates from an AI workflow.
By running as a standalone MCP server, the editor integrates seamlessly with any toolchain that understands the Model Context Protocol. Developers can add it to their MCP settings and invoke its tools from within Claude, ChatGPT, or any other AI client. The server performs all file I/O internally, ensuring that the file remains valid JSON and preventing accidental corruption from manual edits. This reliability is especially valuable in collaborative environments where multiple assistants or scripts may need to read or modify custom modes concurrently.
Key capabilities include:
- Listing all existing custom modes, giving an overview of available configurations.
- Creating a new mode by supplying required fields (, , , , and optional ).
- Retrieving the full set of fields for a specified mode, enabling introspection or display to users.
- Updating one or more fields of an existing mode, allowing incremental changes without overwriting the entire file.
These tools are intentionally simple yet powerful: each operation maps to a single JSON manipulation, so developers can compose complex workflows by chaining tool calls. For example, an AI assistant could list modes, prompt the user for a new name, and then update that field—all within a single conversation.
Typical use cases involve rapid prototyping of new assistant personas or project‑specific behavior tweaks. In a continuous‑integration pipeline, an AI could automatically generate a custom mode based on test results and then publish it to the repository. In a team setting, non‑technical members could request changes through chat, while the MCP server guarantees that the underlying file remains consistent and version‑controlled.
Overall, the Roo Code Custom Mode Editor MCP server provides a reliable bridge between AI assistants and the configuration, reducing friction for developers, preventing file corruption, and enabling dynamic, AI‑driven customization workflows.
Related Servers
MCP Filesystem Server
Secure local filesystem access via MCP
Google Drive MCP Server
Access and manipulate Google Drive files via MCP
Pydantic Logfire MCP Server
Retrieve and analyze application telemetry with LLMs
Swagger MCP Server
Dynamic API Tool Generator from Swagger JSON
Rust MCP Filesystem
Fast, async Rust server for efficient filesystem operations
Goodnews MCP Server
Positive news at your fingertips
Weekly Views
Server Health
Information
Explore More Servers
MCP Network Sentinel
Secure your MCP servers with real-time network monitoring
Rember MCP Server
Create spaced‑repetition flashcards from Claude chats and PDFs
Fluxinc DICOM MCP Server
DICOM connectivity testing made simple
Instadev MCP Server
Next-Gen Development Platform for Rapid Prototyping
Neovim MCP Server
Expose Neovim to external tools via Unix socket
MySQL MCP Server
Natural language to SQL for AI models