Allure TestOps MCP Server
MCP server and CLI for managing Allure TestOps test cases, launches, plans and defects.
Tested on macOS and Linux
Use it
macOS arm64
You need first
- Runtimes:
Python 3.10 through 3.14 - Needs the network
- Keys or accounts: Allure API token
install lucius-mcp via uv tool install
uv tool install lucius-mcp
Check that it works
lucius test_case get --help 2>&1The output should contain “Mapped tool: get_test_case_details”.
Add it to your agent
claude mcp add lucius-mcp -e ALLURE_ENDPOINT='<ALLURE_ENDPOINT>' -e ALLURE_API_TOKEN='<ALLURE_API_TOKEN>' -- startJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"lucius-mcp": {
"command": "start",
"args": [],
"env": {
"ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
"ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
}
}
}
}You fill in
ALLURE_ENDPOINT: Allure TestOps base URL (required)ALLURE_API_TOKEN: Allure API token (required)
Ask the user for ALLURE_ENDPOINT, ALLURE_API_TOKEN; pickfit never had a value, so these are placeholders.
Add the lucius-mcp command as an MCP server in your MCP client, then call its tools such as list_test_cases from the client.
Linux x86_64
You need first
- Runtimes:
Python 3.10 through 3.14 - Needs the network
- Keys or accounts: Allure API token
install lucius-mcp with uv tool install so start/lucius are on PATH
uv tool install lucius-mcp
Add it to your agent
claude mcp add lucius-mcp -e ALLURE_ENDPOINT='<ALLURE_ENDPOINT>' -e ALLURE_API_TOKEN='<ALLURE_API_TOKEN>' -- startJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"lucius-mcp": {
"command": "start",
"args": [],
"env": {
"ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
"ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
}
}
}
}You fill in
ALLURE_ENDPOINT: Allure TestOps base URL (required)ALLURE_API_TOKEN: Allure API token (required)
Ask the user for ALLURE_ENDPOINT, ALLURE_API_TOKEN; pickfit never had a value, so these are placeholders.
Add the lucius-mcp command as an MCP server in your MCP client, then call its tools such as list_test_cases from the client.
What it does
- Create, update and manage test casesNot tested
- Generate test code for a framework from test casesNot tested
- Manage launches and test resultsNot tested
- Manage test plans and their contentsNot tested
How far pickfit got
macOS arm64
- Installs
- Connects
- 0 of 4 features work
- Works offline
Linux x86_64
- Installs
- Connects
- 0 of 4 features work
- Works offline
Other systems
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- manage test case documentation lifecycle
- manage launches and upload test results
- manage test plans and run them
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
An MCP client connects and lists its tools
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version 0.16.6
An MCP client handshake over stdio listed 70 tools.
Differences the test machine hit
- README: Python 3.10 through 3.14 supported, 3.15 experimental
In the test: Installed and ran successfully on Python 3.15.2
Linux x86_64
An MCP client connects and lists its tools
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.16.6
An MCP client handshake over stdio listed 70 tools.
Differences the test machine hit
- README: README documents `lucius ... --help` and `start` as server launch without clarifying `start --help` behavior.
In the test: Use `lucius --help` for CLI help; `start --help` ignores the flag and starts the MCP server on stdio (had to be killed after 30s).