A
licenseA
qualityC
maintenanceAn MCP server that connects AI agents to TestOps, enabling test case management, launches, defects, and analytics through natural language.
48
63 npm
MIT
Lucius
by ivanostanin
Related Servers
Alternatives to Lucius
No user-submitted related servers found.
Related Servers
- 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.405 npmMIT
- AlicenseCqualityBmaintenanceProduction-ready MCP server for Allure TestOps, enabling test case, launch, test result, and test plan management via natural language.100405 npm2MIT
- AlicenseAqualityAmaintenanceMCP server for Allure TestOps — lets an LLM agent (Claude Code, Cursor, Windsurf, etc.) inspect test quality without leaving the chat.11139 PyPI3MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- FlicenseBqualityBmaintenanceMCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.10-
TDQS
B3.4/5.0
Scored across 70 tools
Disambiguation4/5
Most tools follow a clear resource-plus-action pattern, so boundaries between test cases, launches, shared steps, layers, plans, and defects are generally distinct. A few pairs like get_test_case_details vs get_test_result or list_test_layers vs list_test_layer_schemas could require careful reading, but the descriptions provide enough context to avoid serious ambiguity.
Naming Consistency5/5
Tool names are overwhelmingly consistent snake_case verb_noun constructions, such as create_test_case, update_test_plan, list_defects, and delete_shared_step. Even less common actions like rerun_test_results_manually or manage_test_plan_content still follow the same predictable pattern.
Tool Count1/5
With 70 tools, this server is far beyond the range of a well-scoped MCP surface and crosses the extreme-count threshold. Even though Allure TestOps is a broad platform, exposing this many tools in one server creates significant selection overhead and would be better split into focused sub-servers.
Completeness4/5
The tool set is remarkably comprehensive, covering CRUD and lifecycle workflows for test cases, launches, shared steps, layers, schemas, suites, test plans, defects, and defect matchers, along with search, attachments, and manual execution. Minor gaps exist, such as no dedicated test-case attachment upload, no shared-step detail read, and integration management being list-only, but agents can work around these.
Maintenance
ActivityActive
ResponsivenessNo issues