Lucius MCP
Wire your coding agent to Allure TestOps so you can list, update, and triage tests, launches, plans, and defects without leaving the editor.
Overview
Lucius MCP is an MCP server for the Ship phase that lets agents manage Allure TestOps tests, launches, plans, defects, and metadata.
What is this MCP server?
- Manage Allure TestOps tests, launches, test plans, defects, and project metadata via MCP tools
- Stdio transport via PyPI package lucius-mcp (uvx) or OCI image ghcr.io/ivanostanin/lucius-mcp:0.9.2
- Requires ALLURE_ENDPOINT, ALLURE_PROJECT_ID, and ALLURE_API_TOKEN environment variables
- Version 0.9.2 aligned with server.schema.json 2025-12-11 packaging metadata
- Keeps QA workflows agent-driven instead of context-switching to the TestOps web UI
- Server version 0.9.2
- Two distribution paths: PyPI lucius-mcp and OCI ghcr.io/ivanostanin/lucius-mcp:0.9.2
- Three required environment variables: endpoint, project ID, API token
Community signal: 6 GitHub stars.
What problem does it solve?
Switching between your agent session and the Allure TestOps UI slows down triage when you need quick answers about launches, plans, or defects.
Who is it for?
Solo builders or tiny teams using Allure TestOps who want agent-assisted test management and defect workflows during release prep.
Skip if: Projects that do not use Allure TestOps or only need local pytest output without a TMS.
What do I get? / Deliverables
After you register Lucius MCP with your TestOps credentials, your agent can query and update TestOps objects from the same thread where you fix code.
- Agent-callable tools for TestOps tests, launches, plans, and defects
- Stdio MCP connection documented in server.json v0.9.2
Recommended MCP Servers
Journey fit
TestOps work belongs in Ship because it supports release confidence, regression tracking, and defect management right before and after you push. Testing is the canonical shelf for anything that manipulates test cases, launch runs, and quality metadata in a TMS.
How it compares
Allure TestOps MCP bridge, not an in-repo test runner or skills.sh skill.
Common Questions / FAQ
Who is Lucius MCP for?
Developers and QA-minded solo builders who store tests and launches in Allure TestOps and use MCP-capable coding agents.
When should I use Lucius MCP?
Use it during Ship when you triage CI failures, plan regression runs, or update defects and metadata in TestOps from your agent.
How do I add Lucius MCP to my agent?
Install lucius-mcp via uvx or the published OCI image, set ALLURE_ENDPOINT, ALLURE_PROJECT_ID, and ALLURE_API_TOKEN, then register the stdio MCP server in Claude Code, Cursor, or Codex.