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
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server suite that enables AI coding agents to automate both web browsers and Electron desktop applications with auto-snapshots and element references.
      60
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents eyes and hands to visually interact with running apps across 10 platforms, enabling natural language-driven testing and automation without test code.
      382
      MIT

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation3/5

    Several tools overlap in purpose: execute_batch, execute_step, execute_flow, and run_test_suite all execute Robot Framework code, and find_keywords vs get_keyword_info both serve keyword discovery. The detailed descriptions clarify boundaries, but an agent could still misselect between execution tools or keyword-lookup tools without careful reading.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (execute_batch, manage_session, build_test_suite). A few deviate: intent_action is noun_verb, visual_check is adjective_verb, and manage_attach is vague. Overall the pattern is predictable with minor inconsistencies.

    Tool Count3/5

    With 19 tools, this exceeds the ideal 3-15 range but is not excessive for a comprehensive Robot Framework automation server. The count is justified by the breadth of functionality (session management, keyword discovery, execution, suite building, visual checks), but it feels slightly heavy.

    Completeness4/5

    The tool surface covers the full lifecycle from scenario analysis (analyze_scenario) through keyword discovery and execution (execute_step/batch/flow) to suite generation (build_test_suite) and validation (run_test_suite). Minor gaps exist, such as explicit test result retrieval or test data management, but the core workflows are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow