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를 통해 프로젝트, 실행(launch), 테스트 케이스 및 테스트 결과를 조회할 수 있도록 합니다.

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 Context를 통한 진행 상황 보고 — 여러 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에서:

  • "모든 Allure 프로젝트 나열"

  • "프로젝트 63의 최근 실행 10개 표시"

  • "프로젝트 175의 마지막 실행에서 실패한 테스트"

  • "프로젝트 842의 자동화율"

  • "실행 12345에서 상태가 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).

  • 더 작은 페이지 크기로 페이지네이션 수행.

두 가지 도구는 내부적으로 여러 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