Allure TestOps MCP server: 13 tools in beta

A server that arrives with the product rather than as a package, what its thirteen tools reach, and the pricing note in its own documentation.

Last verified 27 August 2026 · from Qameta's own Allure TestOps documentation

This page is one of 90 in a directory of monitoring and developer tools. Each page checks what an AI coding agent can get out of the tool through its MCP server, the connector that lets the agent query the tool directly.

What is the Allure TestOps MCP server?

It is Allure TestOps's server for the Model Context Protocol. TestOps is a test management platform, so a connected agent can author and search test cases rather than only read results.

The tools split cleanly. testops_create_testcase writes a case with full metadata including steps, tags, custom fields and links, and testops_update_testcase supports partial updates.

Shared steps are first-class. testops_find_sharedsteps, testops_create_sharedstep and testops_update_sharedstep exist because a shared step is reused across many cases, so changing one has wide reach.

Allure TestOps builds its 13-tool server into licensed instances from release 26.1.1. The tools cover test management. They do not expose operational, agent or cost data.

For an agent, that means TestOps answers what the test suite says the product should do, and lets the agent write more of that suite. That is authoring rather than debugging. It has no view of the pipeline or the running system, so both need their own connector.

What can an AI agent do with Allure TestOps?

The agent calls testops_get_project first to establish which project it is in, then composes the search. Almost everything else is scoped to a project, and the wrong project returns an empty result rather than an error.

What connecting costs before the first question

A context window is the amount of text a model can hold at once. Thirteen tools cost 1,104 to 1,138 tokens on Claude. The two tokenizer generations differ by barely thirty tokens, because the descriptions are short.

The server is built into a licensed TestOps instance rather than shipped as a package, so this is what the endpoint on your own instance costs an agent to load.

Encodings: GPT-5.6, GPT-5.5 o200k_base; GPT-4, GPT-3.5 cl100k_base; Claude Haiku 4.5 to Opus 5 count_tokens. Counted from the 13 tool entries in the vendor's own documentation. That documentation is the only public inventory.

The server could not be run for a live tools/list. No input schemas are available, so these figures cover each tool's name and description only. They are a floor, not the figure.

The Claude columns are measured through the API's count_tokens endpoint with an empty schema per tool. So they cover the same content as the GPT columns. The range there is two tokenizer generations. Haiku 4.5 and Opus 4.6 are at the low end. Opus 5 and Sonnet 5 are at the high end. The gap between them is a small fraction.

Allure TestOps MCP server limits: where answers come back incomplete

The limits below follow from a server that is part of a licensed product rather than a package.

How to configure Allure TestOps MCP for agents

1. 1

   Check your TestOps version

   The server exists from release 26.1.1 onward and is not available before it.

2. 2

   Read the pricing note

   The documentation calls this a public beta and says it may be subject to additional fees in future releases.

3. 3

   Decide who may delete

   testops_delete_testcase is reachable, and testops_restore_testcase exists because deletion is recoverable.

4. 4

   Treat shared steps carefully

   Updating one changes every case that includes it.

Paste this into your agent’s instructions

Most of this surface writes, and muting hides failures rather than fixing them. An answer must disclose both actions.

When you answer using Allure TestOps MCP tools, state:
- The project the answer covers.
- Whether you created, updated or deleted a test case or a
  shared step. A shared step change reaches every case using it.
- Whether you muted anything. A mute hides a failure from
  reporting until it is deleted.
Never state that data does not exist. State that no test cases
matched the search above.
Write your answer in ASD-STE100 Simplified Technical
English. Use short sentences with one idea in each.

Do you need the MCP server at all?

Not for a scheduled report. TestOps has a REST API, and for bulk import or anything on a timer it is the direct route.

The connector earns its place during authoring. An agent that has just written code can create the matching test case with steps, tags and links in the same conversation.

For test results across runs rather than test definitions, ReportPortal covers launches and failure history in more depth.

