MCP Tools DirectoryAbout this integration
MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.15.5
- Package
- lucius-mcp
- Last compatibility test
- Not independently tested
Connect your agent
lucius-mcpPublisher README and Python manifest reviewed; package and Allure TestOps endpoint were not executed. The stdio process can run after endpoint, project, and API-token provisioning. The documented telemetry is enabled by default and may be disabled with TELEMETRY_ENABLED=false; operators should review that behavior before use.
Capabilities: Manage Allure TestOps test cases, Manage shared steps and test suites, Manage launches and results, Manage test plans and defects
Connected profiles
Additional details
io.github.ivanostanin/lucius-mcp
Source ↗ · Checked 2026-09-170.15.5
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKEN
Source ↗ · Checked 2026-09-17lucius-mcp
Source ↗ · Checked 2026-09-190.15.6
Source ↗ · Checked 2026-09-19The publisher documents starting the server from configured environment values and provides a static stdio MCP client configuration.
Source ↗ · Checked 2026-09-19Allure TestOps access uses a provisioned API token; the project id is a separate scope setting.
Source ↗ · Checked 2026-09-19The documented MCP mode is stdio with a local uvx-launched process connecting to the configured Allure endpoint.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19