Test Case Generator MCP Server
# Test Case Generator MCP Server
An MCP server that auto-generates and manages test cases for any project.
Connect it to Claude and generate comprehensive test cases just by describing a feature.
---
## Setup
```bash
npm install
```
---
## Connect to Claude Desktop
Edit your Claude Desktop config file:
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
```json
{
"mcpServers": {
"testcases": {
"command": "node",
"args": ["/absolute/path/to/testcase-mcp-server/server.js"]
}
}
}
```
Restart Claude Desktop.
---
## Available Tools
| Tool | What it does |
|------|-------------|
| `generate_test_cases` | Auto-generate test cases from a feature description |
| `add_test_case` | Manually add a single custom test case |
| `list_test_cases` | List all test cases (with filters) |
| `update_status` | Mark a test as PASS / FAIL / SKIPPED |
| `project_report` | Get a pass/fail summary report |
| `list_projects` | See all projects |
| `export_markdown` | Export test cases as Markdown for Notion/GitHub/Confluence |
| `delete_project` | Delete a project |
---
## Example prompts to use with Claude
```
Generate test cases for project "my-app", feature "user login",
description "user enters email and password, system validates and creates a session"
List all CRITICAL priority test cases for project "my-app"
Give me a report for project "my-app"
Export test cases for project "my-app" as markdown
Mark test TC-1234-ABCD in project "my-app" as PASS
```
---
## Data storage
Test cases are saved to `./testcase-data/projects.json` — a plain JSON file
you can open, edit, or back up any time.
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.