RobotMCP
Related Servers
Alternatives to RobotMCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables generating and managing Robot Framework test automation with SeleniumLibrary, including test case generation, page object models, and advanced web testing capabilities.812 npm61 PyPI30MIT
- FlicenseBqualityCmaintenanceAn MCP server for analyzing Robot Framework test results. It provides LLMs with tools to parse, summarize, and search through test execution logs from XML or JSON output files.32-
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceA 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.3GNU Lesser General Public v2.1 only

Snowfort Circuit MCPofficial
FlicenseNot gradedqualityDmaintenanceA 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-- AlicenseNot gradedqualityBmaintenanceAn 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.382MIT
TDQS
Scored across 19 tools
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.
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.
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.
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.