lucius-mcp 0.1.0__tar.gz → 0.2.2__tar.gz

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/.github/workflows/release.yml

@@ -48,7 +48,7 @@ jobs:
       artifact-name: mcpb-bundle-${{ needs.validate-version.outputs.version }}
 
   docker-build:
-    needs: python-quality
+    needs: [python-quality, validate-version]
     permissions:
       contents: read
       packages: write
@@ -69,28 +69,46 @@ jobs:
     permissions:
       contents: write
     steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
       - name: Download artifacts
         uses: actions/download-artifact@v4
         with:
           name: mcpb-bundle-${{ needs.validate-version.outputs.version }}
           path: dist/
 
+      - name: Get Changelog Entry
+        id: changelog_reader
+        uses: mindsers/changelog-reader-action@v2
+        with:
+          version: ${{ github.ref_name }}
+          path: ./CHANGELOG.md
+
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v1
         with:
+          body: ${{ steps.changelog_reader.outputs.changes }}
           files: dist/*.mcpb
-          generate_release_notes: true
-          draft: false
-          prerelease: false
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      
-      # Optional: Publish to PyPI
-      # Uncomment if you want to publish to PyPI
-      # - name: Build Python package
-      #   run: uv build
-      # 
-      # - name: Publish to PyPI
-      #   uses: pypa/gh-action-pypi-publish@release/v1
-      #   with:
-      #     password: ${{ secrets.PYPI_API_TOKEN }}
+
+  pypi-publish:
+    needs: python-quality
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python Environment
+        uses: ./.github/actions/python-setup
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

lucius_mcp-0.2.2/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-format
+        name: ruff-format
+        entry: uv run ruff format .
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: ruff-check
+        name: ruff-check
+        entry: uv run ruff check --fix .
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: mypy
+        name: mypy
+        entry: uv run mypy src
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: pytest
+        name: pytest
+        entry: uv run pytest tests/unit tests/integration tests/packaging
+        language: system
+        types: [python]
+        pass_filenames: false
+        stages: [pre-push]

lucius_mcp-0.2.2/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+## [v0.2.2] - 2026-01-30
+
+### Fixed
+- Docker image build.
+
+## [v0.2.1] - 2026-01-30
+
+### Fixed
+- Deployment workflows: release description now includes the changelog, and PyPI publishing steps are corrected.
+
+## [v0.2.0]
+
+### Added
+- `get_custom_fields` tool to fetch custom fields and their allowed values (Story 3.6).
+- New example payloads for the `create_test_case` tool to guide usage.
+- Client generation for project and custom field controllers.
+- Initial `CHANGELOG.md` and `LICENSE` documentation.
+
+### Changed
+- Default run mode changed to `stdio` for easier integration with MCP clients.
+- Improved guidance for `create_test_case` tool, providing extended hints when non-existing custom fields are used (Story 3.5).
+- Updated package metadata and versions.
+
+## [v0.1.0]
+
+- Initial release

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lucius-mcp
-Version: 0.1.0
+Version: 0.2.2
 Summary: Allure TestOps MCP Server
 Project-URL: Homepage, https://github.com/ivanostanin/lucius-mcp
 Project-URL: Documentation, https://github.com/ivanostanin/lucius-mcp#readme
@@ -40,6 +40,7 @@ Requires-Dist: allure-pytest>=2.15.3; extra == 'dev'
 Requires-Dist: faker>=40.1.2; extra == 'dev'
 Requires-Dist: mypy>=1.19.1; extra == 'dev'
 Requires-Dist: openapi-generator-cli>=7.19.0; extra == 'dev'
+Requires-Dist: pre-commit>=4.0.0; extra == 'dev'
 Requires-Dist: pytest-asyncio>=1.3.0; extra == 'dev'
 Requires-Dist: pytest-cov>=7.0.0; extra == 'dev'
 Requires-Dist: pytest-mock>=3.15.1; extra == 'dev'
@@ -98,6 +99,18 @@ This project uses `uv` for dependency management.
 
 ## 🏃 Usage
 
+### Add to Claude Code (MCP)
+
+1.  **Add the MCP**:
+    ```bash
+    claude mcp add testops-mcp --transport stdio \
+      --env ALLURE_ENDPOINT=https://your-testops.example \
+      --env ALLURE_PROJECT_ID=123 \
+      --env ALLURE_API_TOKEN=your_token \
+      --env MCP_MODE=stdio \
+      -- uvx --from lucius-mcp start
+    ```
+
 ### Running via Claude Desktop (One-Click Install)
 
 The easiest way to use Lucius in Claude Desktop is via the `.mcpb` bundle:
@@ -115,7 +128,7 @@ For integration with MCP clients (like Claude Code) using standard input/output.
 uv run start
 ```
 
-Or 
+Or
 
 ```bash
 MCP_MODE=stdio uv run start
@@ -267,3 +280,11 @@ uv run ruff check src/
 ```bash
 uv run mypy --strict src/
 ```
+
+## Release process
+1. Bump version in `pyproject.toml`.
+2. Run `uv sync --all-extras` to update dependencies.
+3. Write release notes in `CHANGELOG.md`.
+4. Commit changes.
+5. Create a tag with the new version.
+6. Push commits and tags.

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/README.md

@@ -47,6 +47,18 @@ This project uses `uv` for dependency management.
 
 ## 🏃 Usage
 
+### Add to Claude Code (MCP)
+
+1.  **Add the MCP**:
+    ```bash
+    claude mcp add testops-mcp --transport stdio \
+      --env ALLURE_ENDPOINT=https://your-testops.example \
+      --env ALLURE_PROJECT_ID=123 \
+      --env ALLURE_API_TOKEN=your_token \
+      --env MCP_MODE=stdio \
+      -- uvx --from lucius-mcp start
+    ```
+
 ### Running via Claude Desktop (One-Click Install)
 
 The easiest way to use Lucius in Claude Desktop is via the `.mcpb` bundle:
@@ -64,7 +76,7 @@ For integration with MCP clients (like Claude Code) using standard input/output.
 uv run start
 ```
 
-Or 
+Or
 
 ```bash
 MCP_MODE=stdio uv run start
@@ -216,3 +228,11 @@ uv run ruff check src/
 ```bash
 uv run mypy --strict src/
 ```
+
+## Release process
+1. Bump version in `pyproject.toml`.
+2. Run `uv sync --all-extras` to update dependencies.
+3. Write release notes in `CHANGELOG.md`.
+4. Commit changes.
+5. Create a tag with the new version.
+6. Push commits and tags.

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/deployment/mcpb/manifest.python.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": "0.4",
   "name": "lucius-mcp",
-  "version": "0.1.0",
+  "version": "__version__",
   "description": "Allure TestOps MCP Server",
   "author": {
     "name": "Ivan Ostanin",
@@ -81,6 +81,10 @@
     {
       "name": "delete_shared_step",
       "description": "Delete a shared step from the library."
+    },
+    {
+      "name": "get_custom_fields",
+      "description": "List all custom fields available in a project."
     }
   ],
   "user_config": {
@@ -123,4 +127,4 @@
     "allure-testops",
     "python"
   ]
-}
+}

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/deployment/mcpb/manifest.uv.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": "0.4",
   "name": "lucius-mcp",
-  "version": "0.1.0",
+  "version": "__version__",
   "description": "Allure TestOps MCP Server",
   "author": {
     "name": "Ivan Ostanin",
@@ -80,6 +80,10 @@
     {
       "name": "delete_shared_step",
       "description": "Delete a shared step from the library."
+    },
+    {
+      "name": "get_custom_fields",
+      "description": "List all custom fields available in a project."
     }
   ],
   "user_config": {
@@ -122,4 +126,4 @@
     "allure-testops",
     "uv"
   ]
-}
+}

{lucius_mcp-0.1.0 → lucius_mcp-0.2.2}/deployment/scripts/verify_mcpb_bundles.py

@@ -58,7 +58,7 @@ def verify_manifest(
             errors.append("python mcp_config.env must be an object")
     else:
         expect(mcp_config.get("command") == "uv", "uv mcp_config.command must be uv", errors)
-        expect(mcp_config.get("args") == ["run", "lucius-mcp"], "uv mcp_config.args must be [run, lucius-mcp]", errors)
+        expect(mcp_config.get("args") == ["run", "start"], "uv mcp_config.args must be [run, start]", errors)
 
 
 def verify_python_bundle_contents(names: set[str], errors: list[str]) -> None:

lucius_mcp-0.2.2/examples/create_test_case_invalid_custom_field_values.json

@@ -0,0 +1,20 @@
+{
+    "name": "Test Case with Invalid Custom Field Values",
+    "description": "This example demonstrates what happens when you provide values that are not in the allowed list for custom fields. The server will return an aggregated error listing all invalid values with their allowed options.",
+    "project_id": 166,
+    "custom_fields": {
+        "Priority": "Critical",
+        "OS": "Android",
+        "Feature": "Authentication"
+    },
+    "steps": [
+        {
+            "action": "Perform action",
+            "expected": "Expected result"
+        }
+    ],
+    "tags": [
+        "example"
+    ],
+    "_comment": "Assuming Priority allows [High, Medium, Low] and OS allows [Mac, Windows, Linux], this will fail with aggregated errors for both Priority and OS"
+}

lucius_mcp-0.2.2/examples/create_test_case_missing_custom_fields.json

@@ -0,0 +1,20 @@
+{
+    "name": "Test Case with Missing Custom Fields",
+    "description": "This example demonstrates what happens when you use custom fields that don't exist in the project. The server will return an aggregated error listing all missing fields.",
+    "project_id": 166,
+    "custom_fields": {
+        "Priority": "High",
+        "NonExistentField1": "SomeValue",
+        "NonExistentField2": "AnotherValue",
+        "ValidField": "ValidValue"
+    },
+    "steps": [
+        {
+            "action": "Perform action",
+            "expected": "Expected result"
+        }
+    ],
+    "tags": [
+        "example"
+    ]
+}

lucius_mcp-0.2.2/examples/create_test_case_mixed_custom_field_errors.json

@@ -0,0 +1,21 @@
+{
+    "name": "Test Case with Mixed Custom Field Errors",
+    "description": "This example demonstrates the aggregated error response when both missing fields and invalid values are present. The server will list all issues in a single response.",
+    "project_id": 166,
+    "custom_fields": {
+        "Priority": "Critical",
+        "NonExistentField": "SomeValue",
+        "OS": "Android",
+        "ValidField": "ValidValue"
+    },
+    "steps": [
+        {
+            "action": "Perform action",
+            "expected": "Expected result"
+        }
+    ],
+    "tags": [
+        "example"
+    ],
+    "_comment": "This will return an error listing: (1) missing fields: NonExistentField, and (2) invalid values: Priority='Critical', OS='Android' with their allowed options"
+}

lucius_mcp-0.2.2/examples/create_test_case_with_valid_custom_fields.json

@@ -0,0 +1,28 @@
+{
+    "name": "User Registration Flow with Valid Custom Fields",
+    "description": "This test case demonstrates using custom fields with valid values from the allowed options",
+    "project_id": 166,
+    "custom_fields": {
+        "Priority": "High",
+        "OS": "Mac",
+        "Feature": "Authentication"
+    },
+    "steps": [
+        {
+            "action": "Navigate to registration page",
+            "expected": "Registration form is displayed"
+        },
+        {
+            "action": "Fill in user details",
+            "expected": "Form accepts the input"
+        },
+        {
+            "action": "Submit registration",
+            "expected": "User account is created successfully"
+        }
+    ],
+    "tags": [
+        "registration",
+        "smoke"
+    ]
+}

lucius_mcp-0.2.2/examples/get_custom_fields_basic.json

@@ -0,0 +1,3 @@
+{
+    "project_id": 166
+}

lucius_mcp-0.2.2/examples/get_custom_fields_filtered.json

@@ -0,0 +1,3 @@
+{
+    "name": "Layer"
+}

lucius_mcp-0.2.2/examples/get_custom_fields_minimal.json

@@ -0,0 +1 @@
+{}

lucius_mcp-0.2.2/examples/get_custom_fields_with_project.json

@@ -0,0 +1,4 @@
+{
+    "name": "priority",
+    "project_id": 166
+}