ai-testcase-generator-mcp
Click on "Install 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., "@ai-testcase-generator-mcpGenerate test plan for POST /users with payload {name, email}"
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.
π€ AI Testcase Generator MCP
An Model Context Protocol(MCP) server that generates comprehensive API test plans (positive, negative, and boundary/edge cases) directly from endpoint metadataβpowered by LLMs.
This is a TypeScript-based Model Context Protocol(MCP) server for QA engineers. It demonstrates core Model Context Protocol concepts by providing:
AI-powered tool for generating exhaustive test case plans from API endpoints and payloads
Prompt-driven LLM integration for quality and coverage
Extensible structure for future automation tooling
β¨ Features
π MCP-compliant server (
stdiotransport).π Tool:
generate_tests_excelInput: endpoint, HTTP method, payload, extra context.
Input options:
Direct endpoint details: endpoint, HTTP method, payload
Use extraContext to provide any additional testing notes or constraints
OutputPut: π Excel test plan with columns: Sl no, Test Name, Pre-Condition, Steps, Expected Result.
π§ Prompt-driven test generation with configurable LLM (Groq, OpenAI, Anthropic).
π Detailed logging with Winston.
Related MCP server: Swagger Testcase MCP
ποΈ Architecture
flowchart TD
A[Claude / MCP Client] -->|Run Tool| B[MCP Server]
B -->|Prompt| C[LLM API]
C -->|Test Cases JSON| B
B -->|Excel Export| D[(Test Plan .xlsx)]
B -->|Logs| E[Server Log File]π Project Structure
ai-testcase-designer-mcp/
βββ build/ # Compiled JavaScript output
βββ assets/ # Demo gifs, images, and sample files
β βββ demo.gif
β βββ excel_preview.png
β βββ sample_chat_message.txt
βββ configs/
β βββ config.json # Server/tool config
βββ src/
β βββ index.ts # Main server entry point (MCP interface & routing)
β βββ excel.ts # Excel file creation & writing logic (modular)
β βββ logger.ts # Winston logger configuration & log writing (modular)
β βββ prompts/
β βββ testcase_prompt.txt # Prompt template for LLM-based test generation
βββ package.json
βββ tsconfig.json
βββ README.md
βββ .gitignoresrc/excel.ts: Handles all Excel (.xlsx) file creation and test plan export (modularized).
src/logger.ts: Provides modular logging functionality across the MCP server using Winston.
src/prompts/: Contains prompt templates for LLM-driven test generation.
assets/: Demo GIFs, Excel sample preview, and chat prompt examples.
π₯ Demo
Hereβs the MCP generating test cases and exporting to Excel:

π Excel Preview
Below is a quick preview of the generated test cases:

Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchβοΈ Installation
Follow these steps to set up the AI Testcase Designer MCP server locally:
Clone the repository
git clone https://github.com/yourusername/ai-testcase-designer-mcp.git cd ai-testcase-designer-mcpInstall dependencies
npm installBuild the server
npm run buildConfigure the server in your MCP client
a. Claude Desktop or any MCP-compatible client
Add the following server configuration:
On MacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.json
{ "mcpServers": { "ai-testcase-designer-mcp": { "disabled": false, "timeout": 60, "command": "node", "args": [ "c:/Auto_WS/ai-testcase-designer-mcp/build/index.js" ], "transportType": "stdio" } } }b. Cline (VS Code Extension)
Quick Start:
Install Cline from the VS Code Marketplace.
Open the Cline sidebar (from the VS Code activity bar).
Go to the "MCP Servers" section and click "Add New MCP Server".
Fill in the server details:
{ "mcpServers": { "ai-testcase-designer-mcp": { "disabled": false, "timeout": 60, "command": "node", "args": [ "c:/Auto_WS/ai-testcase-designer-mcp/build/index.js" ], "transportType": "stdio" } } }Test the connection and save.
For a visual step-by-step guide, see below:


