Lucius MCP

io.github.ivanostanin由 GitHub 帳號 ivanostanin 發布v0.17.0更新於 Nov 11, 2026

MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.

已驗證STDIO僅桌面開發者工具資料與分析

概覽

AI 產生的概覽

讓助理管理 Allure TestOps 中測試案例、啟動(launch)、測試計畫、缺陷與專案中繼資料的 MCP 伺服器。

可以做什麼
  • 建立、更新、刪除與檢視測試案例、自訂欄位與測試分層
  • 搜尋並列出測試案例、測試套件、整合與專案中繼資料
  • 管理共用步驟與測試套件,包含連結與指派
  • 建立與管理啟動、上傳測試結果、附加檔案、重跑及手動測試工作階段
  • 管理測試計畫、缺陷與缺陷比對規則,並依案例產生特定框架的測試程式碼
適用情境
適合讓 AI 代理在既有的 Allure TestOps 專案中工作:草擬或整理測試文件、組織測試套件、處理缺陷,或檢視啟動結果,而不必手寫 API 呼叫。
執行需求
透過 uvx(Python 3.11-3.14)以 stdio 在本機執行,或使用 Claude Desktop 的 MCPB 套件。需要 ALLURE_ENDPOINT(Allure TestOps 基礎網址)、ALLURE_PROJECT_ID 以及密鑰 ALLURE_API_TOKEN;也可用 lucius auth 命令列儲存憑證。需要能連線至 Allure 執行個體的網路。
安裝前請注意
API 權杖可存取 Allure 專案,透過環境變數傳入或存於本機驗證檔。許多工具會建立、更新、刪除資料、上傳結果並執行測試計畫,會改動真實專案資料。使用遙測預設開啟,會將中繼資料傳送至專案擁有者的端點,除非設定 TELEMETRY_ENABLED=false。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Lucius MCP,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[PyPI Version] [PyPI Python Version] [PyPI Downloads] [GitHub License]

Allure TestOps MCP Server

Lucius is a specialized Model Context Protocol (MCP) server for Allure TestOps, built with FastMCP and Starlette.

🎯 Motivation

Allure TestOps is a powerful tool with a huge API. When you're using an AI agent to manage your tests, it can easily get lost in the details or fail because of a small technical mistake.

Lucius makes this easier by giving your AI tools that are simple to use and hard to break:

  • Clear Tools: Every tool is designed for a specific task, like "finding a test case" or "updating a launch".
  • Helpful Errors: If an AI makes a mistake, Lucius doesn't just return a code—it provides an "Agent Hint" that explains exactly what went wrong and how to fix it.
  • Solid Foundation: We follow a clean "Thin Tool" structure, meaning the logic is consistent and easy for both humans and AI to follow.

🛠️ Supported Tools

See the full reference in Tool Reference.

Tool CategoryDescriptionAll Tools
Test Case MgmtFull lifecycle for test documentation.create_test_case, update_test_case, delete_test_case, delete_archived_test_cases, get_test_case_details, get_test_case_custom_fields
Automation GenerationGenerate framework-specific code from existing test cases.generate_test_code
Search & DiscoveryAdvanced search and project metadata discovery.list_test_cases, search_test_cases, get_custom_fields, list_integrations, get_project
Shared StepsCreate and manage reusable step sequences.create_shared_step, list_shared_steps, update_shared_step, delete_shared_step, delete_archived_shared_steps, link_shared_step, unlink_shared_step
Test LayersManage test taxonomy and auto-mapping schemas.list_test_layers, create_test_layer, update_test_layer, delete_test_layer, list_test_layer_schemas, create_test_layer_schema, update_test_layer_schema, delete_test_layer_schema
Test HierarchyOrganize suites and assign tests in tree paths.create_test_suite, list_test_suites, assign_test_cases_to_suite, delete_test_suite
Custom FieldsProject-level management of custom field values.list_custom_field_values, create_custom_field_value, update_custom_field_value, delete_custom_field_value, delete_unused_custom_fields
Launch ManagementManage launches, result uploads, manual execution, reruns, and attachments.create_launch, list_launches, get_launch, list_launch_test_results, upload_test_results, attach_file_to_launch, rerun_test_results_manually, start_manual_test_session, submit_manual_test_results, add_test_result_attachment
Test Result ManagementInspect one exact TestOps result and prepare verified evidence downloads.get_test_result, prepare_attachment_download
Test PlansManage test plans and their content.create_test_plan, update_test_plan, delete_test_plan, list_test_plans, manage_test_plan_content, run_test_plan
Defect MgmtTrack defects, linkage, and automation rules.create_defect, get_defect, update_defect, delete_defect, list_defects, link_defect_to_test_case, unlink_issue_from_test_case, list_defect_test_cases, create_defect_matcher, list_defect_matchers, update_defect_matcher, delete_defect_matcher

🚀 Quick Start

  1. Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh
  2. Setup Credentials: Create a .env file with the variables below, or save CLI auth with lucius auth.
  3. Run Server: uv run start

Basic .env for Quick Start

VariableDescriptionExample
ALLURE_ENDPOINTAllure TestOps base URLhttps://example.testops.cloud
ALLURE_PROJECT_IDDefault Allure project ID (optional for get_project; required by project-scoped tools)123
ALLURE_API_TOKENAllure API token<your_api_token>
MCP_MODEMCP transport mode for Lucius runtimestdio

