Skip to main content
Glama
iampopovich

Allure TestOps MCP

by iampopovich

Related Servers

Alternatives to Allure TestOps MCP

No user-submitted related servers found.

    Related Servers

    TDQS

    C2.8/5.0

    Scored across 100 tools

    Disambiguation2/5

    The tool set spans many resource areas with clear individual descriptions, but multiple tools occupy close conceptual territory—get_test_case_scenario vs get_test_case_steps, get_launch_statistic vs get_launch_progress, and several trend/group analytics—making misselection likely without deep domain knowledge. The sheer volume of 100 tools increases the chance an agent picks the wrong one for a task.

    Naming Consistency4/5

    All tools use snake_case and mostly follow the verb_noun pattern (get_, list_, create_, update_, delete_, set_, etc.). Minor inconsistencies like 'get_tc_last_result' vs 'get_test_case_history' and 'bulk_close_defects' vs 'add_test_case_tags_bulk' (prefix vs suffix placement) prevent a perfect score.

    Tool Count1/5

    100 tools for a single MCP server is an extreme number, far exceeding the 50+ threshold for unreasonable scope. Even though Allure TestOps is a feature-rich platform, this volume is unwieldy and would overwhelm agents during tool selection.

    Completeness4/5

    The surface provides broad CRUD and lifecycle coverage for test cases, launches, test results, defects, test plans, dashboards, and shared steps, plus analytics, bulk operations, and env-var tooling. Minor gaps exist (e.g., no delete test result, no step-level editing for shared steps), but they are workaroundable rather than dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive