kiwi-tcms-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., "@kiwi-tcms-mcpCreate a test case for login with valid credentials"
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.
kiwi-tcms-mcp
An MCP (Model Context Protocol) server that exposes Kiwi TCMS as a set of AI-callable tools. It lets an AI assistant (e.g. Kiro, Cursor, Claude Desktop) create and manage test plans, test cases, test runs, and executions directly from a conversation.
Features
The server registers 50+ tools covering the full Kiwi TCMS lifecycle:
Products & Versions
Tool | Description |
| List all products |
| List versions for a product |
Test Plans
Tool | Description |
| List test plans, optionally filtered by product |
| Get full details of a test plan (name, description, product, version, active status) |
| Create a new test plan |
| Update plan name, description, or deactivate |
| Add an existing test case to a plan |
| Unlink a test case from a plan |
| Get plan hierarchy (parent/child plans) |
| Reorder test cases within a plan by setting sort keys |
| Upload a file attachment to a test plan |
| List attachments on a test plan |
| Add tags to a test plan |
| Remove tags from a test plan |
Test Cases
Tool | Description |
| List test cases in a test plan |
| Fetch ALL data: summary, steps, tags, attachments (with URLs), priority, status, notes, category, author |
| Create a test case with steps, navigation, role, priority, and format (table/list) |
| Non-destructive reformat & push — updates only specified fields, builds HTML table from structured steps |
| Disable a test case that is no longer relevant |
| List all disabled test cases, optionally filtered by product or plan |
| Search by product, plan, status, priority, tag, or summary keyword |
Tags & Components
Tool | Description |
| Add one or more tags to a test case |
| Remove tags from a test case |
| List all tags on a test case |
| Link a component (module/feature) to a test case |
| Unlink a component from a test case |
Test Case Metadata
Tool | Description |
| Add a comment to a test case |
| List comments on a test case |
| Upload a file attachment to a test case |
| List all attachments on a test case |
| Get audit trail — who changed what and when |
| List custom key-value properties |
| Add a custom property |
| Remove a custom property |
Test Runs
Tool | Description |
| List builds for a product version |
| Create a new build for a version |
| Create a test run (campaign) from a test plan |
| Update a test run: name, notes, or stop date |
| List test runs, optionally filtered by plan |
| Add a test case to a test run |
| Remove a test case from a test run |
| Get test cases included in a test run |
| Add tags to a test run |
| Remove tags from a test run |
| Add notification subscribers |
| List notification subscribers |
| Remove a subscriber |
| Upload a file attachment to a test run |
| List attachments on a test run |
Test Executions
Tool | Description |
| List executions in a run with their status |
| Mark execution as PASSED, FAILED, BLOCKED, WAIVED, ERROR, or IDLE |
| Add a comment to a test execution |
| Read comments on a test execution |
| Add a URL link (bug tracker, CI build, etc.) |
| List URL links on a test execution |
| Remove a URL link |
| Upload a file attachment (evidence) |
| List attachments on a test execution |
| Add tags to a test execution |
| Remove tags from a test execution |
| Get audit trail for a test execution |
Reporting & Analytics
Tool | Description |
| Generate a test run report with pass/fail statistics (summary, detailed, or JSON) |
| Get plan metrics: total cases, status breakdown, priority distribution, coverage |
Users & Bugs
Tool | Description |
| List/search users in Kiwi TCMS |
| Get bug details from the configured bug tracker |
| Report a bug from a test execution |
Related MCP server: TestOps MCP Server
Test Case Formatting
Test cases support two output formats via the format parameter:
table(default) — HTML table with Step No. | Action | Expected Behavior columns, plus Navigation and Role headerslist— Bold labels style (Step 1: / Action: / Expected Result:)
Additional fields:
navigation— Path to reach the screen (e.g. "Login → Menu → Daily Roaster")role— User role for the test (e.g. "Sales Manager (SM)")priority— P1 (highest) to P4 (lowest), defaults to P2notes— Stored in Kiwi's dedicated notes field (not embedded in the text body)
Requirements
Node.js 18+
A running Kiwi TCMS instance (self-hosted or cloud)
Installation
npm installThis installs @modelcontextprotocol/sdk, node-fetch, zod, and dotenv.
Configuration
The server reads credentials from environment variables. You can either set system/user environment variables on your machine, or create a .env file in the project root (automatically loaded via dotenv). For MCP configs, reference them using ${VAR} syntax. No credentials are hardcoded or committed.
Variable | Required | Description |
| ✅ | Base URL of your Kiwi TCMS instance |
| ✅ | Login username |
| ✅ | Login password |
Setup (per user)
Option A — Use a .env file (simplest for local development):
Create a .env file in the project root:
KIWI_URL=https://your-kiwi-instance
KIWI_USERNAME=your_user
KIWI_PASSWORD=your_passMake sure
.envis in.gitignoreto avoid committing credentials.
Option B — Set system environment variables:
Windows (run in PowerShell as admin, or via System Settings → Environment Variables):
[System.Environment]::SetEnvironmentVariable('KIWI_URL', 'https://your-kiwi-instance', 'User')
[System.Environment]::SetEnvironmentVariable('KIWI_USERNAME', 'your_user', 'User')
[System.Environment]::SetEnvironmentVariable('KIWI_PASSWORD', 'your_pass', 'User')macOS/Linux (add to ~/.bashrc, ~/.zshrc, or equivalent):
export KIWI_URL="https://your-kiwi-instance"
export KIWI_USERNAME="your_user"
export KIWI_PASSWORD="your_pass"Then, reference them in your MCP config (.kiro/settings/mcp.json or ~/.kiro/settings/mcp.json):
{
"mcpServers": {
"kiwi-tcms": {
"command": "node",
"args": ["/absolute/path/to/kiwi-tcms-mcp/src/index.js"],
"env": {
"KIWI_URL": "${KIWI_URL}",
"KIWI_USERNAME": "${KIWI_USERNAME}",
"KIWI_PASSWORD": "${KIWI_PASSWORD}"
}
}
}
}Kiro expands ${VAR} at runtime from your system environment. Nothing sensitive is stored in the repo.
Self-signed TLS certificates are accepted automatically, which is useful for self-hosted instances.
Usage
Running the server directly
KIWI_URL=https://your-kiwi-instance \
KIWI_USERNAME=your_user \
KIWI_PASSWORD=your_pass \
npm startThe server communicates over stdio using the MCP protocol.
Kiro / Cursor / Claude Desktop integration
Add the server to your MCP configuration file (e.g. .kiro/settings/mcp.json, ~/.cursor/mcp.json, or claude_desktop_config.json):
{
"mcpServers": {
"kiwi-tcms": {
"command": "node",
"args": ["/absolute/path/to/kiwi-tcms-mcp/src/index.js"],
"env": {
"KIWI_URL": "${KIWI_URL}",
"KIWI_USERNAME": "${KIWI_USERNAME}",
"KIWI_PASSWORD": "${KIWI_PASSWORD}"
}
}
}
}Once configured, you can ask the AI to create test plans and cases in natural language:
"Generate test cases for ADS-1697 and push them to Kiwi TCMS under the AWA product."
AI Skill (Kiro / Cursor)
A ready-to-use AI skill is included in skills/kiwi-tcms-test-generation/SKILL.md. It works with Kiro (as a bundled skill) and Cursor (via the agent skills mechanism). Once installed, you can generate and push a full test plan from a feature branch with a single prompt.
What the skill does
Reads your PRD, design docs, and implementation plans
Extracts test scenarios (happy path, edge cases, access control, regressions)
Pushes test cases to Kiwi TCMS via the MCP tools
Supports both new generation and updating after a doc change
Installation
For Kiro: The skill is bundled with this repo and automatically available when the MCP server is configured in your workspace.
For Cursor:
Copy the skill to the Cursor global skills folder:
mkdir -p ~/.agents/skills/kiwi-tcms-test-generation
cp skills/kiwi-tcms-test-generation/SKILL.md \
~/.agents/skills/kiwi-tcms-test-generation/SKILL.mdEdit the copied file and replace all placeholders (search for
<REPLACE_):
Placeholder | Description | Example |
| Base URL of your Kiwi TCMS instance |
|
| Absolute path to |
|
Make sure the MCP server is registered in your IDE's MCP config (see integration section above).
Restart your IDE for the skill and the MCP server to be picked up.
Usage
Once installed, trigger it with a natural language prompt:
"Generate tests for ADS-1234 and push them to Kiwi TCMS."
"Update Kiwi tests after the PRD change on ADS-1234."
Project structure
src/
index.js # MCP server — tool definitions and JSON-RPC helpers
skills/
kiwi-tcms-test-generation/
SKILL.md # AI skill template (copy to ~/.agents/skills/)
package.jsonHow it works
On startup, the server authenticates with
Auth.loginand stores the session cookie.A
rpcSafewrapper handles session expiry — if a 403 is returned, it re-authenticates once and retries.All tool handlers are wrapped in an error handler that catches exceptions and returns them as MCP error content (no crashes).
Tag and multi-item operations run in parallel using
Promise.allfor better performance.Tools communicate with the Kiwi TCMS JSON-RPC API (
POST /json-rpc/).Test case content (steps, preconditions) is stored in the
textfield as formatted HTML (table or list format).The
kiwi_reformat_test_casetool is non-destructive — it only updates fields you explicitly provide and preserves everything else.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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/danish54/kiwi-tcms-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server