🔌 Claude Desktop Integration

The easiest way to use Lucius in Claude Desktop is via the .mcpb bundle:

  1. Download the latest lucius-mcp.mcpb from Releases.
  2. Open with Claude Desktop.
  3. Configure your Allure credentials in the UI.

💻 Claude Code Integration

To add Lucius to Claude Code, use the following command from within your project directory:

bash
claude mcp add --transport stdio --scope project \  --env ALLURE_ENDPOINT=https://example.testops.cloud \  --env ALLURE_PROJECT_ID=123 \  --env ALLURE_API_TOKEN=<your_api_token> \  --env MCP_MODE=stdio \  testops-mcp -- uvx --from lucius-mcp --refresh start

Project-scoped text config example (.mcp.json):

json
{  "mcpServers": {    "testops-mcp": {      "type": "stdio",      "command": "uvx",      "args": [        "--from",        "lucius-mcp",        "--refresh",        "start"      ],      "env": {        "ALLURE_ENDPOINT": "https://example.testops.cloud",        "ALLURE_PROJECT_ID": "123",        "ALLURE_API_TOKEN": "<your_api_token>",        "MCP_MODE": "stdio"      }    }  }}

🧠 Codex Integration

To add Lucius to Codex (CLI or IDE extension), use:

bash
codex mcp add testops-mcp \  --env ALLURE_ENDPOINT=https://example.testops.cloud \  --env ALLURE_PROJECT_ID=123 \  --env ALLURE_API_TOKEN=<your_api_token> \  --env MCP_MODE=stdio \  -- uvx --from lucius-mcp --refresh start

Text config example (~/.codex/config.toml or project .codex/config.toml):

toml
[mcp_servers.testops-mcp]command = "uvx"args = ["--from", "lucius-mcp", "--refresh", "start"]
[mcp_servers.testops-mcp.env]ALLURE_ENDPOINT = "https://example.testops.cloud"ALLURE_PROJECT_ID = "123"ALLURE_API_TOKEN = "<your_api_token>"MCP_MODE = "stdio"

For detailed setup, including Claude Desktop (MCPB) integration, see Setup Guide.

🐍 Supported Python versions

Lucius supports Python 3.11 through 3.14 for runtime use. The generated MCPB manifests and the representative Nuitka CLI compiler matrix validate the same range. Python 3.15 support is experimental: installation may require source builds, and platform compatibility is still being verified. See the development guide for current limitations. Python 3.10 remains unsupported because the locked filelock security update requires Python 3.11 or newer.

💻 Command-Line Interface (CLI)

Lucius also provides a universal CLI entry point for direct tool execution from the command line:

bash
# List available actions for an entityuv run lucius test_case
# Execute an actionuv run lucius test_case get --args '{"test_case_id": 1234}'
# Show help for a specific entity/actionuv run lucius test_case get --help
# Save reusable CLI authuv run lucius auth --url https://example.testops.cloud --token <your_api_token> --project 123uv run lucius auth statusuv run lucius auth clear

CLI Features:

  • 🎯 Type-safe entity/action invocation with validation
  • 🔐 Optional persistent CLI auth with native per-user config storage
  • 📊 Multiple output formats (JSON, table, csv, plain)
  • 🔍 Per-action help with parameters and examples
  • 🛡️ Clean error messages with guidance
  • 📦 Standalone binaries for Linux, macOS, and Windows

CLI auth precedence is:

  1. Explicit tool args such as api_token or project_id
  2. Environment variables
  3. Saved CLI auth config from uv run lucius auth
  4. Defaults

Saved CLI auth uses native config locations:

  • Linux/Unix: $XDG_CONFIG_HOME/lucius/auth.json or ~/.config/lucius/auth.json
  • macOS: ~/Library/Application Support/lucius/auth.json unless XDG overrides are explicitly set
  • Windows: %LOCALAPPDATA%\lucius\auth.json

For full CLI documentation and installation instructions, see CLI Guide.

📡 Telemetry

Lucius collects privacy-preserving usage telemetry to improve tool quality. Telemetry is enabled by default and sends metadata to https://stats.ostanin.me, an endpoint operated by the project owner (no third party has access to this endpoint).

If this is acceptable in your environment, staying opted in helps improve Lucius over time. If you want to opt out, set TELEMETRY_ENABLED=false in your environment.

No API tokens, test content, or tool arguments are sent.

See Telemetry & Privacy for the full data dictionary and telemetry behavior details.

📂 Documentation

Full documentation is available in the docs/ folder:

🤝 Contributing

Contributions are welcome! Please see the Contribution Guidelines and the Development Guide for more details.

來源:README.md,提交 a649efa

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

12
  1. v0.17.0最新Nov 11, 2026
  2. v0.16.9Nov 5, 2026
  3. v0.16.8Nov 3, 2026
  4. v0.16.6Oct 21, 2026
  5. v0.16.5Oct 12, 2026
  6. v0.16.4Oct 6, 2026
  7. v0.16.3Oct 1, 2026
  8. v0.16.2Sep 29, 2026
  9. v0.16.1Sep 23, 2026
  10. v0.15.7Sep 21, 2026
  11. v0.15.6Sep 17, 2026
  12. v0.15.5Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分