kiwi-tcms-mcp
Related Servers
Alternatives to kiwi-tcms-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Kiwi TCMS as a set of AI-callable tools, enabling assistants to create and manage test plans, test cases, test runs, and executions directly from a conversation.1-
- AlicenseBqualityBmaintenanceEnables MCP clients to interact with Kiwi TCMS test-management data, allowing users to browse and create test cases, build plans and runs, and record execution results through natural-language prompts. It exposes 49 read/write tools over the Kiwi JSON-RPC API.49MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Kiwi TCMS test management system through MCP, supporting read and write operations on test plans, cases, runs, and executions, with API key authentication.1AGPL 3.0
- AlicenseBqualityCmaintenanceMCP server to interact with the QMetry for Jira API, enabling management of test cases, test cycles, test plans, and more through well-defined tools.9348 npmApache 2.0
- AlicenseCqualityCmaintenanceMCP server for TestRail API, providing AI assistants with 107 tools to manage test cases, runs, results, plans, and more. Supports API key, password, and SSO cookie authentication.5415 npm2MIT
- AlicenseBqualityCmaintenanceComprehensive MCP server for Project COR, a project management platform, exposing 61 tools covering the complete COR REST API as MCP tools.61MIT
TDQS
Scored across 68 tools
Each tool clearly targets a specific resource and action (e.g., creating runs, adding cases, listing executions, managing attachments). Even similar-sounding tools like kiwi_list_executions and kiwi_run_get_cases have distinct purposes (filtering vs. retrieving run cases).
Tool names consistently use the kiwi_ prefix and snake_case, but the verb/noun order varies (kiwi_create_run vs. kiwi_run_add_case). This minor inconsistency is readable and does not cause confusion.
68 tools is well beyond the recommended range and may overwhelm agents. The server covers a large domain, but many operations could be consolidated (e.g., generic attachment/property tools already exist).
The surface covers nearly every Kiwi TCMS workflow: full CRUD for cases/plans/runs, execution management, tags, attachments, properties, links, and a generic RPC fallback. No obvious dead ends remain.