Rovodev CLI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CWD | No | Working directory for the underlying CLI. | |
| ROVODEV_CMD | No | Alternative to ROVODEV_CLI_PATH to specify the CLI command. | acli |
| MCP_LOG_LEVEL | No | Logging level: debug, info, warn, error, silent. | |
| MCP_CHUNK_SIZE | No | Preferred chunk size for large responses (first found used, default 20000). | 20000 |
| MCP_CHUNK_TTL_MS | No | Chunk cache TTL in milliseconds (default 20 minutes). | 1200000 |
| ROVODEV_CLI_PATH | No | Path to the underlying CLI executable. Alternative: ROVODEV_CMD. | acli |
| ROVODEV_HELP_FLAG | No | Flag to show help. | --help |
| ROVODEV_YOLO_FLAG | No | Flag to enable yolo mode. | --yolo |
| ROVODEV_CHUNK_SIZE | No | Legacy chunk size variable (first found used, default 20000). | 20000 |
| ROVODEV_SUBCOMMAND | No | Subcommand passed to the CLI. | rovodev run |
| MCP_EXEC_TIMEOUT_MS | No | Execution timeout in milliseconds. | |
| MCP_MAX_STDOUT_SIZE | No | Maximum stdout buffer size before termination. | |
| ROVODEV_CONFIG_FLAG | No | Flag to specify config file. | --config-file |
| ROVODEV_SHADOW_FLAG | No | Flag to enable shadow mode. | --shadow |
| ROVODEV_RESTORE_FLAG | No | Flag to enable restore mode. | --restore |
| ROVODEV_VERBOSE_FLAG | No | Flag to enable verbose output. | --verbose |
| MCP_CHUNK_MAX_ENTRIES | No | Maximum number of chunk cache entries (default 500). | 500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-rovodevB | Invoke Rovodev agent via 'acli rovodev run'. Always runs in yolo mode (non-interactive) for MCP usage. Supports flags like --config-file, --shadow, --verbose, --restore. |
| PingA | Echo back a message for testing |
| HelpA | Show underlying Rovodev CLI help output |
| fetch-chunkA | Fetch a specific chunk from a previously cached large response (from ask-rovodev) |
| next-chunkB | Fetch the next chunk for a previously cached large response (from ask-rovodev) |
| session_managerA | Manage isolated sessions for Rovodev CLI operations. Each session has its own working directory and can be used to maintain context across multiple commands. |
| health_checkB | Check the health status of the Rovodev CLI MCP server, including Rovodev CLI availability, session manager status, and environment configuration. |
| diagnosticsA | Get comprehensive diagnostics information including performance metrics, health status, session statistics, and system information. |
| tap-rovodevB | Invoke Rovodev agent via 'acli rovodev run'. Always runs in yolo mode (non-interactive) for MCP usage. Supports flags like --config-file, --shadow, --verbose, --restore. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ask-rovodev | Send a message to the Rovodev CLI agent |
| Ping | Ping the server |
| Help | Display help for the underlying CLI |
| fetch-chunk | Fetch a specific chunk of a prior large response |
| next-chunk | Fetch the next chunk of a prior large response |
| tap-rovodev | Send a message to the Rovodev CLI agent |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Multiple tools have identical or overlapping purposes: 'ask-rovodev' and 'tap-rovodev' have exactly the same description, making them indistinguishable. 'fetch-chunk' and 'next-chunk' both deal with chunks from cached responses, though they are differentiated. 'diagnostics' and 'health_check' also overlap in providing system information.
Tool names follow no consistent pattern: some use hyphens (ask-rovodev, fetch-chunk), some underscores (health_check, session_manager), some are capitalized (Help, Ping), others lowercase. Verbs and nouns are mixed without clear convention.
With 9 tools, the count falls within the typical 3-15 range. However, the presence of two identical tools (ask-rovodev and tap-rovodev) suggests the set could be streamlined. Overall, the number is reasonable for the server's purpose.
The tool surface covers the core operations of invoking the Rovodev agent, managing sessions, and checking health, but lacks lifecycle management for sessions (e.g., listing, deleting) and config management beyond flags. The duplicate tool indicates unnecessary redundancy.