Lucius MCP — Claude Code MCP server: what it does, how to install
Connects AI assistants to Allure TestOps for managing test cases, runs, and defects. Useful for teams automating QA workflows directly in chat.
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-mcpWhat Lucius MCP 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.
What it helps with
- 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 for the agent
- 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
How to install Lucius MCP
Platform CLI
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-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>
Platform CLI
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-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>
Config file
{
"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>
Config file
{
"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>
Platform CLI
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-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from lucius-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Lucius MCP
How to install Lucius MCP in Claude Code?
Run `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`.
What does Lucius MCP do?
It provides tools for interacting with Allure TestOps test cases, launches, custom fields, and issue tracking. Coding assistants can query project metadata and update QA documentation.
What prerequisites are needed to run Lucius MCP?
You need uvx installed alongside your Allure instance URL in ALLURE_ENDPOINT, an API token in ALLURE_API_TOKEN, and an optional or required ALLURE_PROJECT_ID.
