Rovodev CLI MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rovodev CLI MCP ask Rovodev agent to list my active sessions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Rovodev CLI MCP
An MCP server wrapper that exposes Rovodev CLI as MCP tools. Modeled after gemini-mcp-tool.
Install
npm install -g rovodev-cli-mcpOr use with npx:
npx -y rovodev-cli-mcpRelated MCP server: claude-cli-mcp
Configure in Claude Desktop
{
"mcpServers": {
"rovodev": {
"command": "npx",
"args": ["-y", "rovodev-cli-mcp"]
}
}
}Environment variables to customize underlying CLI:
ROVODEV_CLI_PATHorROVODEV_CMD(default:acli)ROVODEV_SUBCOMMAND(default:"rovodev run")ROVODEV_CONFIG_FLAG(default:--config-file)ROVODEV_SHADOW_FLAG(default:--shadow)ROVODEV_VERBOSE_FLAG(default:--verbose)ROVODEV_RESTORE_FLAG(default:--restore)ROVODEV_YOLO_FLAG(default:--yolo)ROVODEV_HELP_FLAG(default:--help)
Chunking configuration (for large responses):
MCP_CHUNK_SIZE(preferred)ROVODEV_CHUNK_SIZE(legacy) The first one found is used; default is 20000 characters if none are set.
Global setup for Claude Code (user scope)
Install the MCP server for your user so it’s available across projects in Claude Code.
Add with npx (no global npm install required):
claude mcp add -s user rovodev -- npx -y rovodev-cli-mcpOptional: use a globally installed binary instead of npx
npm i -g rovodev-cli-mcp claude mcp add -s user rovodev rovodev-cli-mcpOptional: set environment overrides when adding
claude mcp add -s user rovodev -- \ npx -y rovodev-cli-mcp \ -e ROVODEV_CLI_PATH=acli \ -e ROVODEV_SUBCOMMAND="rovodev run" \ -e ROVODEV_CONFIG_FLAG=--config-file \ -e ROVODEV_SHADOW_FLAG=--shadow \ -e ROVODEV_VERBOSE_FLAG=--verbose \ -e ROVODEV_RESTORE_FLAG=--restore \ -e ROVODEV_YOLO_FLAG=--yolo \ -e ROVODEV_HELP_FLAG=--helpVerify it’s connected:
claude mcp listRemove from user scope (to update or uninstall):
claude mcp remove -s user rovodev
Global setup for Amazon Q CLI
Install the MCP server for Amazon Q CLI to use Rovodev tools in Q chat sessions.
Add with npx (no global npm install required):
q mcp add --name rovodev --command npx --args "-y,rovodev-cli-mcp"Optional: set environment variables when adding
q mcp add --name rovodev --command npx --args "-y,rovodev-cli-mcp" \ --env "ROVODEV_CLI_PATH=acli" \ --env "ROVODEV_SUBCOMMAND=rovodev run"Verify it's installed:
q mcp listCheck server status:
q mcp status --name rovodevRemove (to update or uninstall):
q mcp remove --name rovodev
Using tools in Q CLI: Tools are available with the rovodev___ prefix:
rovodev___ask-rovodev- Send messages to Rovodev agent (enhanced with session support)rovodev___tap-rovodev- Alias for ask-rovodevrovodev___session_manager- Manage isolated sessions for context persistencerovodev___health_check- Check server health and CLI availabilityrovodev___diagnostics- Get comprehensive system diagnosticsrovodev___next-chunk- Fetch next chunk for large responsesrovodev___fetch-chunk- Fetch specific chunk by indexrovodev___Help- Show Rovodev CLI helprovodev___Ping- Test connectivity
Local development with Claude Code
If you are iterating on this repo and want Claude Code to use your local build:
Install deps and build
npm i
npm run buildPoint Claude Code at your local
dist/index.js
claude mcp remove -s user rovodev || true
claude mcp add -s user rovodev -- node "$(pwd)/dist/index.js"Verify connection
claude mcp listOptional: quick smoke test (no Claude required)
node scripts/smoke.mjsNotes:
This server communicates over stdio. Do not print to stdout; only stderr is safe for logs.
The server already routes logs to stderr; if you add logs, follow the same pattern.
You can still register via
npx -y rovodev-cli-mcp, but during development usingnode dist/index.jsavoids npm network hiccups.
Troubleshooting
"Failed to connect" in
claude mcp listEnsure your Node is >= 18 (
node -v).Ensure no output is written to stdout (stdout is reserved for the MCP protocol). This repo's logger writes to stderr only.
Try registering the local path:
claude mcp add -s user rovodev -- node "$(pwd)/dist/index.js".If using WSL, register from the Linux side; Claude Code on Windows can discover WSL user-scoped config.
Authentication errors (API key issues)
If you see "Authentication Error" messages, your rovodev CLI API key may be expired or invalid
Check your rovodev CLI configuration and update your API key
The server now detects authentication issues and provides clear error messages instead of hanging
Underlying CLI not found
The default command is
acli. Install it or override:
claude mcp add -s user rovodev -- \ node "$(pwd)/dist/index.js" \ -e ROVODEV_CLI_PATH=/path/to/your/cliLarge responses
Use
ask-rovodevfirst. If the response is chunked, callnext-chunkrepeatedly with the providedcacheKey. You can also fetch a specific page withfetch-chunk.Tune chunk size with env vars (in order of precedence):
MCP_CHUNK_SIZE, then legacyROVODEV_CHUNK_SIZE.
Tools and streaming
This server supports streaming chunk-caching to reduce memory usage for large outputs. The ask-rovodev tool streams the CLI output directly into a chunk cache. If the output exceeds the page chunk size, it returns the first chunk and a cacheKey so you can fetch subsequent chunks with next-chunk or fetch-chunk.
Tools
Enhanced Core Tools
ask-rovodev:{ message?: string, prompt?: string, configFile?: string, shadow?: boolean, verbose?: boolean, restore?: boolean, yolo?: boolean, sessionId?: string, retries?: number, backoffMs?: number, args?: string[], pagechunksize?: number }New: Session isolation with
sessionId, retry logic withretries/backoffMsDefault:
yolomode is enabled for non-interactive MCP usage; setyolo: falseto disable if you need interactive behavior.Tip: If your message starts with dashes (e.g.,
--example), the underlying CLI may interpret it as a flag. The server inserts--before such messages to prevent flag parsing.
tap-rovodev: alias ofask-rovodev
Session Management
session_manager:{ action: "create" | "destroy" | "list" | "get" | "cleanup", sessionId?: string, timeoutMs?: number }Manage isolated sessions for maintaining context across multiple commands
Health & Diagnostics
health_check:{ detailed?: boolean }Check server health including CLI availability, session manager status, and environment configuration
diagnostics:{ includePerformance?: boolean, includeHealth?: boolean, includeSessions?: boolean, includeSystem?: boolean, includeRecentExecutions?: boolean, recentLimit?: number }Get comprehensive system diagnostics including performance metrics and resource usage
Utility Tools
next-chunk:{ cacheKey: string }Fetch the next chunk sequentially from a cached large responsefetch-chunk:{ cacheKey: string, chunkIndex: number }(optional) Fetch a specific chunk by indexHelp: show help from underlying CLIPing: connectivity test
Server behavior and tuning via env vars:
Logging level:
MCP_LOG_LEVEL(debug | info | warn | error | silent)Exec timeout:
MCP_EXEC_TIMEOUT_MS(kill underlying CLI after N ms; includes partial stdout tail in error)Max stdout buffer:
MCP_MAX_STDOUT_SIZE(maximum output buffer size before termination)Working directory:
MCP_CWD(set process cwd for the underlying CLI)Chunk cache TTL:
MCP_CHUNK_TTL_MS(default 20 minutes)Chunk cache max entries:
MCP_CHUNK_MAX_ENTRIES(default 500)
Handling large responses (simple sequential flow)
If the output is too large, the first
ask-rovodevcall returns page 1 plus acacheKey:Response header example:
cacheKey: <key>,chunk: 1/N
To continue, call
next-chunkwith the samecacheKeyto get chunk 2, then 3, etc. until it reports no further chunks.
Available Tools
9 toolsask-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.
Inputs: args, yolo, prompt, shadow, +8 more.
diagnosticsA
Get comprehensive diagnostics information including performance metrics, health status, session statistics, and system information.
Inputs: recentLimit, includeHealth, includeSystem, includeSessions, +2 more.
fetch-chunkA
Fetch a specific chunk from a previously cached large response (from ask-rovodev)
Inputs: cacheKey (required), chunkIndex (required).
health_checkB
Check the health status of the Rovodev CLI MCP server, including Rovodev CLI availability, session manager status, and environment configuration.
Inputs: detailed.
HelpA
Show underlying Rovodev CLI help output
Inputs: no named parameters.
next-chunkB
Fetch the next chunk for a previously cached large response (from ask-rovodev)
Inputs: cacheKey (required).
PingA
Echo back a message for testing
Inputs: message.
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.
Inputs: action (required), sessionId, timeoutMs.
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.
Inputs: args, yolo, prompt, shadow, +8 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Build, test, publish, and run Kovca workflows from AI agents over remote MCP.
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceExposes a set of CLI tools (test generation, documentation generation, linting, test running, code search) to AI assistants via MCP, allowing them to perform these tasks through natural language.3-
- AlicenseAqualityDmaintenanceWraps Anthropic Claude Code CLI as tools, allowing MCP clients to invoke headless Claude Code sessions.2324 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes opencode's coding agent and shell as MCP tools, enabling MCP-only AI clients to execute shell commands, manage files, and run agent sessions with async job handling.MIT
- FlicenseBqualityCmaintenanceEnables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.15-