MCP Tools DirectoryAbout this integration
Allure TestOps MCP — projects, launches, test cases, test results via REST API.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.9.3
- Package
- allure-testops-mcp
- Last compatibility test
- Not independently tested
Connect your agent
allure-testops-mcpPublisher documentation and executable manifest were reviewed from pinned captures. The package and Allure instance were not executed. Read tools are the documented default; write and destructive tools require explicit enablement, with destructive calls also requiring confirmation.
Capabilities: Explore Allure TestOps projects and launches, Inspect test cases, results, and reference data, Optionally manage test cases and categories when writes are enabled
Connected profiles
Additional details
io.github.mshegolev/allure-testops-mcp
Source ↗ · Checked 2026-09-170.9.3
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17ALLURE_URL, ALLURE_TOKEN
Source ↗ · Checked 2026-09-17allure-testops-mcp
Source ↗ · Checked 2026-09-190.9.3
Source ↗ · Checked 2026-09-19Publisher documentation explicitly describes a stdio process that the MCP client runs and respawns for each session.
Source ↗ · Checked 2026-09-19An Allure TestOps instance URL and API token are required; token permissions inherit the issuing account's role.
Source ↗ · Checked 2026-09-19The publisher explicitly documents stdio transport and client configuration; the existing null endpoint is preserved.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19