Lucius MCP

OCI · GHCR.IO/IVANOSTANIN/LUCIUS-MCP:0.14.0 · 4 COMPONENTS · SCANNED AUG 3

MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.

Available components

mcpb · lucius-mcp-0.14.0-python.mcpb 13 mcpb · lucius-mcp-0.14.0-uv.mcpb 17 oci · ghcr.io/ivanostanin/lucius-mcp:0.14.0 35 pypi · lucius-mcp 25

35 35 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
CVE data not yet available for this package.Unverified
Install-script risk not yet assessed.Unverified
Dependency-health data not yet available.Unverified

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: no license is declared. See how to fix → Fail
Actively maintained (last published 4 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability66

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 8396 tokens (~127/item across 66 items; 66 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/ivanostanin/lucius-mcp:0.14.0

Claude Codex opencode Hermes Other

# add to Claude Code

claude mcp add ivanostanin-lucius-mcp -- docker run --rm -i ghcr.io/ivanostanin/lucius-mcp:0.14.0

# add to Codex CLI

codex mcp add ivanostanin-lucius-mcp -- docker run --rm -i ghcr.io/ivanostanin/lucius-mcp:0.14.0

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ivanostanin-lucius-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/ivanostanin/lucius-mcp:0.14.0"
      ],
      "enabled": true
    }
  }
}

# ~/.hermes/config.yaml

mcp_servers:
  ivanostanin-lucius-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ivanostanin/lucius-mcp:0.14.0"]

// mcp.json

{
  "mcpServers": {
    "ivanostanin-lucius-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ivanostanin/lucius-mcp:0.14.0"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

1 Aug 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 +31
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
30 Jul 26 8

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed oci/ghcr.io/ivanostanin/lucius-mcp:0.14.0

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 66 exposed · ~8,396 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

add_test_result_attachment Add Test Result Attachment ~90

Upload evidence to a manual test result.

Input Output Examples

Name	Type	Req	Description
attachment	object	yes	Attachment payload using the repo-standard pattern: {name, content_type, content? \| url?}.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
test_result_id	integer	yes	Manual test result ID (required).

Name	Type	Req	Description
file_names	—	—	—
status_code	—	—	—
target_id	—	—	—
target_kind	—	—	—

No examples provided.

add_test_step_attachment Add Test Step Attachment ~205

Upload evidence to a manual attachment step inside a test result.

Input Output Examples

Name	Type	Req	Description
attachment	object	yes	Attachment payload using the repo-standard pattern: {name, content_type, content? \| url?}.
attachment_id	—	—	Optional explicit manual step attachment ID resolved from the test result execution.
fixture_name	—	—	Optional fixture name used only for the legacy fixture-step fallback.
fixture_result_id	—	—	Optional explicit fixture result ID for legacy fixture-step fallback.
fixture_type	—	—	Optional fixture type hint for the legacy fixture-step fallback: 'before' or 'after'.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
step_index	—	—	Optional zero-based manual step index to resolve within the test result execution.
step_name	—	—	Optional attachment-step name to resolve within the manual test result.
test_result_id	integer	yes	Parent test result ID (required).

Name	Type	Req	Description
file_names	—	—	—
status_code	—	—	—
target_id	—	—	—
target_kind	—	—	—

No examples provided.

assign_test_cases_to_suite Assign Test Cases To Suite ~123

Assign test cases to a suite path in hierarchy. ⚠️ CAUTION: Destructive. Reassigning test cases changes their hierarchy location.

Input Output Examples

Name	Type	Req	Description
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID.
suite_id	integer	yes	Target suite/group node ID for assignment.
test_case_ids	array	yes	List of test case IDs to assign to the suite.
tree_id	—	—	Target hierarchy tree ID. If omitted, default project tree is used.

Name	Type	Req	Description
assigned_count	—	—	—
suite_id	—	—	—
test_case_ids	—	—	—
tree_id	—	—	—

No examples provided.

close_launch Close Launch ~71

Close a launch and return updated launch details.

Input Output Examples

Name	Type	Req	Description
api_token	—	—	Optional runtime API token override.
launch_id	integer	yes	Launch ID (required).
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.

Name	Type	Req	Description
autoclose	—	—	—
closed	—	—	—
created_date	—	—	—
external	—	—	—
id	—	—	—
known_defects_count	—	—	—
last_modified_date	—	—	—
manual_execution_guidance	—	—	—
name	—	—	—
new_defects_count	—	—	—
operation	—	—	—
project_id	—	—	—
url	—	—	—

No examples provided.

create_custom_field_value Create Custom Field Value ~100

Create a new custom field value option.

Input Output Examples

Name	Type	Req	Description
custom_field_id	—	—	Project-scoped custom field ID to create a value for.
custom_field_name	—	—	Custom field name to resolve when custom_field_id is not provided.
name	string	yes	Name for the new custom field value.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.

Name	Type	Req	Description
custom_field_id	—	—	—
custom_field_name	—	—	—
id	—	—	—
name	—	—	—

No examples provided.

create_defect Create Defect ~83

Create a new defect in the current project. Use this tool to register a known defect that can later be linked to failing test results through defect matchers (automation rules).

Input Output Examples

Name	Type	Req	Description
description	—	—	Optional markdown description
name	string	yes	Name / title of the defect
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
description	—	—	—
id	—	—	—
name	—	—	—
url	—	—	—

No examples provided.

create_defect_matcher Create Defect Matcher ~137

Create a defect matcher (automation rule) for a defect. Matchers automatically link future failing test results to a defect when the test failure's error message or stack trace matches the provided regex patterns. At least one of ``message_regex`` or ``trace_regex`` must be supplied.

Input Output Examples

Name	Type	Req	Description
defect_id	integer	yes	ID of the parent defect
message_regex	—	—	Regex to match against error messages
name	string	yes	Human-readable matcher rule name
output_format	—	—	Output format: 'json' (default) or 'plain'.
trace_regex	—	—	Regex to match against stack traces

Name	Type	Req	Description
defect_id	—	—	—
id	—	—	—
message_regex	—	—	—
name	—	—	—
trace_regex	—	—	—

No examples provided.

create_launch Create Launch ~117

Create a new launch in Allure TestOps.

Input Output Examples

Name	Type	Req	Description
autoclose	—	—	Whether the launch auto-closes.
external	—	—	Whether the launch is external.
issues	—	—	Optional list of issue dictionaries.
links	—	—	Optional list of external links (name, url, type).
name	string	yes	Launch name (required).
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
tags	—	—	Optional list of tags.

Name	Type	Req	Description
autoclose	—	—	—
closed	—	—	—
created_date	—	—	—
external	—	—	—
id	—	—	—
known_defects_count	—	—	—
last_modified_date	—	—	—
manual_execution_guidance	—	—	—
name	—	—	—
new_defects_count	—	—	—
operation	—	—	—
project_id	—	—	—
url	—	—	—

No examples provided.

create_shared_step Create Shared Step ~159

Create a new reusable Shared Step.

Input Output Examples

Name	Type	Req	Description
name	string	yes	The name of the shared step (e.g., "Login as Admin").
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
steps	—	—	Optional list of steps. Each step is a dictionary with: - action (str): The step description (e.g., "Enter username"). - expected (str, optional): The expected result. - attachments (list[dict], opti…

Name	Type	Req	Description
id	—	—	—
name	—	—	—
project_id	—	—	—
url	—	—	—

No examples provided.

create_test_case Create Test Case ~370

Create a new test case in Allure TestOps.

Input Output Examples

Name	Type	Req	Description
attachments	—	—	List of attachments.Example Base64: [{'name': 's.png', 'content': '<base64>', 'content_type': 'image/png'}]Example URL: [{'name': 'report.pdf', 'url': 'http://example.com/report.pdf', 'content_type':…
custom_fields	—	—	Dictionary of custom field names and their values (string or list of strings).Example: {'Layer': 'UI', 'Components': ['Auth', 'DB']}
description	—	—	A markdown description of the test case.
integration_id	—	—	Optional integration ID for issue linking (use list_integrations to find IDs). Required when multiple integrations exist. Mutually exclusive with integration_name.
integration_name	—	—	Optional integration name for issue linking (exact case-sensitive match). Required when multiple integrations exist. Mutually exclusive with integration_id.
issues	—	—	Optional list of issue keys to link (e.g., ['PROJ-123']).
name	string	yes	The name of the test case.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
steps	—	—	List of steps. Each step must be a dict with 'action' and 'expected' keys. Example: [{'action': 'Login', 'expected': 'Dashboard visible'}]
tags	—	—	List of tag names.
test_layer_id	—	—	Optional test layer ID to assign (use list_test_layers to find IDs). If provided, the layer must exist in the project.
test_layer_name	—	—	Optional test layer name to assign (exact case-sensitive match). Mutually exclusive with test_layer_id.

Name	Type	Req	Description
id	—	—	—
issues	—	—	—
name	—	—	—
url	—	—	—

No examples provided.

create_test_layer Create Test Layer ~115

Create a new test layer in Allure TestOps. Test layers define taxonomy for categorizing test cases. Common examples include 'Unit', 'Integration', 'E2E', 'UI', 'API', etc.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Name of the test layer (e.g., 'Unit', 'Integration', 'E2E').
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID to create the test layer in.

Name	Type	Req	Description
id	—	—	—
name	—	—	—

No examples provided.

create_test_layer_schema Create Test Layer Schema ~142

Create a new test layer schema to map a custom field key to a test layer. Test layer schemas define the mapping between custom field keys and test layers. This allows test cases with specific custom field values to be automatically assigned to the correct test layer.

Input Output Examples

Name	Type	Req	Description
key	string	yes	The schema key (e.g., custom field name like 'layer' or 'test_layer').
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	integer	yes	Allure TestOps project ID to create the schema in.
test_layer_id	integer	yes	ID of the test layer to link to this schema.

Name	Type	Req	Description
id	—	—	—
key	—	—	—
test_layer_id	—	—	—
test_layer_name	—	—	—

No examples provided.

create_test_plan Create Test Plan ~152

Create a new Test Plan in Allure TestOps. This tool allows creating a Test Plan, which is a collection of Test Cases to be executed. You can define the content of the plan either by: 1. Explicitly listing Test Case IDs (`test_case_ids`). 2. Providing an AQL (Allure Query Language) filter (`aql_filter`). 3. Both (explicit selection + dynamic filter).

Input Output Examples

Name	Type	Req	Description
aql_filter	—	—	AQL query to select test cases
name	string	yes	Name of the test plan
output_format	—	—	Output format: 'json' (default) or 'plain'.
test_case_ids	—	—	List of Test Case IDs to include

Name	Type	Req	Description
aql_filter	—	—	—
id	—	—	—
name	—	—	—
test_case_ids	—	—	—
test_case_urls	—	—	—
url	—	—	—

No examples provided.

create_test_suite Create Test Suite ~98

Create a new test suite node in the hierarchy tree.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Suite name to create in hierarchy.
output_format	—	—	Output format: 'json' (default) or 'plain'.
parent_suite_id	—	—	Parent suite/group node ID for nested suite creation.
project_id	—	—	Allure TestOps project ID.
tree_id	—	—	Target hierarchy tree ID. If omitted, default project tree is used.

Name	Type	Req	Description
id	—	—	—
name	—	—	—
parent_suite_id	—	—	—
tree_id	—	—	—

No examples provided.

delete_archived_shared_steps Delete Archived Shared Steps ~69

Permanently delete all archived shared steps in the current project.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional Allure TestOps project ID override.

Name	Type	Req	Description
action	—	—	Requested operation name.
deleted_count	—	—	—
requires_confirmation	—	—	—

No examples provided.

delete_archived_test_cases Delete Archived Test Cases ~71

Permanently delete all archived/deleted test cases in the current project.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional Allure TestOps project ID override.

Name	Type	Req	Description
action	—	—	Requested operation name.
deleted_count	—	—	—
requires_confirmation	—	—	—

No examples provided.

delete_custom_field_value Delete Custom Field Value ~130

Delete a custom field value. ⚠️ CAUTION: Destructive.

Input Output Examples

Name	Type	Req	Description
cfv_id	integer	yes	Custom field value ID to delete.
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
custom_field_id	—	—	Project-scoped custom field ID (optional, resolves by name if missing).
custom_field_name	—	—	Custom field name to resolve when custom_field_id is not provided.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.

Name	Type	Req	Description
action	—	—	Requested operation name.
cfv_id	—	—	—
id	—	—	—
requires_confirmation	—	—	—
status	—	—	—

No examples provided.

delete_defect Delete Defect ~96

Permanently delete a defect and all its associated matchers. This is a destructive operation. The ``confirm`` parameter must be set to ``true`` to actually perform the deletion.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Safety flag — must be set to true to confirm deletion
defect_id	integer	yes	ID of the defect to delete
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
defect_id	—	—	—
id	—	—	—
status	—	—	—

No examples provided.

delete_defect_matcher Delete Defect Matcher ~96

Permanently delete a defect matcher (automation rule). This is a destructive operation. The ``confirm`` parameter must be set to ``true`` to actually perform the deletion.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Safety flag — must be set to true to confirm deletion
matcher_id	integer	yes	ID of the matcher to delete
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
id	—	—	—
matcher_id	—	—	—
status	—	—	—

No examples provided.

delete_launch Delete Launch ~68

Delete a launch by ID. ⚠️ CAUTION: Destructive.

Input Output Examples

Name	Type	Req	Description
launch_id	integer	yes	Launch ID to delete (required).
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.

Name	Type	Req	Description
launch_id	—	—	—
message	—	—	—
status	—	—	—

No examples provided.

delete_shared_step Delete Shared Step ~113

Delete a shared step from the library. ⚠️ CAUTION: Destructive. ⚠️ CAUTION: If this shared step is used by test cases, deleting it will break those references.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be True to proceed (safety measure).
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
step_id	integer	yes	The shared step ID to delete (required).

Name	Type	Req	Description
action	—	—	Requested operation name.
id	—	—	—
requires_confirmation	—	—	—
status	—	—	—
step_id	—	—	—
url	—	—	—

No examples provided.

delete_test_case Delete Test Case ~142

Archive an obsolete test case. ⚠️ CAUTION: Destructive. This performs a SOFT DELETE (archive). The test case can typically be recovered from the Allure UI if needed. ⚠️ CAUTION: This action removes the test case from active views. Historical data and launch associations may be affected.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional Allure TestOps project ID override.
test_case_id	integer	yes	The Allure test case ID to archive.

Name	Type	Req	Description
action	—	—	Requested operation name.
error	—	—	—
name	—	—	—
requires_confirmation	—	—	—
status	—	—	—
test_case_id	—	—	—
url	—	—	—

No examples provided.

delete_test_layer Delete Test Layer ~92

Delete a test layer from Allure TestOps. ⚠️ CAUTION: Destructive.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
layer_id	integer	yes	ID of the test layer to delete.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID.

Name	Type	Req	Description
action	—	—	Requested operation name.
id	—	—	—
layer_id	—	—	—
requires_confirmation	—	—	—
status	—	—	—

No examples provided.

delete_test_layer_schema Delete Test Layer Schema ~93

Delete a test layer schema from the project. ⚠️ CAUTION: Destructive.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID.
schema_id	integer	yes	ID of the test layer schema to delete.

Name	Type	Req	Description
action	—	—	Requested operation name.
id	—	—	—
requires_confirmation	—	—	—
schema_id	—	—	—
status	—	—	—

No examples provided.

delete_test_plan Delete Test Plan ~106

Delete a Test Plan. ⚠️ CAUTION: Destructive. Permanently removes the Test Plan from Allure TestOps. The operation is idempotent: if the plan does not exist, it returns success.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
output_format	—	—	Output format: 'json' (default) or 'plain'.
plan_id	integer	yes	ID of the test plan to delete

Name	Type	Req	Description
action	—	—	Requested operation name.
plan_id	—	—	—
requires_confirmation	—	—	—
status	—	—	—

No examples provided.

delete_test_suite Delete Test Suite ~119

Delete a test suite node from hierarchy. ⚠️ CAUTION: Destructive. This operation removes a hierarchy suite/group node. Allure TestOps handles nested entities according to its API behavior for tree groups.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with deletion. Safety measure.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional Allure TestOps project ID override.
suite_id	integer	yes	Suite/group node ID to delete from hierarchy.

Name	Type	Req	Description
action	—	—	Requested operation name.
requires_confirmation	—	—	—
status	—	—	—
suite_id	—	—	—

No examples provided.

delete_unused_custom_fields Delete Unused Custom Fields ~71

Delete custom fields that are unused by any test case in the current project.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional Allure TestOps project ID override.

Name	Type	Req	Description
action	—	—	Requested operation name.
deleted_count	—	—	—
requires_confirmation	—	—	—

No examples provided.

generate_test_code Generate Test Code ~225

Generate a current, framework-specific test snippet from a TestOps test case. Both target selections are required. The tool validates verified TestOps language/framework compatibility locally and synchronizes only requested test-case metadata before generation.

Input Output Examples

Name	Type	Req	Description
framework	string	yes	Required framework compatible with language. TypeScript choices: CodeceptJS, Cucumber, Jasmine, Jest, Mocha, Playwright, Vitest, WebdriverIO, ZeroStep. Compatibility is language-specific.
language	string	yes	Required target language. Choose Java, Python, TypeScript, JavaScript, Kotlin, PHP, or .NET. Backward-compatible aliases: java, python, ts, js, and dotnet.
metadata	—	—	Optional metadata to synchronize: Name, Tags, Custom fields, Members, Issues, Scenario. Omit for Name, Tags, Custom fields, Scenario; use [] to disable all.
output_format	—	—	Output format: 'json' (default) or 'plain'.
test_case_id	integer	yes	ID of the TestOps test case to generate code for.

Name	Type	Req	Description
code	—	—	Generated source-code snippet.
framework	—	—	Requested target testing framework.
language	—	—	Requested target programming language.
metadata	—	—	Canonical test-case metadata selections included in generated code.
test_case_id	—	—	—

No examples provided.

get_custom_fields Get Custom Fields ~130

Get available custom fields and their allowed values for the project. Use this tool to discover what custom fields are available (e.g., 'Layer', 'Priority') and what values are valid for them (e.g., 'UI', 'High'). This is essential before creating or updating test cases to ensure you use valid field names and values.

Input Output Examples

Name	Type	Req	Description
name	—	—	Optional case-insensitive name filter to search for specific custom fields.
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID to fetch custom fields from.

Name	Type	Req	Description
filter_name	—	—	—
items	—	—	Entity-specific collection entries.
total	—	—	—

No examples provided.

get_defect Get Defect ~49

Retrieve detailed information about a specific defect.

Input Output Examples

Name	Type	Req	Description
defect_id	integer	yes	ID of the defect to retrieve
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
closed	—	—	—
description	—	—	—
id	—	—	—
name	—	—	—
status	—	—	—
url	—	—	—

No examples provided.

get_launch Get Launch ~60

Retrieve a specific launch and summarize its details.

Input Output Examples

Name	Type	Req	Description
launch_id	integer	yes	Launch ID (required).
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.

Name	Type	Req	Description
autoclose	—	—	—
closed	—	—	—
created_by	—	—	—
created_date	—	—	—
environment	—	—	—
external	—	—	—
id	—	—	—
issues	—	—	—
jobs	—	—	—
known_defects_count	—	—	—
last_modified_by	—	—	—
last_modified_date	—	—	—
links	—	—	—
manual_execution_guidance	—	—	—
name	—	—	—
new_defects_count	—	—	—
project_id	—	—	—
statistic	—	—	—
tags	—	—	—
url	—	—	—

No examples provided.

get_project Get Project ~102

Retrieve one project by name or list accessible projects. Name matching is case-insensitive. An exact match is preferred; an unambiguous partial match is accepted. Omit ``name`` to discover the available project IDs and names before making project-scoped calls.

Input Output Examples

Name	Type	Req	Description
name	—	—	Project name to resolve. Omit it to list all projects available to the authenticated user.
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
abbr	—	—	Project abbreviation.
description	—	—	—
id	—	—	—
is_public	—	—	Whether the project is publicly visible.
items	—	—	Entity-specific collection entries.
name	—	—	—
total	—	—	—

No examples provided.

get_test_case_custom_fields Get Test Case Custom Fields ~72

Retrieve custom field values for a specific test case.

Input Output Examples

Name	Type	Req	Description
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID.
test_case_id	integer	yes	The ID of the test case to retrieve custom fields for

Name	Type	Req	Description
custom_fields	—	—	Custom-field values as named entries or a value map.
test_case_id	—	—	—

No examples provided.

get_test_case_details Get Test Case Details ~105

Get complete details of a specific test case. Retrieves all information about a test case including its steps, tags, custom fields, and attachments. Use this before updating a test case to understand its current state.

Input Output Examples

Name	Type	Req	Description
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Allure TestOps project ID to list test cases from.
test_case_id	integer	yes	ID of the test case to retrieve.

Name	Type	Req	Description
attachments	—	—	—
custom_fields	—	—	—
description	—	—	—
id	—	—	—
name	—	—	—
precondition	—	—	—
status	—	—	—
steps	—	—	—
tags	—	—	—
url	—	—	—

No examples provided.

link_defect_to_test_case Link Defect To Test Case ~168

Link a defect to a test case through a shared issue mapping. This operation ensures defect governance and test coverage are connected: the issue is linked to the defect and to the specified test case.

Input Output Examples

Name	Type	Req	Description
defect_id	integer	yes	ID of the defect to link
integration_id	—	—	Optional integration ID for issue mapping. Mutually exclusive with integration_name.
integration_name	—	—	Optional integration name for issue mapping. Mutually exclusive with integration_id.
issue_key	—	—	Issue key to use for linking (for example, PROJ-123). If omitted, the defect's existing issue mapping is reused.
output_format	—	—	Output format: 'json' (default) or 'plain'.
test_case_id	integer	yes	ID of the test case to link

Name	Type	Req	Description
already_linked	—	—	—
defect_id	—	—	—
defect_url	—	—	—
integration_id	—	—	—
issue_key	—	—	—
test_case_id	—	—	—
test_case_url	—	—	—

No examples provided.

link_shared_step Link Shared Step ~185

Link a shared step to a test case. ⚠️ CAUTION: Destructive. Adds a reference to the shared step in the test case's step list. The shared step's actions will expand at execution time.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	Must be set to True to proceed with linking. Safety measure.
output_format	—	—	Output format: 'json' (default) or 'plain'.
position	—	—	Where to insert the shared step (0-indexed, optional). 0 = Insert at beginning None = Append to end (default) N = Insert after step N (so it becomes the (N+1)th step)
project_id	—	—	Optional override for the default Project ID.
shared_step_id	integer	yes	The ID of shared step to link.
test_case_id	integer	yes	The ID of test case to modify.

Name	Type	Req	Description
action	—	—	Requested operation name.
error	—	—	—
requires_confirmation	—	—	—
shared_step_id	—	—	—
shared_step_url	—	—	—
status	—	—	—
steps	—	—	Serialized scenario steps.
test_case_id	—	—	—
test_case_url	—	—	—

No examples provided.

list_custom_field_values List Custom Field Values ~165

List available values for a custom field.

Input Output Examples

Name	Type	Req	Description
custom_field_id	—	—	Project-scoped custom field ID to list values for.
custom_field_name	—	—	Custom field name to resolve when custom_field_id is not provided.
output_format	—	—	Output format: 'json' (default) or 'plain'.
page	—	—	Zero-based page index.
project_id	—	—	Optional override for the default Project ID.
query	—	—	Optional search query to filter values.
size	—	—	Number of items per page.
sort	—	—	Optional sort criteria, e.g. ['name,asc', 'id,desc']
test_case_search	—	—	Optional test case search filter to match values in test cases.
var_global	—	—	Optional filter for global values.

Name	Type	Req	Description
items	—	—	Entity-specific collection entries.
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

list_defect_matchers List Defect Matchers ~55

List all matchers (automation rules) for a given defect.

Input Output Examples

Name	Type	Req	Description
defect_id	integer	yes	ID of the parent defect
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
defect_id	—	—	—
items	—	—	—
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

list_defect_test_cases List Defect Test Cases ~81

List test cases currently linked to a defect.

Input Output Examples

Name	Type	Req	Description
defect_id	integer	yes	ID of the defect whose linked test cases should be listed
output_format	—	—	Output format: 'json' (default) or 'plain'.
page	integer	—	Zero-based page index
size	integer	—	Page size (1..100)

Name	Type	Req	Description
defect_id	—	—	—
defect_url	—	—	—
items	—	—	Entity-specific collection entries.
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

list_defects List Defects ~35

List all defects in the current project.

Input Output Examples

Name	Type	Req	Description
output_format	—	—	Output format: 'json' (default) or 'plain'.

Name	Type	Req	Description
items	—	—	Entity-specific collection entries.
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

list_integrations List Integrations ~99

List available integrations (issue trackers) in Allure TestOps. Use this tool to discover which integrations (Jira, GitHub, etc.) are configured and available for linking issues to test cases.

Input Output Examples

Name	Type	Req	Description
output_format	—	—	Output format: 'json' (default) or 'plain'.
project_id	—	—	Optional override for the default Project ID. When provided (or from environment default), integrations are filtered to those available for that project.

Name	Type	Req	Description
items	—	—	Entity-specific collection entries.
total	—	—	—

No examples provided.

list_launch_test_results List Launch Test Results ~184

List test results inside a launch, including manual execution metadata.

Input Output Examples

Name	Type	Req	Description
failed_only	boolean	—	When true, return only failed or broken results. Filtering is handled for you.
filter_id	—	—	Optional saved filter ID from TestOps.
launch_id	integer	yes	Launch ID (required).
manual_only	boolean	—	When true, return only manual results. Filtering is handled for you.
output_format	—	—	Output format: 'json' (default) or 'plain'.
page	integer	—	Zero-based page index after optional filtering.
project_id	—	—	Optional override for the default Project ID.
search	—	—	Optional result-name search term.
size	integer	—	Number of results per page (max 100).
sort	—	—	Optional sort directives such as ['name,ASC'] or ['createdDate,DESC'].

Name	Type	Req	Description
failed_only	—	—	—
items	—	—	Entity-specific collection entries.
launch_id	—	—	—
manual_only	—	—	—
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

list_launches List Launches ~115

List launches in a project.

Input Output Examples

Name	Type	Req	Description
filter_id	—	—	Optional filter ID.
output_format	—	—	Output format: 'json' (default) or 'plain'.
page	integer	—	Zero-based page index.
project_id	—	—	Optional override for the default Project ID.
search	—	—	Optional name search.
size	integer	—	Number of results per page (max 100).
sort	—	—	Sorting criteria in the format: property(,asc\|desc). Example: ['createdDate,DESC']

Name	Type	Req	Description
items	—	—	—
page	—	—	—
size	—	—	—
total	—	—	—
total_pages	—	—	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

30 Jul 3 Aug