Allows exporting test cases as Markdown formatted for use in Confluence.
Allows exporting test cases as Markdown formatted for use in GitHub.
Allows exporting test cases as Markdown formatted for use in Notion.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Test Case Generator MCP Server generate test cases for project my-app, feature user login"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
npm installRelated MCP server: QAcito
Edit your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"testcases": {
"command": "node",
"args": ["/absolute/path/to/testcase-mcp-server/server.js"]
}
}
}Restart Claude Desktop.
Tool | What it does |
| Auto-generate test cases from a feature description |
| Manually add a single custom test case |
| List all test cases (with filters) |
| Mark a test as PASS / FAIL / SKIPPED |
| Get a pass/fail summary report |
| See all projects |
| Export test cases as Markdown for Notion/GitHub/Confluence |
| Delete a project |
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 PASSTest cases are saved to ./testcase-data/projects.json — a plain JSON file
you can open, edit, or back up any time.
Manually add a single custom test case to a project.
Inputs: steps (required), title (required), feature (required), project (required), +6 more.
Delete all test cases for a project.
Inputs: confirm (required), project (required).
Export all test cases for a project as a Markdown document (ready to paste into Notion, GitHub, Confluence, etc.)
Inputs: project (required), feature.
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.
Inputs: feature (required), project (required), description (required), type.
List all projects that have test cases stored.
Inputs: no named parameters.
List all test cases for a project. Optionally filter by feature, type, priority, or status.
Inputs: project (required), type, status, feature, +1 more.
Get a summary report of all test cases in a project — pass/fail counts, coverage by feature, and pending items.
Inputs: project (required).
Update the status of a test case after running it (PASS, FAIL, SKIPPED).
Inputs: id (required), status (required), project (required), notes.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Create and manage test cases, test runs and results in Testiny from your AI assistant.
Write, run and check natural-language browser tests of your web app from your AI assistant.
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
