Skip to main content
Glama
yanggf8

Rovodev CLI MCP

by yanggf8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Rovodev CLI MCP

No user-submitted related servers found.

    Related Servers

    • kagero by niwa-labs

      kageroofficial

      niwa-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables unified access to multiple coding-agent CLIs via MCP, with tools for running prompts, managing sessions, and retrieving task outputs.
      MIT

    • LinkTerm v2

      silencebadwolf
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools for terminal session control, serial/SSH/Shell connections, workspace configuration, J-Link debugging, RTT logging, and UI interaction, enabling AI hosts to collaboratively operate embedded development workflows.
      AGPL 3.0

    • Terminal Session Manager

      danieldoalto
      F
      license
      B
      quality
      B
      maintenance
      Enables 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
      -

    • opencode-mcp-bridge

      nmt3325
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 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.
      14 npm
      1
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation2/5

    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.

    Naming Consistency2/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources