Skip to main content
Glama
allure-testops-mcp

allure-testops-mcp

allure-testops-mcp

PyPI Python License: MIT Tests

Allure TestOps用MCPサーバー。LLMエージェント(Claude Code、Cursor、OpenCodeなど)がAllure REST APIを通じてプロジェクト、ローンチ、テストケース、テスト結果をクエリできるようにします。

Python、FastMCP、stdioトランスポートを使用。

あらゆるAllure TestOpsインスタンス(SaaSの qameta.io またはセルフホスト/オンプレミス)で動作します。企業ネットワークを考慮して設計されており、プロキシバイパスの設定、SSL検証の切り替え(オプション)、APIトークン認証に対応しています。

設計のハイライト

  • ツールアノテーション — すべてのツールに readOnlyHint: True / openWorldHint: True がマークされています。6つのツールはすべて読み取り専用であり、MCPクライアントが確認を求めることはありません。

  • すべてのツールで構造化された出力 — 各ツールは TypedDict 戻り値の型を宣言しているため、FastMCPが自動的に outputSchema を生成し、すべての結果が structuredContent(型付きペイロード)と事前レンダリングされたマークダウンテキストブロックの両方を保持します。

  • 構造化されたエラー — 認証、404、403、429、5xx、環境変数不足のエラーは、アクション可能なメッセージ(例: "認証失敗 — ALLURE_TOKENにAPIスコープがあるか確認してください")に変換されます。

  • Pydanticによる入力バリデーション — すべての引数には、JSON Schemaとして自動公開される型付き制約(範囲、長さ、リテラル)があります。

  • ページネーション — リストツールは、page、total、has_more、next_page を含む pagination ブロックを返します。

  • MCPコンテキストによる進捗報告 — 複数のAPI呼び出しを行うツール(allure_get_project_statistics、allure_search_failed_tests)および allure_list_test_cases は、ctx.report_progress + ctx.info イベントを発行するため、互換性のあるクライアントはプログレスバーやステップラベルを表示できます。

Related MCP server: Allure TestOps MCP

機能

日常的なAllure TestOpsワークフローをカバーする6つのツール:

探索

  • allure_list_projects — ID、名前、略称を含むすべてのプロジェクト

  • allure_get_project_statistics — TC数、自動化率、前回のローンチ概要

ローンチと結果

  • allure_list_launches — 合格/不合格統計を含む最近のローンチ

  • allure_get_test_results — ローンチ内のテスト結果(ステータスでフィルタリング可能)

  • allure_search_failed_tests — 前回または指定したローンチにおけるFAILED/BROKENテスト

テストケース

  • allure_list_test_cases — 自動/手動フィルタ付きのテストケース(各結果はレイヤー、例: UNIT / API / E2E も保持)

インストール

Python 3.10以上が必要です。

# via uvx (recommended)
uvx --from allure-testops-mcp allure-testops-mcp

# or via pipx
pipx install allure-testops-mcp

設定

短いバージョン — claude mcp add:

claude mcp add allure -s project \
  --env ALLURE_URL=https://allure.example.com \
  --env ALLURE_TOKEN=your-api-token \
  --env ALLURE_SSL_VERIFY=true \
  -- uvx --from allure-testops-mcp allure-testops-mcp

または ~/.claude.json / プロジェクトの .mcp.json に記述:

{
  "mcpServers": {
    "allure": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "allure-testops-mcp", "allure-testops-mcp"],
      "env": {
        "ALLURE_URL": "https://allure.example.com",
        "ALLURE_TOKEN": "${ALLURE_TOKEN}",
        "ALLURE_SSL_VERIFY": "true"
      }
    }
  }
}

サポートされているすべての環境変数のテンプレートについては、.env.example を参照してください。

確認:

claude mcp list
# allure: uvx --from allure-testops-mcp allure-testops-mcp - ✓ Connected

環境変数

変数

必須

説明

ALLURE_URL

はい

Allure TestOps URL (例: https://allure.example.com)

ALLURE_TOKEN

はい

Allure TestOpsのAPIトークン (プロフィール → APIトークン)

ALLURE_SSL_VERIFY

いいえ

true/false。自己署名企業証明書の場合は false に設定。デフォルト: true。

使用例

Claude Codeでの例:

  • "List all Allure projects"

  • "Show last 10 launches for project 63"

  • "Failed tests in the last launch for project 175"

  • "Automation rate for project 842"

  • "Test results in launch 12345 with status FAILED"

セキュリティに関する考慮事項

  • APIトークンは ALLURE_TOKEN 環境変数から読み取られます — コマンドラインで渡されることはなく、ログに書き込まれることもありません。

  • シークレットはツール応答でエコーバックされません (stat.request_headers のダンプや session.auth の反映はありません)。

  • 自己署名SSL は ALLURE_SSL_VERIFY=false を介したオプトインです — デフォルトは true です。パブリックネットワークで検証を無効にすることはセキュリティリスクです。信頼できる企業内インスタンスでのみ使用してください。

  • プロキシ検出は無効化されています (session.trust_env = False) — MCPは意図的に HTTP_PROXY/HTTPS_PROXY 環境変数を無視するため、セッションが意図しないプロキシ経由でルーティングされることはありません。Allureインスタンスにプロキシ経由でしか到達できない場合は、requests が直接解決できる環境でMCPを実行してください。

  • 書き込み操作は公開されていません — 6つのツールはすべて読み取り専用です。APIトークンに書き込みスコープがある場合でも、このMCPサーバーはAllure TestOps内の何かを作成、変更、削除することはできません。

  • Pydanticによる入力バリデーション — すべてのツール引数は型指定され、制限されています(IDは1以上、ページネーションは200〜500に制限)。

レート制限

Allure TestOpsはインスタンスごとのレート制限を強制します(通常、APIトークンあたり約60リクエスト/分)。HTTP 429が発生した場合、MCPは以下を推奨するアクション可能なエラーを返します:

  • 再試行する前に30〜60秒待機する。

  • size パラメータを減らす(テスト結果のデフォルトは50、プロジェクトは200)。

  • より小さいページサイズでページネーションを行う。

2つのツールは内部で複数のAPI呼び出しを実行します:

  • allure_get_project_statistics — 3回の呼び出し(TC数 + ローンチ + ローンチ統計)。

  • allure_search_failed_tests — 2〜3回の呼び出し(最新ローンチの解決 + FAILED + BROKEN)。

どちらもMCP Context を使用してステップごとの進捗を報告します。allure_list_test_cases も単一の進捗イベントを発行します。互換性のあるクライアントで進捗ストリームを監視してください。

開発

git clone https://github.com/mshegolev/allure-testops-mcp.git
cd allure-testops-mcp
pip install -e '.[dev]'
pytest

サーバーを直接実行する(stdioトランスポート、MCPメッセージのstdinを待機):

ALLURE_URL=... ALLURE_TOKEN=... allure-testops-mcp

ライセンス

MIT © Mikhail Shchegolev

Available Tools

11 tools
allure_get_project_statisticsA
Read-onlyIdempotent

Get summary statistics for an Allure project.

Returns TC count, automation rate, and the last closed launch's pass/fail breakdown. Performs 3-4 API calls — progress is reported via MCP Context (visible as progress updates in compatible clients).

Args: project_id: Allure project ID (see allure_list_projects). ctx: MCP Context injected by FastMCP (used for progress reporting; never supplied by the agent directly).

Returns: dict with keys: - project_id (int) - total_test_cases (int) - automated_test_cases (int) - manual_test_cases (int) - automation_rate_pct (float) - last_launch_id (int | None): latest closed launch - last_launch_name (str | None) - last_launch_passed / last_launch_failed / last_launch_broken (int) - last_launch_total (int) - recent_launches_count (int): launches examined to find the latest closed one

Examples: - "How automated is project 63?" -> project_id=63, read automation_rate_pct - "What was the last passing run for project 175?" -> read last_launch_passed

Don't use when:
- You need per-test detail (use ``allure_get_test_results``).
- You need the full launch history (use ``allure_list_launches``).

Inputs: project_id (required). Returns: project_id, total_test_cases, automated_test_cases, manual_test_cases, +8 more

allure_get_test_caseA
Read-onlyIdempotent

Get one test case's full detail — fields, status/layer, tags, and steps.

Unlike allure_list_test_cases (summaries), this returns the body of a single test case: description, precondition, expected result, and the manual scenario steps (flattened with a depth marker). Use it to read or review the actual content of a test case.

Returns: dict with id, name, project_id, automated, description, precondition, expected_result, status, layer, tags and steps (each: depth, keyword, name, expected_result). steps is empty when include_scenario is false or the case has none.

Inputs: test_case_id (required), include_scenario. Returns: id, name, project_id, automated, +9 more

allure_get_test_case_custom_fieldsA
Read-onlyIdempotent

List the custom-field values set on a test case.

Returns each value flattened to field_id / field_name (the custom field) and value_id / value_name (the chosen value) — e.g. field "Priority" → value "High". These are not included in allure_get_test_case; fetch them here when you need a test case's custom-field assignments.

Inputs: test_case_id (required). Returns: test_case_id, count, custom_fields

allure_get_test_resultsA
Read-onlyIdempotent

Get individual test results inside a launch, optionally filtered by status.

Args: launch_id: Allure launch ID (from allure_list_launches). status: Filter — PASSED / FAILED / BROKEN / SKIPPED. None returns all. page: 0-based page index. size: Items per page (1-200; default 50).

Returns: dict with keys: - launch_id (int) - count (int) - pagination (dict) - results (list): each with id / name / status / duration_ms / error (first 300 chars of statusMessage)

Examples: - "FAILED tests in launch 12345" -> launch_id=12345, status="FAILED" - "All results in launch X, second page" -> launch_id=X, page=1

Don't use when:
- You want only FAILED+BROKEN (``allure_search_failed_tests`` does both in one call).

Inputs: launch_id (required), status, page, size. Returns: launch_id, count, pagination, results

allure_list_custom_fieldsA
Read-onlyIdempotent

List the custom fields defined on a project (its schema).

Returns each field's field_id, name, single_select and required. Use it to discover which custom fields a project has before reading a test case's values with allure_get_test_case_custom_fields. Built-in metadata fields (Epic/Feature/Story/Component/Suite) use negative ids; project-specific custom fields use positive ids.

Inputs: project_id (required). Returns: project_id, count, custom_fields

allure_list_launchesA
Read-onlyIdempotent

List recent launches for a project, newest first.

Each launch carries a pass/fail/broken/skipped breakdown from Allure's statistic field. Pagination info is returned in the pagination block (use next_page to continue).

Args: project_id: Allure project ID. page: 0-based page index. size: Items per page (1-100; 20 is usually enough for triage).

Returns: dict with keys: - project_id (int) - count (int): items in this response - pagination (dict): page / size / total / total_pages / has_more / next_page - launches (list): each with id / name / status / created_date / passed / failed / broken / skipped / total

Examples: - "Last 10 launches for project 63" -> project_id=63, size=10 - "Older launches beyond page 1" -> repeat with page=1

Don't use when:
- You need test results inside a launch (``allure_get_test_results``).
- You need just the latest FAILED/BROKEN tests (``allure_search_failed_tests``).

Inputs: project_id (required), page, size. Returns: project_id, count, pagination, launches

allure_list_layersA
Read-onlyIdempotent

List the test layers defined in a project (id, name).

Use this to discover valid layer names/ids before setting a layer on allure_create_test_case / allure_update_test_case. Built-in layers use negative ids (e.g. API Tests = -3).

Returns: dict with project_id, count and layers (each: id, name).

Inputs: project_id (required). Returns: project_id, count, layers

allure_list_projectsA
Read-onlyIdempotent

List all projects in the Allure TestOps instance.

Use this first to discover which project IDs exist — all other tools take a project_id that you can look up here.

Returns: dict with keys: - count (int): number of projects in this response - projects (list): each item has id, name, abbreviation

Examples: - "Which projects exist in Allure?" -> default call, take the names/ids - "Find project by abbreviation" -> iterate projects and match

Don't use when:
- You already know the project id (skip discovery, go straight to the target tool).

Inputs: page, size. Returns: count, projects

allure_list_statusesA
Read-onlyIdempotent

List the test-case statuses defined in a project (id, name, color).

Use this to discover valid status names/ids before setting a status on allure_create_test_case / allure_update_test_case. Built-in statuses use negative ids (e.g. Draft = -1).

Returns: dict with project_id, count and statuses (each: id, name, color).

Inputs: project_id (required). Returns: project_id, count, statuses

allure_list_test_casesA
Read-onlyIdempotent

List test cases for a project with optional automation and ownership filters.

Each TC carries id, name, automated, status, layer (e.g. UNIT, API, E2E), the createdBy / lastModifiedBy audit usernames, and a flat list of tag names. Caveat: the audit fields and tags are only populated when owner is set, because Allure's plain /testcase endpoint returns a compact projection that omits them — the owner path uses __search which returns the full projection.

Args: project_id: Allure project ID. ctx: MCP Context (auto-injected by FastMCP for progress reporting). automated: True — only automated, False — only manual, None — both. owner: Optional Allure username. When set, the response is narrowed to TCs where createdBy = owner OR lastModifiedBy = owner (case-sensitive, exact match), enforced server-side via Allure's RQL __search endpoint. The username must match [A-Za-z0-9._@-]+ — anything else is rejected at the MCP input layer (Pydantic pattern) to prevent RQL injection.

    **Why "creator/modifier" and not "owner".** Allure TestOps does
    not expose a separate ``owner`` field in RQL on most
    deployments — the closest stable proxy for "TCs I touched" is
    the union of ``createdBy`` and ``lastModifiedBy``.

    **Trade-off when ``owner`` is set.** ``__search`` does not
    accept the ``automated`` query parameter, so an ``automated``
    filter combined with ``owner`` is applied **client-side after
    the page is fetched**. ``pagination`` then reflects the raw
    owner-filtered set, not the further automation-filtered view —
    a fetched page of 50 may shrink. Raise ``size`` (max 200) or
    iterate ``page`` for full coverage.
page: 0-based page index.
size: Items per page (1-200; default 50).

Returns: dict with keys: - project_id (int) - count (int): items in this response (post any client-side automated filter) - pagination (dict): raw Allure paging - test_cases (list): each item carries id / name / automated / status / layer / created_by / last_modified_by / tags

Examples: - "How many manual TCs does project 63 have?" -> project_id=63, automated=False, read pagination.total - "First 200 automated TCs" -> automated=True, size=200 - "My manual TCs in project 63" -> project_id=63, automated=False, owner="jdoe", size=200

Don't use when:
- You need just the automation % (``allure_get_project_statistics``).

Inputs: project_id (required), automated, owner, page, +1 more. Returns: project_id, count, pagination, test_cases

allure_search_failed_testsA
Read-onlyIdempotent

Find FAILED and BROKEN tests in the most recent (or given) launch.

Useful for triage: "what's broken in the latest run" without listing every test. Performs up to 3 API calls; progress reported via MCP Context.

Args: project_id: Allure project ID. launch_id: Specific launch ID. If None, the latest launch is used. limit: Max failures per status (so up to 2 * limit total). ctx: MCP Context (auto-injected).

Returns: dict with keys: - launch_id (int): the resolved launch (latest if not passed in) - failed_count (int) - results (list): id / name / status / duration_ms / error

Examples: - "What's failing in project 63 right now?" -> project_id=63 - "Failures in launch 98765" -> project_id=N, launch_id=98765

Don't use when:
- You need PASSED tests too (use ``allure_get_test_results`` without status filter).

Inputs: project_id (required), launch_id, limit. Returns: launch_id, failed_count, results, reason

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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.
      27
      1,151 npm
      45
      Apache 2.0
    • A
      license
      B
      quality
      B
      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
      408 PyPI
      8
      Apache 2.0