Allure TestOps FAQs

Question 1

What are the core features of Allure TestOps MCP Server?

Accepted Answer

Key features include robust JWT bearer authentication with caching and refresh, project-aware tools, full support for test case custom fields (lookup and updates), and `stdio` transport for seamless integration with local MCP clients.

Question 2

How does authentication work with Allure TestOps MCP Server?

Accepted Answer

The server uses your user-generated Allure TestOps API token (`ALLURE_TOKEN`) to exchange for a JWT bearer token. This token is then cached in-memory and automatically refreshed on expiry, ensuring secure and continuous access to the Allure TestOps API.

Question 3

Can Allure TestOps MCP Server be integrated with other tools?

Accepted Answer

Yes, it supports `stdio` transport for easy integration with various local MCP clients such as Claude Desktop, Claude Code, Cursor, and any other MCP client that supports `stdio` servers, allowing for flexible test automation workflows.

Question 4

What is Allure TestOps MCP Server?

Accepted Answer

Allure TestOps MCP Server is a production-ready server designed for comprehensive management of test cases, launches, test results, and test plans within the Allure TestOps ecosystem. It offers extensive API coverage for these key testing assets.

Question 5

Which test management entities can be controlled via the server?

Accepted Answer

The server provides extensive API coverage for test cases (list, search, create, update, delete, custom fields, history), launches (create, update, close, statistics), test results (create, update, assign, resolve), and test plans (list, create, update, run).

Allure TestOps

Allure TestOps

主な機能

ユースケース

主な機能

ユースケース