Automation Script Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN | Yes | Your Notion integration token used to access the Notion API. | |
| GEMINI_API_KEY | Yes | Your Google Gemini API key used for generating Playwright scripts. | |
| NOTION_DATABASE_ID | Yes | The ID of the Notion database containing your test tickets. |
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 |
|---|---|
| process_test_scenarioB | Process a test scenario provided directly by the user and generate complete WDIO test files |
| analyze_repository_patternsC | Read and analyze repository for existing patterns, formats, and validation rules |
| generate_feature_fileC | Generate WDIO feature file with Gherkin syntax (Given, When, Then) |
| generate_steps_fileB | Generate WDIO step definitions file with functions to execute Gherkin syntax |
| generate_page_fileC | Generate WDIO page object file with general functions and element selectors |
| generate_component_fileC | Generate component file with collection of data items (only if needed) |
| review_and_enhance_codeC | Review generated code and enhance it with improvements, documentation, validation, POM patterns, and reusable functions |
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 7 tools
Most tools have distinct purposes targeting different file types or stages in the test automation workflow. However, 'process_test_scenario' could overlap with the individual file generation tools, as it generates complete WDIO test files which might include components the other tools create separately. The descriptions help clarify but some ambiguity remains.
All tool names follow a consistent verb_noun pattern with snake_case, using clear action verbs like 'analyze', 'generate', 'process', and 'review'. The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 7 tools, this server is well-scoped for generating WDIO automation scripts. Each tool serves a specific role in the workflow, from analysis to file generation and enhancement, making the count appropriate and efficient for the domain without being overwhelming or insufficient.
The tool set covers the core lifecycle of test automation generation, including analysis, file creation for components, features, pages, and steps, processing scenarios, and code review. A minor gap exists in lacking explicit tools for updating or deleting generated files, but agents can work around this by regenerating or using the review tool for modifications.