Skip to main content
Glama

Related Servers

Alternatives to RobotMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive Robot Framework through natural language, discovering keywords, running live test steps across web, mobile, API, database, and desktop targets, and generating clean .robot test suites from plain-English instructions.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables generating Robot Framework test cases with SeleniumLibrary, creating page object models, and performing performance monitoring through natural language.
      7 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables agents to work with Robot Framework by discovering tests and resources, drafting tests from requirements, dry-running and executing suites, and parsing output.xml results.
      6
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables QA to interactively inspect DOM elements in a visible browser, generate resilient Robot Framework locators and Page Objects, and validate selectors via natural language.
      7
      BSD 2-Clause "Simplified"
    • A
      license
      A
      quality
      A
      maintenance
      RobotMCP is a comprehensive Model Context Protocol (MCP) server that bridges the gap between human language and Robot Framework automation. It enables AI agents to understand test intentions, execute steps interactively, and generate complete test suites from successful executions.
      19
      1,692 PyPI
      114
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation3/5

    The set has several overlapping clusters: session creation (analyze_scenario vs manage_session init), execution (intent_action, execute_step, execute_batch, execute_flow), and keyword/library discovery (recommend_libraries, find_keywords, get_keyword_info, check_library_availability). The detailed descriptions help differentiate these tools, but the boundaries are not always obvious, and two discovery tools share the same 'No keyword with name' trigger.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern such as execute_batch, recommend_libraries, and build_test_suite. A few names deviate—intent_action is noun-oriented and visual_check is adjective+noun—but the overall convention is consistent and readable.

    Tool Count3/5

    19 tools is on the heavy side and includes several near-duplicate discovery and execution aids that could be consolidated. However, the server covers a broad workflow from scenario analysis through suite generation and visual validation, so the count is not unreasonable for its scope.

    Completeness4/5

    The workflow from scenario analysis through keyword discovery, execution, batching, suite generation, and running is well covered. Minor gaps exist, such as no explicit session teardown/reset action and some redundancy among discovery helpers, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo issues