Test Case Generator 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_test_casesA | Analyze a feature or function description and auto-generate comprehensive test cases. Covers: happy path, edge cases, negative tests, boundary values, and security basics. Saves them to the project store and returns the full list. |
| add_test_caseA | Manually add a single custom test case to a project. |
| list_test_casesA | List all test cases for a project. Optionally filter by feature, type, priority, or status. |
| update_statusB | Update the status of a test case after running it (PASS, FAIL, SKIPPED). |
| project_reportA | Get a summary report of all test cases in a project — pass/fail counts, coverage by feature, and pending items. |
| list_projectsA | List all projects that have test cases stored. |
| export_markdownA | Export all test cases for a project as a Markdown document (ready to paste into Notion, GitHub, Confluence, etc.) |
| delete_projectA | Delete all test cases for a project. |
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
Each tool targets a distinct operation: generation, reporting, manual creation, listing, status updates, project listing, export, and project deletion. Potential overlap between generate and add is clearly differentiated by automatic vs manual.
Most tools follow verb_noun pattern (generate_test_cases, add_test_case, list_test_cases, update_status, delete_project). However, project_report deviates as a noun-based name, and delete_project could be misinterpreted as deleting the project rather than its test cases.
With 8 tools covering generation, management, reporting, and export, the set is well-scoped for a test case generation server. Each tool serves a clear purpose without redundancy.
Core workflows are covered: generate/add, list, update status, report, export, and delete project. Missing individual test case deletion and editing details are minor gaps that don't break the primary use case.