Robot Framework MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_login_test_caseA | Generate Robot Framework test case code for login functionality. Returns the complete .robot file content as text - does not execute the test. |
| create_page_object_loginB | Generate Robot Framework page object model code for login page. Returns .robot file content as text - does not execute. |
| create_advanced_selenium_keywordsA | Generate Robot Framework keywords for advanced Selenium operations. Returns .robot file content as text - does not execute. |
| create_extended_selenium_keywordsA | Generate extended Robot Framework keywords for screenshots, performance monitoring, and window management. Returns .robot file content as text - does not execute. |
| create_performance_monitoring_testA | Generate Robot Framework performance monitoring test code. Returns complete .robot file content as text - does not execute. |
| create_data_driven_testB | Generate Robot Framework data-driven test template code. Returns .robot file content as text - does not execute. |
| create_api_integration_testB | Generate Robot Framework API integration test code. Returns .robot file content as text - does not execute. |
| validate_robot_framework_syntaxB | Validate Robot Framework syntax and provide suggestions. Returns validation report as text - does not execute code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct by focusing on different test types (e.g., API integration, data-driven, performance monitoring), but there is notable overlap between 'create_advanced_selenium_keywords' and 'create_extended_selenium_keywords'—both generate Selenium-related keywords, which could confuse an agent about which to use for specific Selenium tasks. The descriptions help differentiate them slightly, but the boundaries are fuzzy.
All tool names follow a consistent 'create_*' or 'validate_*' verb_noun pattern with snake_case, making them predictable and easy to parse. The naming convention is uniform across all eight tools, with no deviations in style or structure.
With 8 tools, the count is reasonable and well-scoped for a Robot Framework code generation server, covering various test types and a validation tool. It's slightly on the higher side but not excessive, as each tool serves a distinct purpose in test creation, though some overlap exists.
The server covers code generation for multiple test scenarios (Selenium, API, data-driven, login, performance) and includes syntax validation, but there are notable gaps: it lacks tools for executing tests, managing test suites, or handling other common Robot Framework operations like variable management or reporting. This limits the workflow to creation-only, which agents might find incomplete for full test automation.