Lucius MCP

Name: Lucius MCP
Author: ivanostanin

作者：ivanostanin版本 0.16.9i★ –i在你的电脑上运行

注册名称io.github.ivanostanin/lucius-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i起步阶段↓ 501/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

claude mcp add lucius --env ALLURE_ENDPOINT=your-value --env ALLURE_PROJECT_ID=your-value --env ALLURE_API_TOKEN=your-value -- uvx lucius-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "lucius": {
      "command": "uvx",
      "args": [
        "lucius-mcp"
      ],
      "env": {
        "ALLURE_ENDPOINT": "your-value",
        "ALLURE_PROJECT_ID": "your-value",
        "ALLURE_API_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "lucius": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "lucius-mcp"
      ],
      "env": {
        "ALLURE_ENDPOINT": "your-value",
        "ALLURE_PROJECT_ID": "your-value",
        "ALLURE_API_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

ALLURE_ENDPOINT 必填 env
Allure TestOps base URL, for example https://example.testops.cloud.
ALLURE_PROJECT_ID 必填 env
Default Allure TestOps project ID.
ALLURE_API_TOKEN 机密必填 env
Allure TestOps API token.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 ivanostanin 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18643 个服务器的 0%
发布到注册中心的时间比此分类中其他 18643 个服务器的 92% 更新
基础检查结果等于或优于此分类中其他 18643 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Lucius MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.16.9）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv), Docker, MCPB。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Cosas Guapas: buscador de regalos

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Cosas Guapas: buscador de regalos

Regalos originales por ocasión, persona y presupuesto, con enlaces a guías completas (España).

作者：cosasguapas.com起步阶段今天更新

在云端运行✓ cosasguapas.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 Category	Description	All Tools
Test Case Mgmt	Full 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 Generation	Generate framework-specific code from existing test cases.	`generate_test_code`
Search & Discovery	Advanced search and project metadata discovery.	`list_test_cases`, `search_test_cases`, `get_custom_fields`, `list_integrations`, `get_project`
Shared Steps	Create 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 Layers	Manage 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 Hierarchy	Organize suites and assign tests in tree paths.	`create_test_suite`, `list_test_suites`, `assign_test_cases_to_suite`, `delete_test_suite`
Custom Fields	Project-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 Management	Manage 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 Management	Inspect one exact TestOps result and prepare verified evidence downloads.	`get_test_result`, `prepare_attachment_download`
Test Plans	Manage 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 Mgmt	Track 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

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

Basic `.env` for Quick Start

Variable	Description	Example
`ALLURE_ENDPOINT`	Allure TestOps base URL	`https://example.testops.cloud`
`ALLURE_PROJECT_ID`	Default Allure project ID (optional for `get_project`; required by project-scoped tools)	`123`
`ALLURE_API_TOKEN`	Allure API token
`MCP_MODE`	MCP transport mode for Lucius runtime	`stdio`

🔌 Claude Desktop Integration

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

Download the latest lucius-mcp.mcpb from Releases.
Open with Claude Desktop.
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:

claude mcp add --transport stdio --scope project \

--env ALLURE_ENDPOINT=https://example.testops.cloud \ --env ALLURE_PROJECT_ID=123 \ --env ALLURE_API_TOKEN= \ --env MCP_MODE=stdio \ testops-mcp -- uvx --from lucius-mcp --refresh start

Project-scoped text config example (.mcp.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": " ", "MCP_MODE": "stdio" } } } }

🧠 Codex Integration

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

codex mcp add testops-mcp \

--env ALLURE_ENDPOINT=https://example.testops.cloud \ --env ALLURE_PROJECT_ID=123 \ --env ALLURE_API_TOKEN= \ --env MCP_MODE=stdio \ -- uvx --from lucius-mcp --refresh start

Text config example (~/.codex/config.toml or project .codex/config.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 = " " 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:

# List available actions for an entity

uv run lucius test_case

Execute an action

uv run lucius test_case get --args '{"test_case_id": 1234}'

Show help for a specific entity/action

uv run lucius test_case get --help

Save reusable CLI auth

uv run lucius auth --url https://example.testops.cloud --token --project 123 uv run lucius auth status uv 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:

Explicit tool args such as api_token or project_id
Environment variables
Saved CLI auth config from uv run lucius auth
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:

Architecture & Design
Tool Reference
Configuration & Setup
Telemetry & Privacy
Attachment download capability links
Development Guide
AI Agent Protocol

🤝 Contributing

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