Skip to main content
Glama
mshegolev

allure-testops-mcp

by mshegolev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to allure-testops-mcp

No user-submitted related servers found.

    Related Servers

    • Lucius

      ivanostanin
      A
      license
      B
      quality
      A
      maintenance
      An MCP server for Allure TestOps that enables AI agents to manage test cases, defects, test plans, and other test management entities with clear, easy-to-use tools and helpful error guidance.
      70
      532 PyPI
      7
      Apache 2.0

    • AI Test Automation MCP Server

      abhirise1981
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes AI agents as MCP tools to fetch Jira stories, generate BRDs and Playwright test scripts, run tests, and auto-heal broken locators. Integrates with Claude Desktop and Cursor IDE for enterprise-grade test automation.
      -

    • TestRail MCP Server

      uarlouski
      A
      license
      B
      quality
      A
      maintenance
      AI-native Model Context Protocol (MCP) server for TestRail. Lets Claude, Cursor, Windsurf, and other AI assistants browse projects, create and update test cases, kick off test runs, and record results through natural-language conversation — with strongly-typed tool schemas and per-project custom field validation that helps LLMs generate valid TestRail requests on the first try.
      26
      1,108 npm
      39
      Apache 2.0

    • QA Copilot AI

      Sham-coder16
      F
      license
      B
      quality
      B
      maintenance
      MCP 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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation (projects, statistics, test cases, launches, results, failures, custom fields, layers, statuses) with clear boundaries and explicit 'Don't use when' guidance to prevent misselection.

    Naming Consistency5/5

    All tools follow a consistent 'allure_verb_noun' pattern (e.g., allure_list_projects, allure_get_test_case), making the naming predictable and easy to navigate.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a test management server, covering essential query and list operations without being overwhelming.

    Completeness3/5

    The tools are heavily read-focused, missing create/update/delete operations for test cases and other entities, which are fundamental to full lifecycle management. The descriptions reference 'allure_create_test_case' but it is not included.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources