MCP.so
ログイン

Modes MCP Server

@ccc0168

基本情報

カテゴリ

その他

トランスポート

stdio

作者

ccc0168

Modes MCP Server について

MCP server for managing Roo's custom operational modes

#modes-mcp-server#mcp-server#operational-modes

Modes MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "modes": {
      "command": "node",
      "args": [
        "/path/to/modes-mcp-server/build/index.js"
      ],
      "env": {
        "MODES_CONFIG_PATH": ""
      }
    }
  }
}

Modes MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Modes MCP Server?

An MCP server for managing Roo’s custom operational modes, providing full CRUD operations, schema validation with Zod, and file system watching for configuration changes. It is intended for developers and operators who need programmatic control over mode definitions and their lifecycle.

How to use Modes MCP Server?

Clone the repository, install dependencies with npm install, build with npm run build, then configure the environment variable MODES_CONFIG_PATH (defaults to a path under %APPDATA%) and add the server to your MCP settings file. Start the server with npm start. Use the provided tools (list_modes, get_mode, create_mode, update_mode, delete_mode, validate_mode) to manage modes.

Key features of Modes MCP Server

  • Full CRUD operations for custom modes
  • Schema validation using Zod
  • File system watching for config changes
  • Standard MCP error codes (InvalidParams, MethodNotFound, InternalError)
  • Atomic file operations
  • Pre‑defined core system and specialized mode templates

Use cases of Modes MCP Server

  • Programmatically create, read, update, and delete custom operational modes
  • Validate a mode configuration before saving it
  • Manage mode transitions following a natural workflow flow
  • Integrate mode management into larger automation or orchestration pipelines

よくある質問

1

What does Modes MCP Server do vs alternatives?

It provides a dedicated MCP interface for managing Roo’s custom modes, with built-in schema validation and atomic file operations. The README does not compare it to other tools.

2

What runtime or dependencies are required?

Node.js and npm are required. Dependencies are installed via `npm install`. No other runtime is mentioned.

3

Where does the mode configuration data live?

The configuration file path is set via the `MODES_CONFIG_PATH` environment variable. By default it points to `%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json`.

4

What transport does the server use?

The server is an MCP server; the README does not explicitly state the transport, but standard MCP servers typically use stdio. No other transport is mentioned.

5

What authentication does the server require?

No authentication is mentioned in the README.

コメント

「その他」の他のコンテンツ