Allure TestOps MCP — projects, launches, test cases, test results via REST API.
If you already use Allure, the allure mcp server is the piece that lets your assistant work with it directly. Allure TestOps MCP — projects, launches, test cases, test results via REST API.
20 tools — 13 read-only (always on) and 7 write tools (opt-in via ALLURE_ENABLE_WRITE=true). Every tool carries MCP annotations and returns both a typed structuredContent payload and a markdown summary.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
allure_list_projects — readallure_get_project_statistics — readallure_list_launches — readallure_get_test_results — readallure_search_failed_tests — readallure_list_test_cases — readallure_get_test_case — readallure_get_test_case_custom_fields — readallure_list_statuses — readallure_list_layers — readallure_list_custom_fields — readallure_list_categories — readConfiguration is passed through the environment: ALLURE_URL, ALLURE_TOKEN, ALLURE_SSL_VERIFY, ALLURE_ENABLE_WRITE, ALLURE_TEST_PROJECT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Allure's toolset — allure_list_projects, allure_get_project_statistics, allure_list_launches and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mshegolev; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Allure's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| allure_list_projects | read |
| allure_get_project_statistics | read |
| allure_list_launches | read |
| allure_get_test_results | read |
| allure_search_failed_tests | read |
| allure_list_test_cases | read |
| allure_get_test_case | read |
| allure_get_test_case_custom_fields | read |
| allure_list_statuses | read |
| allure_list_layers | read |
| allure_list_custom_fields | read |
| allure_list_categories | read |
| allure_list_category_matchers | read |
| allure_create_test_case | write ⚑ |
{
"mcpServers": {
"allure-testops": {
"command": "uvx",
"args": ["allure-testops-mcp"],
"env": {
"ALLURE_URL": "your-value",
"ALLURE_TOKEN": "your-value",
"ALLURE_SSL_VERIFY": "your-value",
"ALLURE_ENABLE_WRITE": "your-value",
"ALLURE_TEST_PROJECT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ALLURE_URL | Endpoint or connection string the server talks to. | Yes |
| ALLURE_TOKEN | Credential the server authenticates with. | Yes |
| ALLURE_SSL_VERIFY | Configuration value read at startup. | Optional |
| ALLURE_ENABLE_WRITE | Configuration value read at startup. | Optional |
| ALLURE_TEST_PROJECT_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.