M
mshegolev/allure-testops-mcp
An MCP server for Allure TestOps.
★ 3·updated 2026-10-29
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 3 ★ · mshegolev/allure-testops-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mshegolev/allure-testops-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# allure-testops-mcp
Excerpted from the repository README (abridged)
An MCP server for Allure TestOps. It lets an
LLM agent (Claude Code, Cursor, OpenCode, …) explore and manage projects, launches, test cases, test
results and reference data through the Allure REST API.
Stack: Python 3.10+, FastMCP, stdio transport.
Compatibility: any Allure TestOps instance — SaaS qameta.io or self-hosted / on-prem (API at /api/rs).
Instance-wide — all projects at once: one connection serves every project on the instance. The server isn't pinned to a single project — discover them with allure_list_projects, then pass any project_id. No reconfiguration to switch or compare projects.
Corporate-friendly: API-token auth, optional SSL-verify toggle, deliberate proxy bypass.
Safe by default: 13 read-only tools; the 7 write tools are off unless you opt in.
## Quick start
bash
claude mcp add allure -s user \
--env ALLURE_URL=https://allure.example.com \
--env ALLURE_TOKEN=your-api-token \
-- uvx --from allure-testops-mcp allure-testops-mcp
Then ask your agent: "List all Allure projects" or "Show failed tests in the last launch for project 175".
Get an API token in Allure TestOps under Profile → API tokens. See Configuration for
other clients and Environment variables for all options.
## Tools at a glance
20 tools — 13 read-only (always on) and 7 write tools (opt-in via ALLURE_ENABLE_WRITE=true). Every tool
carries MCP annotations and returns both a typed structuredContent payload and a markdown summary.
| Tool | Kind | Purpose |
| allure_list_projects | read | All projects (id, name, abbreviation) |
| allure_get_project_statistics | read | TC count, automation rate, last-launch summary |
| allure_list_launches | read | Recent launches with pass/fail stats |
| allure_get_test_results | read | Test results in a launch (filter by status) |
| allure_search_failed_tests | read | FAILED/BROKEN tests in the last or a given launch |
| allure_list_test_cases | read | Test cases (automated/manual + owner filters) |
| allure_get_test_case | read | One test case's full detail + scenario steps |
| allure_get_test_case_custom_fields | read | A test case's custom-field values |
| allure_list_statuses | read | A project's statuses (id, name, color) |
| allure_list_layers | read | A project's test layers (id, name) |
| allure_list_custom_fields | read | A project's custom-field schema |
| allure_list_categories | read | Defect categories (named/coloured buckets) |
| allure_list_category_matchers | read | Regex automation rules (message/trace → category) |
| allure_create_test_case | write ⚑ | Create a test case |
| allure_update_test_case | write ⚑ | Partial update of a test case |
| allure_delete_test_case | write ⚑ | Permanent delete (destructive — needs confirm=true) |
| allure_create_category | write ⚑ | Create a defect category |
| allure_delete_category | write ⚑ | Permanent delete (destructive — needs confirm=true) |
| allure_create_category_matcher | write ⚑ | Create + attach a regex automation rule |
| allure_delete_category_matcher | write ⚑ | Permanent delete (destructive — needs confirm=true) |
⚑ Registered only when ALLURE_ENABLE_WRITE=true. Without the flag they are never imported, so the agent
LLM agent (Claude Code, Cursor, OpenCode, …) explore and manage projects, launches, test cases, test
results and reference data through the Allure REST API.
Stack: Python 3.10+, FastMCP, stdio transport.
Compatibility: any Allure TestOps instance — SaaS qameta.io or self-hosted / on-prem (API at /api/rs).
Instance-wide — all projects at once: one connection serves every project on the instance. The server isn't pinned to a single project — discover them with allure_list_projects, then pass any project_id. No reconfiguration to switch or compare projects.
Corporate-friendly: API-token auth, optional SSL-verify toggle, deliberate proxy bypass.
Safe by default: 13 read-only tools; the 7 write tools are off unless you opt in.
## Quick start
bash
claude mcp add allure -s user \
--env ALLURE_URL=https://allure.example.com \
--env ALLURE_TOKEN=your-api-token \
-- uvx --from allure-testops-mcp allure-testops-mcp
Then ask your agent: "List all Allure projects" or "Show failed tests in the last launch for project 175".
Get an API token in Allure TestOps under Profile → API tokens. See Configuration for
other clients and Environment variables for all options.
## Tools at a glance
20 tools — 13 read-only (always on) and 7 write tools (opt-in via ALLURE_ENABLE_WRITE=true). Every tool
carries MCP annotations and returns both a typed structuredContent payload and a markdown summary.
| Tool | Kind | Purpose |
| allure_list_projects | read | All projects (id, name, abbreviation) |
| allure_get_project_statistics | read | TC count, automation rate, last-launch summary |
| allure_list_launches | read | Recent launches with pass/fail stats |
| allure_get_test_results | read | Test results in a launch (filter by status) |
| allure_search_failed_tests | read | FAILED/BROKEN tests in the last or a given launch |
| allure_list_test_cases | read | Test cases (automated/manual + owner filters) |
| allure_get_test_case | read | One test case's full detail + scenario steps |
| allure_get_test_case_custom_fields | read | A test case's custom-field values |
| allure_list_statuses | read | A project's statuses (id, name, color) |
| allure_list_layers | read | A project's test layers (id, name) |
| allure_list_custom_fields | read | A project's custom-field schema |
| allure_list_categories | read | Defect categories (named/coloured buckets) |
| allure_list_category_matchers | read | Regex automation rules (message/trace → category) |
| allure_create_test_case | write ⚑ | Create a test case |
| allure_update_test_case | write ⚑ | Partial update of a test case |
| allure_delete_test_case | write ⚑ | Permanent delete (destructive — needs confirm=true) |
| allure_create_category | write ⚑ | Create a defect category |
| allure_delete_category | write ⚑ | Permanent delete (destructive — needs confirm=true) |
| allure_create_category_matcher | write ⚑ | Create + attach a regex automation rule |
| allure_delete_category_matcher | write ⚑ | Permanent delete (destructive — needs confirm=true) |
⚑ Registered only when ALLURE_ENABLE_WRITE=true. Without the flag they are never imported, so the agent
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mshegolev-allure-testops-mcp/)
- Source
- awesome · https://github.com/mshegolev/allure-testops-mcp
- Browse by field
- MCP servers
- Traction
- 3 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.