Connect it when an agent is authoring tests. Use the REST API for bulk and scheduled work.

Allure TestOps MCP server setup

There is nothing to install. If your instance runs 26.1.1 or later, the endpoint is already there at /api/mcp.

Clients connect to your own TestOps host, and the instance's own authentication applies.

claude mcp add allure -- npx mcp-remote \
  https://testops.internal/api/mcp \
  --header "Authorization: api-token <your-testops-token>"

{"mcpServers":{"allure":{"command":"npx","args":[
  "mcp-remote","https://testops.internal/api/mcp",
  "--header","Authorization: api-token ${AUTH_TOKEN}"],
  "env":{"AUTH_TOKEN":"<your-testops-token>"}}}}

[mcp_servers.allure]
command = "npx"
args = ["mcp-remote", "https://testops.internal/api/mcp",
  "--header", "Authorization: api-token <your-testops-token>"]

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

{"mcpServers":{"allure":{"command":"npx","args":[
  "mcp-remote","https://testops.internal/api/mcp",
  "--header","Authorization: api-token ${AUTH_TOKEN}"],
  "env":{"AUTH_TOKEN":"<your-testops-token>"}}}}

{"mcpServers":{"allure":{"command":"npx","args":[
  "mcp-remote","https://testops.internal/api/mcp",
  "--header","Authorization: api-token ${AUTH_TOKEN}"],
  "env":{"AUTH_TOKEN":"<your-testops-token>"}}}}

{"servers":{"allure":{"command":"npx","args":[
  "mcp-remote","https://testops.internal/api/mcp",
  "--header","Authorization: api-token ${AUTH_TOKEN}"],
  "env":{"AUTH_TOKEN":"<your-testops-token>"}}}}

{"mcpServers":{"allure":{"command":"npx","args":[
  "mcp-remote","https://testops.internal/api/mcp",
  "--header","Authorization: api-token ${AUTH_TOKEN}"],
  "env":{"AUTH_TOKEN":"<your-testops-token>"}}}}

# The MCP endpoint is present from TestOps 26.1.1.
curl -H "Authorization: api-token <your-testops-token>" \
  https://testops.internal/api/mcp

Read-only access, permissions and security

• Eight of the thirteen tools write

  Creating, updating and deleting test cases and shared steps, plus creating and deleting mutes.

• A shared step update has wide reach

  Shared steps exist to be reused, so one change propagates to every case that includes it.

• Muting hides failures

  testops_create_mute suppresses a failing test from reporting until the mute is removed.

• The instance is the boundary

  The server is part of TestOps, so its authentication and permissions are the ones you already run.

Troubleshooting

There is no MCP endpoint

The server ships from release 26.1.1. An earlier TestOps instance does not have it at all.

A search returns nothing

Most tools are scoped to a project. Call testops_get_project first and confirm which project the agent is querying.

A deleted case needs to come back

testops_restore_testcase reverses a deletion, which is why it sits alongside the delete tool.

Failures stopped appearing in reports

Check for a mute. testops_create_mute hides a failing test until testops_delete_mute removes the mute.

Allure TestOps MCP server: Reference

What engineers report

The documentation is short and specific, so the figures below come from it directly.

Tool inventory, release version and beta status read from Qameta's own Allure TestOps documentation on 24 August 2026. The endpoint is part of a licensed instance rather than a downloadable package, so no tools/list capture was possible.

Should you connect an agent to Allure TestOps?

Yes. Best for authoring work on a project-scoped token, with mutes treated as a reviewable action.

Strongest fit

TestOps teams on 26.1.1 or later who want an agent to author and maintain test cases.

Main advantage

Nothing to deploy: the endpoint arrives with the product and uses the authentication you already run.

Main weakness

A public beta with a documented possibility of future fees, and no route at all before 26.1.1.

Operational risk

Eight writing tools, including deletion and muting, both of which change what reporting shows.

Frequently asked questions