Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
claude mcp add lucius --env ALLURE_ENDPOINT=your-value --env ALLURE_PROJECT_ID=your-value --env ALLURE_API_TOKEN=your-value -- uvx lucius-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lucius": {
"command": "uvx",
"args": [
"lucius-mcp"
],
"env": {
"ALLURE_ENDPOINT": "your-value",
"ALLURE_PROJECT_ID": "your-value",
"ALLURE_API_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lucius": {
"type": "stdio",
"command": "uvx",
"args": [
"lucius-mcp"
],
"env": {
"ALLURE_ENDPOINT": "your-value",
"ALLURE_PROJECT_ID": "your-value",
"ALLURE_API_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account ivanostanin, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.16.9) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker, MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Alion: company, startup and market intelligence
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Companies, jobs, pay and people; check counterparties, register agents, write to companies.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Lucius is a specialized Model Context Protocol (MCP) server for Allure TestOps, built with FastMCP and Starlette.
Allure TestOps is a powerful tool with a huge API. When you're using an AI agent to manage your tests, it can easily get lost in the details or fail because of a small technical mistake.
Lucius makes this easier by giving your AI tools that are simple to use and hard to break:
See the full reference in Tool Reference.
| Tool Category | Description | All Tools |
|---|---|---|
| Test Case Mgmt | Full lifecycle for test documentation. | create_test_case, update_test_case, delete_test_case, delete_archived_test_cases, get_test_case_details, get_test_case_custom_fields |
| Automation Generation | Generate framework-specific code from existing test cases. | generate_test_code |
| Search & Discovery | Advanced search and project metadata discovery. | list_test_cases, search_test_cases, get_custom_fields, list_integrations, get_project |
| Shared Steps | Create and manage reusable step sequences. | create_shared_step, list_shared_steps, update_shared_step, delete_shared_step, delete_archived_shared_steps, link_shared_step, unlink_shared_step |
| Test Layers | Manage test taxonomy and auto-mapping schemas. | list_test_layers, create_test_layer, update_test_layer, delete_test_layer, list_test_layer_schemas, create_test_layer_schema, update_test_layer_schema, delete_test_layer_schema |
| Test Hierarchy | Organize suites and assign tests in tree paths. | create_test_suite, list_test_suites, assign_test_cases_to_suite, delete_test_suite |
| Custom Fields | Project-level management of custom field values. | list_custom_field_values, create_custom_field_value, update_custom_field_value, delete_custom_field_value, delete_unused_custom_fields |
| Launch Management | Manage launches, result uploads, manual execution, reruns, and attachments. | create_launch, list_launches, get_launch, list_launch_test_results, upload_test_results, attach_file_to_launch, rerun_test_results_manually, start_manual_test_session, submit_manual_test_results, add_test_result_attachment |
| Test Result Management | Inspect one exact TestOps result and prepare verified evidence downloads. | get_test_result, prepare_attachment_download |
| Test Plans | Manage test plans and their content. | create_test_plan, update_test_plan, delete_test_plan, list_test_plans, manage_test_plan_content, run_test_plan |
| Defect Mgmt | Track defects, linkage, and automation rules. | create_defect, get_defect, update_defect, delete_defect, list_defects, link_defect_to_test_case, unlink_issue_from_test_case, list_defect_test_cases, create_defect_matcher, list_defect_matchers, update_defect_matcher, delete_defect_matcher |
curl -LsSf https://astral.sh/uv/install.sh | sh.env file with the variables below, or save CLI auth with lucius auth.uv run start.env for Quick Start| Variable | Description | Example |
|---|---|---|
ALLURE_ENDPOINT | Allure TestOps base URL | https://example.testops.cloud |
ALLURE_PROJECT_ID | Default Allure project ID (optional for get_project; required by project-scoped tools) | 123 |
ALLURE_API_TOKEN | Allure API token | |
MCP_MODE | MCP transport mode for Lucius runtime | stdio |
The easiest way to use Lucius in Claude Desktop is via the .mcpb bundle:
lucius-mcp.mcpb from Releases.To add Lucius to Claude Code, use the following command from within your project directory:
claude mcp add --transport stdio --scope project \
--env ALLURE_ENDPOINT=https://example.testops.cloud \ --env ALLURE_PROJECT_ID=123 \ --env ALLURE_API_TOKEN= \ --env MCP_MODE=stdio \ testops-mcp -- uvx --from lucius-mcp --refresh start
Project-scoped text config example (.mcp.json):
{
"mcpServers": { "testops-mcp": { "type": "stdio", "command": "uvx", "args": [ "--from", "lucius-mcp", "--refresh", "start" ], "env": { "ALLURE_ENDPOINT": "https://example.testops.cloud", "ALLURE_PROJECT_ID": "123", "ALLURE_API_TOKEN": " ", "MCP_MODE": "stdio" } } } }
To add Lucius to Codex (CLI or IDE extension), use:
codex mcp add testops-mcp \
--env ALLURE_ENDPOINT=https://example.testops.cloud \ --env ALLURE_PROJECT_ID=123 \ --env ALLURE_API_TOKEN= \ --env MCP_MODE=stdio \ -- uvx --from lucius-mcp --refresh start
Text config example (~/.codex/config.toml or project .codex/config.toml):
[mcp_servers.testops-mcp]
command = "uvx" args = ["--from", "lucius-mcp", "--refresh", "start"]
[mcp_servers.testops-mcp.env] ALLURE_ENDPOINT = "https://example.testops.cloud" ALLURE_PROJECT_ID = "123" ALLURE_API_TOKEN = " " MCP_MODE = "stdio"
For detailed setup, including Claude Desktop (MCPB) integration, see Setup Guide.
Lucius supports Python 3.11 through 3.14 for runtime use. The generated MCPB manifests and the representative Nuitka CLI compiler matrix validate the same range. Python 3.15 support is experimental: installation may require source builds, and platform compatibility is still being verified. See the development guide for current limitations. Python 3.10 remains unsupported because the locked filelock security update requires Python 3.11 or newer.
Lucius also provides a universal CLI entry point for direct tool execution from the command line:
# List available actions for an entity
uv run lucius test_case
uv run lucius test_case get --args '{"test_case_id": 1234}'
uv run lucius test_case get --help
uv run lucius auth --url https://example.testops.cloud --token --project 123 uv run lucius auth status uv run lucius auth clear
CLI Features:
CLI auth precedence is:
api_token or project_iduv run lucius authSaved CLI auth uses native config locations:
$XDG_CONFIG_HOME/lucius/auth.json or ~/.config/lucius/auth.json~/Library/Application Support/lucius/auth.json unless XDG overrides are explicitly set%LOCALAPPDATA%\lucius\auth.jsonFor full CLI documentation and installation instructions, see CLI Guide.
Lucius collects privacy-preserving usage telemetry to improve tool quality. Telemetry is enabled by default and sends metadata to https://stats.ostanin.me, an endpoint operated by the project owner (no third party has access to this endpoint).
If this is acceptable in your environment, staying opted in helps improve Lucius over time. If you want to opt out, set TELEMETRY_ENABLED=false in your environment.
No API tokens, test content, or tool arguments are sent.
See Telemetry & Privacy for the full data dictionary and telemetry behavior details.
Full documentation is available in the docs/ folder:
Contributions are welcome! Please see the Contribution Guidelines and the Development Guide for more details.