pickfit

BrowseMCP servers

Allure TestOps MCP Server

MCP server and CLI for managing Allure TestOps test cases, launches, plans and defects.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Python 3.10 through 3.14
  • Needs the network
  • Keys or accounts: Allure API token
  1. install lucius-mcp via uv tool install

    uv tool install lucius-mcp

Check that it works

lucius test_case get --help 2>&1

The output should contain “Mapped tool: get_test_case_details”.

Add it to your agent

claude mcp add lucius-mcp -e ALLURE_ENDPOINT='<ALLURE_ENDPOINT>' -e ALLURE_API_TOKEN='<ALLURE_API_TOKEN>' -- start
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "lucius-mcp": {
      "command": "start",
      "args": [],
      "env": {
        "ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
        "ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
      }
    }
  }
}

You fill in

  • ALLURE_ENDPOINT: Allure TestOps base URL (required)
  • ALLURE_API_TOKEN: Allure API token (required)

Ask the user for ALLURE_ENDPOINT, ALLURE_API_TOKEN; pickfit never had a value, so these are placeholders.

Add the lucius-mcp command as an MCP server in your MCP client, then call its tools such as list_test_cases from the client.

Linux x86_64

You need first

  • Runtimes: Python 3.10 through 3.14
  • Needs the network
  • Keys or accounts: Allure API token
  1. install lucius-mcp with uv tool install so start/lucius are on PATH

    uv tool install lucius-mcp

Add it to your agent

claude mcp add lucius-mcp -e ALLURE_ENDPOINT='<ALLURE_ENDPOINT>' -e ALLURE_API_TOKEN='<ALLURE_API_TOKEN>' -- start
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "lucius-mcp": {
      "command": "start",
      "args": [],
      "env": {
        "ALLURE_ENDPOINT": "<ALLURE_ENDPOINT>",
        "ALLURE_API_TOKEN": "<ALLURE_API_TOKEN>"
      }
    }
  }
}

You fill in

  • ALLURE_ENDPOINT: Allure TestOps base URL (required)
  • ALLURE_API_TOKEN: Allure API token (required)

Ask the user for ALLURE_ENDPOINT, ALLURE_API_TOKEN; pickfit never had a value, so these are placeholders.

Add the lucius-mcp command as an MCP server in your MCP client, then call its tools such as list_test_cases from the client.

What it does

  • Create, update and manage test cases
    Not tested
  • Generate test code for a framework from test cases
    Not tested
  • Manage launches and test results
    Not tested
  • Manage test plans and their contents
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • manage test case documentation lifecycle
  • manage launches and upload test results
  • manage test plans and run them

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.16.6

An MCP client handshake over stdio listed 70 tools.

Differences the test machine hit

  • README: Python 3.10 through 3.14 supported, 3.15 experimental
    In the test: Installed and ran successfully on Python 3.15.2

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.16.6

An MCP client handshake over stdio listed 70 tools.

Differences the test machine hit

  • README: README documents `lucius ... --help` and `start` as server launch without clarifying `start --help` behavior.
    In the test: Use `lucius --help` for CLI help; `start --help` ignores the flag and starts the MCP server on stdio (had to be killed after 30s).

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.