Allure TestOps MCP โ projects, launches, test cases, test results via REST API.
Connect Runs on your machine
claude mcp add allure-testops-mcp -e ALLURE_URL=<ALLURE_URL> -e ALLURE_TOKEN=<ALLURE_TOKEN> -e ALLURE_SSL_VERIFY=<ALLURE_SSL_VERIFY> -- uvx allure-testops-mcp==0.9.5
{
"mcpServers": {
"allure-testops-mcp": {
"command": "uvx",
"args": [
"allure-testops-mcp==0.9.5"
],
"env": {
"ALLURE_URL": "<ALLURE_URL>",
"ALLURE_TOKEN": "<ALLURE_TOKEN>",
"ALLURE_SSL_VERIFY": "<ALLURE_SSL_VERIFY>"
}
}
}
}
{
"mcpServers": {
"allure-testops-mcp": {
"command": "uvx",
"args": [
"allure-testops-mcp==0.9.5"
],
"env": {
"ALLURE_URL": "<ALLURE_URL>",
"ALLURE_TOKEN": "<ALLURE_TOKEN>",
"ALLURE_SSL_VERIFY": "<ALLURE_SSL_VERIFY>"
}
}
}
}
{
"servers": {
"allure-testops-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"allure-testops-mcp==0.9.5"
],
"env": {
"ALLURE_URL": "<ALLURE_URL>",
"ALLURE_TOKEN": "<ALLURE_TOKEN>",
"ALLURE_SSL_VERIFY": "<ALLURE_SSL_VERIFY>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ALLURE_URLRequired | Allure TestOps URL (e.g. https://allure.example.com) |
ALLURE_TOKENRequired, secret | API token from Allure TestOps (Profile -> API tokens) |
ALLURE_SSL_VERIFYOptional | Verify SSL certificates (true/false). Set to 'false' for self-signed corp certs. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 29 Oct 2026 |
| Last updated | 29 Oct 2026 |
| Registry name | io.github.mshegolev/allure-testops-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