For detailed Cline guidance, see the official docs:
cline.bot/getting-started/installing-cline#vs-code-marketplace%3A-step-by-step-setup
c. Hermes Agent
Add the following server configuration to
~/.hermes/config.yamlundermcp_servers:
mcp_servers:
ai-testcase-designer-mcp:
command: "node"
args: ["/absolute/path/to/ai-testcase-designer-mcp/build/index.js"]π API Key & Work Directory Setup
To use the AI Testcase Designer MCP.
Get your Groq API key from here for free: https://console.groq.com/keys
A working directory (WORK_DIR) where generated Excel test plans and server logs will be saved.
Update your config.json file like this:
{
"MODEL_API_KEY": "gsk_7Ma3Fabcd <your-api-key-here>",
"WORK_DIR": "C:/Auto_WS/ai-testcase-designer-mcp"
}How to Use
π₯οΈ Open Claude Desktop (or any MCP-compatible client).
π Download Sample Chat Message: sample_chat_message.txt and copy its content.
βοΈ Paste the content into the chat and send the message: the AI will generate detailed test cases in Excel format.
πΎ Generated Excel files and server logs are saved in your
WORK_DIRfolder.
βΆοΈ Example Request
{
"name": "generate_tests_excel",
"arguments": {
"endpoint": "https://api.example.com/v1/users",
"method": "POST",
"payload": {
"name": "John Doe",
"email": "john@example.com"
},
"extraContext": "Focus on invalid email and empty payload scenarios."
}
}π Example Excel Output
Sl no | Test Name | Pre-Condition | Steps | Expected Result |
1 | Valid User Create | DB is empty | Send POST with valid payload | User created successfully |
2 | Missing Email | DB is empty | Send POST with name only | 400 validation error |
3 | Invalid Email | DB is empty | Send POST with invalid email format | 422 error message |
π Files Output
Files are written to: ./workdir/generated/
Sample Log Output
2025-09-13T10:22:11 [info]: [Step1] Incoming request: endpoint=/v1/users, method=POST
2025-09-13T10:22:11 [info]: [Step2] Building LLM prompt...
2025-09-13T10:22:13 [info]: [Step5] Converting LLM JSON to Excel rows (15 test cases)Debugging
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
License
This project is licensed under the MIT License.
See the LICENSE file for details.
Available Tools
1 toolgenerate_tests_excelA
Generate a comprehensive API test plan with positive, negative, and boundary value analysis test cases. Output is Excel with columns: Sl no, Test Name, Pre-Condition, Steps, Expected Result
| Name | Required | Description | Default |
|---|---|---|---|
| endpoint | Yes | API endpoint to test (e.g., https://api.example.com/v1/users) | |
| method | Yes | HTTP method (GET, POST, etc.) | |
| payload | No | Sample payload for the request (if applicable) | |
| extraContext | No | Any additional instructions/context for the test plan |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral transparency. It fails to disclose whether authentication is needed, if the endpoint must be live, potential rate limits, or how the payload is used. The word 'comprehensive' is vague, and there is no mention of what happens with large outputs or errors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first covers purpose and test types, second describes output format. No superfluous content. Every sentence adds value. Ideal conciseness for a relatively straightforward tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the moderate complexity (generating test plans) and lack of output schema, the description should explain the output more (e.g., is it a file download?) and mention potential time or size constraints. It partially covers the output with column names but omits behavioral context. Adequate but with gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100% with clear descriptions for all four parameters, so baseline is 3. The tool description does not add any parameter-specific detail beyond what the schema already provides, so it neither improves nor detracts from the schema's clarity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it generates a comprehensive API test plan with positive, negative, and boundary value analysis, and specifies the Excel output columns. It uses a specific verb ('Generate') and resource ('API test plan'), making the purpose unambiguous, especially since there are no sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about what the tool does and its output, but does not explicitly state when to use it or when not to. Since there are no sibling tools, the lack of exclusion criteria is less critical, but some guidance on prerequisites (e.g., valid endpoint) would improve it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
Only one tool exists, so there is no risk of confusion with other tools.
The single tool name follows a clear verb_noun pattern (generate_tests_excel), which is consistent.
A single tool for a test case generator seems too few; typically one would expect multiple tools for different operations (e.g., generating, configuring, listing templates) or varying inputs.
The tool covers only generating a test plan in Excel, lacking other common operations such as generating for specific APIs, customizing output, or handling different input formats.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
AI-callable tools for API mocking, testing, monitoring, security, and automation.
End-to-end API testing β generate and run tests from OpenAPI, curl, Postman, or real user traffic.
API governance for AI agents. Detects breaking changes, scores blast radius, blocks unsafe calls.
Turn any task into the right API calls: discover, evaluate, and integrate public APIs.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables LLM clients to generate standardized test cases, perform quality control with lint scoring, convert to Xray/Jira format, and compose test suites (Smoke/Regression/E2E) with coverage analysis.92MIT
- AlicenseAqualityFmaintenanceMCP server for API test case generation from Swagger/OpenAPI specs. Parses Swagger 2.0 and OpenAPI 3.x, generates test cases across 8 categories (positive, negative, boundary, auth, security, idempotency, pagination, business logic), and exports to Postman, TestRail, Allure, k6, pytest, Gherkin, and CSV. Supports internal corporate APIs with auth headers. Auto-saves export files to your working di10142MIT
- FlicenseAqualityDmaintenanceGenerates structured, comprehensive test cases from user stories, API specs, or raw text, with automatic Excel export and Playwright automation code generation.61
- AlicenseCqualityBmaintenanceAutomates generation of QA artifacts such as API tests, E2E tests, and documentation exports. It supports REST Assured, Cypress, and Excel/Word document generation.517MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mallikarjun-Roddannavar/ai-testcase-generator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server