# Lucius MCP

Connects AI assistants to Allure TestOps for managing test cases, runs, and defects. Useful for teams automating QA workflows directly in chat.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 7
- Author: ivanostanin
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ivanostanin/lucius-mcp
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/mcp/lucius-mcp

## What it does

Built on top of `FastMCP` and `Starlette`, the server exposes structured tools for the Allure TestOps API. It allows agents to inspect and edit test documentation, manage shared steps, configure test layers, and organize suite hierarchies.

Beyond static cases, it handles test plan execution, manual test sessions, result uploads, and defect tracking. When an agent crafts an invalid call, the server returns a dedicated hint to help the model recover on the next attempt.

The server cannot function without `ALLURE_ENDPOINT` and `ALLURE_API_TOKEN`. Most project-scoped operations also require a configured `ALLURE_PROJECT_ID`.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `ALLURE_ENDPOINT`, `ALLURE_PROJECT_ID`, `ALLURE_API_TOKEN` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add lucius-mcp -e ALLURE_ENDPOINT=<ALLURE_ENDPOINT> -e ALLURE_PROJECT_ID=<ALLURE_PROJECT_ID> -e ALLURE_API_TOKEN=<ALLURE_API_TOKEN> -- uvx lucius-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>

### Codex

**Platform CLI**
```bash
codex mcp add lucius-mcp --env ALLURE_ENDPOINT=<ALLURE_ENDPOINT> --env ALLURE_PROJECT_ID=<ALLURE_PROJECT_ID> --env ALLURE_API_TOKEN=<ALLURE_API_TOKEN> -- uvx lucius-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "lucius-mcp": {
            "command": "uvx",
            "args": [
                "lucius-mcp"
            ],
            "env": {
                "ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
                "ALLURE_PROJECT_ID": "<ALLURE_PROJECT_ID>",
                "ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "lucius-mcp": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "lucius-mcp"
            ],
            "env": {
                "ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
                "ALLURE_PROJECT_ID": "<ALLURE_PROJECT_ID>",
                "ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e ALLURE_ENDPOINT=<ALLURE_ENDPOINT> -e ALLURE_PROJECT_ID=<ALLURE_PROJECT_ID> -e ALLURE_API_TOKEN=<ALLURE_API_TOKEN> lucius-mcp uvx lucius-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>

## When to use it
- manage and update test case documentation inside Allure TestOps
- produce automation test code from existing manual test scenarios
- track test runs, upload run results, and attach diagnostic files
- link reported defects to specific test cases and matchers

## Example prompts
- Find all test cases tagged with smoke in Allure TestOps
- Generate automated test code from test case 405
- Create a new test plan and start a test run for the release

## Similar
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74569
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18779
- [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13181
- [mobile-mcp](https://affpapa.org/en/nevibecode/mcp/mobile-mcp.md) — MCP server · ★ 10025
- [e2e](https://affpapa.org/en/nevibecode/mcp/e2e.md) — MCP server · ★ 11962
- [mockserver](https://affpapa.org/en/nevibecode/mcp/mockserver.md) — MCP server · ★ 4999

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md