M
mshegolev/allure-testops-mcp
An MCP server for Allure TestOps.
★ 3·更新 2026-10-29
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 3 ★ · mshegolev/allure-testops-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
mshegolev/allure-testops-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# allure-testops-mcp
以下摘录自该仓库的 README(片段)
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
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/mshegolev-allure-testops-mcp/)
- 来源
- awesome · https://github.com/mshegolev/allure-testops-mcp
- 按领域浏览
- MCP 服务
- Traction
- 3 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。