A
licenseA
qualityA
maintenanceEnables interaction with the Tuskr test management API through MCP, supporting account ID and access token authentication for managing test cases, runs, and projects.
3
1
MIT
tuskr-mcp
by Zapkid
Related Servers
Alternatives to tuskr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that integrates Cursor IDE with Xray Test Management for Jira, enabling management of tests, test executions, test plans, and import/export operations.2436 npm2MIT
- AlicenseCqualityFmaintenanceA TypeScript-based MCP server that provides integration with the Qase test management platform, allowing you to manage projects, test cases, runs, results, plans, suites, and shared steps.2612MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Allure TestOps that enables test case management operations like searching, creating, deleting, and updating test cases, scenarios, issues, and custom fields.59 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for TestRail that enables AI assistants to interact with TestRail's test management platform. It can query and manage projects, test cases, runs, results, plans, milestones, and more.MIT
- FlicenseAqualityBmaintenanceMCP server for self-hosted Jira, enabling task management, searching issues, adding comments, transitioning statuses, and logging worklogs directly from Cursor.121-
TDQS
B3/5.0
Scored across 17 tools
Disambiguation5/5
All tools target distinct resources or operations (sections, test cases, suites, runs, projects) with clear boundaries. Even similar tools like set_test_case_automated and set_test_cases_automated_bulk are differentiated by single vs. bulk operation. No two tools are easily confused.
Naming Consistency4/5
Naming mostly follows verb_noun snake_case (create_section, list_projects). However, 'health_check' and 'validate_tuskr_setup' deviate slightly (health_check is noun_verb, validate_tuskr_setup is verb_noun but longer). Overall pattern is consistent enough for an agent to predict tool names.
Tool Count4/5
With 17 tools, the server is slightly above the typical 3-15 range but still appropriate for a test management domain that covers projects, suites, sections, test cases, test runs, and setup validation. Each tool serves a clear purpose without bloat.
Completeness3/5
The tool set covers creation and reading for most resources but lacks update and delete operations everywhere except for a single automated field update on test cases. Missing general test case update, test suite update/delete, test run creation, and any deletion. This leaves notable gaps for full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues