Lucius MCP
MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.
Connector by ivanostanin · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Claude Desktop, Cursor, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install connector/ivanostanin-lucius-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 22 read · 31 write · 15 delete · 1 not yet classified
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- None found
- Runs as
- Python package
Tools by what they do 69
Read from the source code; the running server may list different tools.
Read 22 · Look things up without changing anything.
get_custom_fieldsget_defectget_launchget_projectget_test_case_custom_fieldsget_test_case_detailsget_test_resultget_test_suite_contentslist_custom_field_valueslist_defect_matcherslist_defect_test_caseslist_defects
Show 10 more tools
list_integrationslist_launch_test_resultslist_launcheslist_shared_stepslist_test_caseslist_test_layer_schemaslist_test_layerslist_test_planslist_test_suitessearch_test_cases
Write 31 · Create, change, send or run things.
add_test_result_attachmentassign_test_cases_to_suiteattach_file_to_launchclose_launchcreate_custom_field_valuecreate_defectcreate_defect_matchercreate_launchcreate_shared_stepcreate_test_casecreate_test_layercreate_test_layer_schema
Show 19 more tools
create_test_plancreate_test_suitelink_shared_stepmanage_test_plan_contentprepare_attachment_downloadreopen_launchrerun_test_results_manuallyrun_test_planstart_manual_test_sessionsubmit_manual_test_resultsupdate_custom_field_valueupdate_defectupdate_defect_matcherupdate_shared_stepupdate_test_caseupdate_test_layerupdate_test_layer_schemaupdate_test_planupload_test_results
Delete 15 · Delete, drop, revoke or wipe things.
delete_archived_shared_stepsdelete_archived_test_casesdelete_custom_field_valuedelete_defectdelete_defect_matcherdelete_launchdelete_shared_stepdelete_test_casedelete_test_layerdelete_test_layer_schemadelete_test_plandelete_test_suite
Show 3 more tools
delete_unused_custom_fieldsunlink_issue_from_test_caseunlink_shared_step
Not yet classified 1 · We could not tell from the name and description.
link_defect_to_test_case
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
ALLURE_API_TOKEN
Other settings (environment variables or headers).
ALLURE_ENDPOINTALLURE_PROJECT_ID
Network hosts it talks to 9
app.testops.cloud· found in codeastral.sh· found in codedemo.testops.cloud· found in codedocs.qameta.io· found in codeexample.testops.cloud· found in codegithub.com· found in install command, codeopenapi-generator.tech· found in codeqameta.io· found in codestats.ostanin.me· found in code
Files it touches
/etc/localtime- Your home directory (~)
Tools (69)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
add_test_result_attachmentUpload one attachment to a manual test result.
assign_test_cases_to_suiteAssign test cases to a suite path in hierarchy. ⚠️ CAUTION: Destructive. Reassigning test cases changes their hierarchy location. Args: suite_id: Target suite/group node ID. test_case_ids: List of test case IDs to assign. project_id: Optional project override. If omitted, use default project from environment. tree_id: Optional hierarchy tree ID. If omitted, the default project tree is used. output_format: Output format: 'json' (default) or 'plain'. Returns: Success message with the number of assigned test cases.
attach_file_to_launchAttach one file to an existing launch through a secure push or pull transfer. Push is available only from a persistent HTTP MCP server with an externally reachable HTTPS URL. It returns a short-lived one-use raw upload URL; POST bytes with exactly the returned content type and no TestOps bearer token. Pull reads a regular file below the deployment's configured import root. Args: launch_id: Existing launch ID that will receive the file. name: Safe display filename for the native launch attachment. transfer_mode: ``push`` for a caller upload URL, or ``pull`` for server-side import …
close_launchClose a launch and return updated launch details.
create_custom_field_valueCreate a new custom field value option. Args: name: Name for the new custom field value. 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. project_id: Optional override for the default Project ID. output_format: Output format: 'json' (default) or 'plain'.
create_defectCreate a new defect. Args: name: Defect name (required). description: Defect description (optional). Returns: Created DefectOverviewDto. Raises: AllureValidationError: If name is empty.
create_defect_matcherCreate a defect matcher (automation rule). Args: defect_id: Parent defect for this matcher. name: Human-readable matcher name. message_regex: Regex to match against error messages. trace_regex: Regex to match against stack traces. Returns: Created DefectMatcherDto. Raises: AllureValidationError: If neither message_regex nor trace_regex is provided.
create_launchCreate a new launch. Args: name: Launch name. autoclose: Whether the launch auto-closes. external: Whether the launch is external. issues: Optional list of issue dictionaries. links: Optional list of external link dictionaries. tags: Optional list of launch tags. Returns: The created launch.
create_shared_stepCreate a new shared step with optional steps. Args: name: Name of the shared step. steps: Optional list of steps. Returns: The created SharedStepDto.
create_test_caseCreate a new test case in Allure TestOps. Args: name: The name of the test case. description: A markdown description of the test case. 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. 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', …
create_test_layerCreate a new test layer in Allure TestOps. Test layers define taxonomy for categorizing test cases. Common examples include 'Unit', 'Integration', 'E2E', 'UI', 'API', etc. Args: name: Name of the test layer project_id: Optional project ID override output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message with the created layer's ID and name
create_test_layer_schemaCreate 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. Args: key: Schema key (typically a custom field name) test_layer_id: ID of the test layer to link project_id: Project ID output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message with the created schema's details
create_test_planCreate 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). Args: name: The display name for the new Test Plan. test_case_ids: Optional list of numeric Test Case IDs to include initially. aql_filter: Optional AQL query string to dynamically select test cases (e.g., 'tag in ["smoke", "r…
create_test_suiteCreate a new test suite node in the hierarchy tree. Args: name: Suite name to create. project_id: Optional project override. If omitted, use default project from environment. tree_id: Optional hierarchy tree ID. If omitted, the default project tree is used. parent_suite_id: Optional parent suite ID. Provide to create a nested suite. output_format: Output format: 'json' (default) or 'plain'. Returns: Success message containing created suite ID and name.
delete_archived_shared_stepsPermanently delete all archived shared steps in the current project. Args: confirm: Must be set to True to proceed. project_id: Optional Allure TestOps project ID override. output_format: Output format: 'json' (default) or 'plain'.
Show 54 more tools
delete_archived_test_casesPermanently delete all archived/deleted test cases in the current project. Args: confirm: Must be set to True to proceed. project_id: Optional Allure TestOps project ID override. output_format: Output format: 'json' (default) or 'plain'.
delete_custom_field_valueDelete a custom field value. ⚠️ CAUTION: Destructive. Args: cfv_id: Custom field value ID to delete. 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. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with deletion. This is a safety measure to prevent accidental deletions. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message.
delete_defectDelete a defect. Args: defect_id: The defect to delete. Raises: AllureNotFoundError: If the defect does not exist.
delete_defect_matcherDelete a defect matcher. Args: matcher_id: The matcher to delete. Raises: AllureNotFoundError: If the matcher does not exist.
delete_launchDelete a launch by ID with idempotent behavior.
delete_shared_stepDelete (archive) a shared step with idempotent behavior. Args: step_id: The shared step ID to delete. Returns: The archive outcome, including whether an archived entity was confirmed to exist for safe URL rendering. Raises: AllureAPIError: If the API request fails (other than 404). Note: This operation is idempotent following Story 1.5 pattern. A 404 is reported as ``not_found`` so callers do not link to a deleted entity.
delete_test_caseArchive 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. Args: test_case_id: The Allure test case ID to archive. Found in the URL: /testcase/12345 -> test_case_id=12345 confirm: Must be set to True to proceed with deletion. This is a safety measure to prevent accidental deletions. project_id: Optional Allure TestOps project ID override.…
delete_test_layerDelete a test layer from Allure TestOps. ⚠️ CAUTION: Destructive. Args: layer_id: ID of the test layer to delete. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with deletion. This is a safety measure to prevent accidental deletions. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message.
delete_test_layer_schemaDelete a test layer schema from the project. ⚠️ CAUTION: Destructive. Args: schema_id: ID of the schema to delete. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with deletion. This is a safety measure to prevent accidental deletions. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message.
delete_test_planDelete 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. Args: plan_id: The numeric ID of the Test Plan to delete. confirm: Must be set to True to proceed with deletion. output_format: Output format: 'json' (default) or 'plain'. Returns: A formatted success message or a warning if confirmation is missing.
delete_test_suiteDelete 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. Args: suite_id: Existing suite (tree node) ID to delete. tree_id: Optional hierarchy tree containing the suite. confirm: Must be set to True to proceed. This safety flag prevents accidental destructive actions. project_id: Optional Allure TestOps project override. output_format: Output format: 'json' (default) or 'plain'. Returns: A confirmation or safety wa…
delete_unused_custom_fieldsDelete custom fields that are unused by any test case in the current project. Args: confirm: Must be set to True to proceed. project_id: Optional Allure TestOps project ID override. output_format: Output format: 'json' (default) or 'plain'.
get_custom_fieldsGet 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. Args: name: Optional name filter to find a specific field (case-insensitive). project_id: Optional project ID override. output_format: Output format: 'json' (default) or 'plain'. Returns: A list of custom fields with their required status and allowed values.
get_defectGet defect details by ID. Args: defect_id: ID of the defect. Returns: DefectOverviewDto details. Raises: AllureNotFoundError: If defect not found.
get_launchRetrieve a specific launch by its ID. Args: launch_id: The unique ID of the launch. Returns: The launch data.
get_projectRetrieve 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. Args: name: Exact or unique partial project name. Omit to list projects. output_format: Output format: 'json' (default) or 'plain'. Returns: A project record with its ID and details, or a concise list of project IDs and names when no name is supplied.
get_test_case_custom_fieldsRetrieve custom field values for a specific test case. Args: test_case_id: The ID of the test case. project_id: Optional project ID override. output_format: Output format: 'json' (default) or 'plain'. Returns: A dictionary where keys are custom field names and values are either a single string value or a list of string values.
get_test_case_detailsGet complete details of a specific test case. Retrieves all information about a test case including its steps, tags, custom fields, and attachments. For each attachment, call prepare_attachment_download with its attachment_id, attachment_kind, and test_case_id, then HTTP GET the returned Lucius URL. Use this before updating a test case to understand its current state. Args: test_case_id: The unique ID of the test case to retrieve. project_id: Optional override for the default Project ID. output_format: Output format: 'json' (default) or 'plain'. Returns: Formatted test case …
get_test_resultRetrieve one complete TestOps result without recursively reading related results. Attachment references identify their verified owner. Call prepare_attachment_download with an attachment's attachment_id, attachment_kind, and owner context, then HTTP GET the returned Lucius URL before it expires. Args: test_result_id: Exact TestOps result ID matching ``/api/testresult/{id}``. Ignore a ``treeId`` URL query parameter. project_id: Optional project override. output_format: Structured JSON (default) or plain agent-readable detail. Returns: Curated result detail, typed atta…
get_test_suite_contentsGet test cases directly assigned to one test suite. This is a targeted hierarchy read. It does not enumerate unrelated suites or recursively traverse the project tree. Args: suite_id: Existing suite/group node ID to inspect. project_id: Optional Allure TestOps project override. tree_id: Optional hierarchy tree containing the suite. expected_suite_name: Optional exact name of the target suite. Supply it when available to avoid reading a missing node after an asynchronous deletion. output_format: Output format: 'json' (default) or 'plain'. Returns: The suite ID…
link_defect_to_test_caseLink defect and test case through a shared issue mapping. Args: defect_id: Defect ID. test_case_id: Test case ID. issue_key: Issue key to map (for example, PROJ-123). If omitted, an existing issue mapping from the defect is reused. integration_id: Optional explicit integration ID. integration_name: Optional explicit integration name. Returns: DefectTestCaseLinkResult with mapping details and idempotency state. Raises: AllureValidationError: For invalid input or missing issue mapping. AllureNotFoundError: If defect/test case is not found.
link_shared_stepLink 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. Args: test_case_id: The ID of test case to modify. Found in URL: /testcase/12345 shared_step_id: The ID of shared step to link. Found via list_shared_steps or in Allure UI. 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) pro…
list_custom_field_valuesList available values for a custom field. Args: 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. query: Optional search query to filter values. var_global: Optional filter for global values. test_case_search: Optional test case search filter to match values in test cases. page: Zero-based page index. size: Number of items per page. sort: Optional sort criteria, e.g. ["name,asc", "id,desc"]. project_id: Optional override for the default Project ID. ou…
list_defect_matchersList all matchers for a given defect. Args: defect_id: The parent defect ID. Returns: List of DefectMatcherDto objects.
list_defect_test_casesList test cases linked to a defect. Args: defect_id: Defect ID. page: Zero-based page index. size: Page size (1..100). Returns: DefectTestCaseListResult with pagination metadata.
list_defectsList all defects in the configured project. Returns: List of DefectCountRowDto objects.
list_integrationsList 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. Args: project_id: Optional override for the default Project ID. When provided (or from environment default), integrations are filtered to those available for that project. output_format: Output format: 'json' (default) or 'plain'. Returns: A formatted list of available integrations with their IDs and names. If no integrations are configured, returns an informative messa…
list_launch_test_resultsList launch test results with optional manual/status filtering.
list_launchesList launches for the configured project. Args: page: Zero-based page index. size: Page size. search: Optional name search. filter_id: Optional filter ID. sort: Optional sort criteria. Returns: LaunchListResult with items and pagination metadata.
list_shared_stepsList shared steps for a project. Args: page: Page number (0-based). size: Page size. search: Optional search query. archived: Optional archived status filter. Returns: List of SharedStepDto.
list_test_casesList all test cases in a project. Returns a paginated list of test cases with their IDs, names, and tags. Use this to review existing test documentation in a project. Args: page: Page number for pagination (0-indexed). Default: 0. size: Number of results per page (max 100). Default: 20. name_filter: Optional filter to search by name or description. tags: Optional list of tag names to filter by (exact match). status: Optional test case status name to filter by (exact match). project_id: Optional override for the default Project ID. output_format: Output format: 'js…
list_test_layer_schemasList test layer schemas for a project. Test layer schemas map custom field keys to test layers within a project. They determine which test layer is assigned when a specific custom field value is used. Args: project_id: Optional project ID override page: Page number (0-based) size: Page size (max 100) output_format: Output format: 'json' (default) or 'plain'. Returns: List of test layer schemas with their IDs, keys, and linked test layers
list_test_layersList test layers to discover available test layer taxonomy. Test layers define the taxonomy for categorizing test cases (e.g., Unit, Integration, E2E). Use this to find layer IDs and names before creating or updating test cases. Args: page: Page number (0-based) size: Page size (max 100) output_format: Output format: 'json' (default) or 'plain'. Returns: List of test layers with their IDs and names
list_test_plansList Test Plans for the current project. Retrieves a paginated list of Test Plans, showing their IDs, names, and the number of test cases they contain. Args: page: The page number to retrieve (0-based index). Defaults to 0. size: The number of items per page. Defaults to 100. output_format: Output format: 'json' (default) or 'plain'. Returns: A formatted string listing the Test Plans found, or a message indicating no plans were found.
list_test_suitesList hierarchy suites for a project tree. Args: project_id: Optional project override. If omitted, use default project from environment. tree_id: Optional hierarchy tree ID. If omitted, the default project tree is used. include_empty: Whether to include suites without nested child suites. output_format: Output format: 'json' (default) or 'plain'. Returns: Hierarchical text output with tree info and suite nodes.
manage_test_plan_contentModify the content (Test Cases) of an existing Test Plan. Allows adding or removing specific Test Cases by ID, or updating the underlying AQL filter query. Args: plan_id: The numeric ID of the Test Plan to modify. add_test_case_ids: List of Test Case IDs to add to the plan. remove_test_case_ids: List of Test Case IDs to remove from the plan. update_aql_filter: New AQL query string to replace the existing one. Use this to change the dynamic criteria for test case selection. output_format: Output format: 'json' (default) or 'plain'. Returns: A success message c…
prepare_attachment_downloadPrepare one verified attachment download, then HTTP GET its returned Lucius URL. Call this after get_test_result or get_test_case_details provides an attachment ID, kind, and owner context. The returned download URL is one-time and short-lived: HTTP GET it before expires_at without an Allure bearer token. Prepare again if the URL expires or was already retrieved. Args: attachment_id: Attachment ID discovered from a readable result or test case. attachment_kind: Verified attachment kind: test_result, fixture_result, or test_case. test_result_id: Required owner ID for test_result o…
reopen_launchReopen a launch and return updated launch details.
rerun_test_results_manuallySchedule manual reruns for selected launch test results.
run_test_planStart a launch from an existing Test Plan. Runs the selected test plan by its ID and returns the created launch as a compact mutation summary enriched with the source plan context. Starting a launch is reversible: use delete_launch to remove it when unwanted. Args: plan_id: The numeric ID of the Test Plan to run. launch_name: Name for the launch created from the plan (1-255 characters). issues: Optional list of issue dictionaries. links: Optional list of external link dictionaries. tags: Optional list of launch tags. output_format: Output format: 'json' (default) or '…
search_test_casesSearch for test cases by name, tag, or AQL query. Find test cases matching your search criteria. Supports simple name/tag search or advanced AQL (Allure Query Language) for complex filtering. Simple Query Syntax (use 'query' parameter): - Plain text: Searches in test case names (case-insensitive) - tag:value: Filters by exact tag match - Combined: "login tag:smoke" finds test cases with "login" in name AND "smoke" tag Important: see https://docs.qameta.io/allure-testops/advanced/aql/ for the full AQL syntax reference. AQL Syntax (use 'aql' parameter): - Operators: and, or, not - Precedence:…
start_manual_test_sessionStart a manual test session for a launch.
submit_manual_test_resultsSubmit manual execution payloads to existing or explicit launch contexts. When ``results[*].result_id`` is provided, the existing launch result is resolved in place via the test-result run controller. When explicit ``launch_id`` and ``test_case_id`` are provided without ``result_id``, the legacy create-new-result flow is used as a fallback.
unlink_issue_from_test_caseUnlink an issue from a test case. Args: test_case_id: ID of the target test case. issue_id: Issue key or Allure internal issue-link ID. Returns: True if the issue was already absent; otherwise False. Raises: AllureValidationError: If the supplied IDs are invalid. TestCaseNotFoundError: If the test case does not exist.
unlink_shared_stepRemove a shared step reference from a test case. ⚠️ CAUTION: Destructive. Removes the link to the shared step. The test case will no longer include those steps at execution time. Args: test_case_id: The test case to modify. shared_step_id: The shared step to unlink. project_id: Optional override for the default Project ID. confirm: Must be set to True to proceed with unlinking. This is a safety measure to prevent accidental unlinking. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation with updated step list. Note: This only remo…
update_custom_field_valueUpdate an existing custom field value. ⚠️ CAUTION: Destructive. Args: cfv_id: Custom field value ID to update. name: New name for the custom field value. 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. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with update. This is a safety measure to prevent accidental updates. output_format: Output format: 'json' (default) or 'plain'. Returns:…
update_defectUpdate a defect. Args: defect_id: Defect to update. name: New name (optional). description: New description (optional). closed: New status (True for closed, False for open). Returns: Updated DefectOverviewDto. Raises: AllureNotFoundError: If the defect does not exist. AllureValidationError: If no fields are provided.
update_defect_matcherUpdate a defect matcher. Args: matcher_id: The matcher to update. name: New name (optional). message_regex: New message regex (optional). trace_regex: New trace regex (optional). Returns: Updated DefectMatcherDto. Raises: AllureNotFoundError: If the matcher does not exist. AllureValidationError: If no fields are provided.
update_shared_stepUpdate an existing shared step with idempotency support. Only provided fields are updated. Repeated calls with same data are idempotent. Args: step_id: The shared step ID to update. name: New name for the shared step (optional). description: New description (optional). Returns: Tuple of (updated_shared_step, changed) where changed is True if update was applied. Raises: AllureNotFoundError: If shared step doesn't exist. AllureValidationError: If validation fails. AllureAPIError: If the server returns an error.
update_test_caseUpdate an existing test case in Allure TestOps. ⚠️ CAUTION: Destructive. Performs a partial update: only supplied fields are sent to the API. When provided, ``steps`` replace all existing steps, and ``attachments`` replace all existing global attachments. Omit a field to preserve its current value. Args: test_case_id: The ID of the test case to update. name: New name for the test case. description: New description for the test case. precondition: New precondition text. steps: New list of steps. Each step is a dict with ``action``, ``expected``, and optional ``atta…
update_test_layerUpdate an existing test layer's name. ⚠️ CAUTION: Destructive. Args: layer_id: ID of the test layer to update. name: New name for the test layer. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with update. This is a safety measure to prevent accidental updates. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message indicating whether changes were made.
update_test_layer_schemaUpdate an existing test layer schema. ⚠️ CAUTION: Destructive. Args: schema_id: ID of the schema to update. test_layer_id: Optional new test layer ID to link to. key: Optional new schema key. project_id: Optional Allure TestOps project ID override. confirm: Must be set to True to proceed with update. This is a safety measure to prevent accidental updates. output_format: Output format: 'json' (default) or 'plain'. Returns: Confirmation message indicating whether changes were made.
update_test_planUpdate the metadata of an existing Test Plan. Currently, supports updating the name of the plan. Args: plan_id: The numeric ID of the Test Plan to update. name: The new name for the Test Plan. output_format: Output format: 'json' (default) or 'plain'. Returns: A success message confirming the update with the Plan ID and new Name.
upload_test_resultsUpload external test results to an existing launch. Args: launch_id: Launch ID that receives all submitted results. results: Objects with required `test_case_id` and `status`; timestamps, duration, and a message are optional. project_id: Optional override for the default Project ID. output_format: Output format: 'json' (default) or 'plain'. Returns: A concise upload summary, including any rejected result indexes.
Signals
- Stars
- 7
- Forks
- 3
- Open issues
- 0
- Weekly downloads
- 336
- Last commit
- Oct 21, 2026 (7 days ago)
- Last release
- Oct 21, 2026 (7 days ago)
- Last package publish
- Oct 21, 2026 (7 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.ivanostanin/lucius-mcp- Version
- 0.16.6
- Auth
- API key
- Packages
- pypi lucius-mcpoci
ghcr.io/ivanostanin/lucius-mcp:0.16.6mcpb https://github.com/ivanostanin/lucius-mcp/releases/download/v0.16.6/lucius-mcp-0.16.6-uv.mcpbmcpb https://github.com/ivanostanin/lucius-mcp/releases/download/v0.16.6/lucius-mcp-0.16.6-python.mcpb - License
- Apache-2.0
- Repository
- github.com/ivanostanin/lucius-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Cite this page
Lucius MCP. Agent Mart. https://agentmart.dev/connectors/ivanostanin-lucius-mcp (last updated 2026-10-24)