MCP Test Case Generator
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_test_casesA | Generate comprehensive test cases from requirements, user stories, or API specs (with auto Excel export) |
| read_requirement_fileB | Read requirement file from local filesystem (supports .md, .txt, .json, .yml, .yaml, .doc, .docx, .pdf) |
| scan_requirement_directoryB | Scan directory for requirement files and list them |
| generate_test_cases_from_fileB | Read requirement file and generate test cases from its content |
| export_to_excelB | Export generated test cases to Excel file (.xlsx format) |
| generate_automation_testsB | Generate automation test code from test cases (supports Playwright) |
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 6 tools
Tools are mostly distinct, but generate_test_cases and generate_test_cases_from_file have overlapping purposes, though descriptions clarify the difference. The export_to_excel tool may be redundant if generate_test_cases auto-exports.
All tool names follow a consistent verb_noun pattern with underscores, making them predictable and easy to understand.
With 6 tools, the set is well-scoped for a test case generator, covering file reading, generation, export, and automation code generation without overloading.
Core workflow of reading requirements, generating test cases, exporting to Excel, and generating automation tests is covered. Minor gaps like specifying output paths or managing in-memory test cases are absent but not critical.