rootly-mcp-server 2.0.10__tar.gz → 2.0.12__tar.gz

rootly_mcp_server-2.0.12/.github/workflows/test.yml

@@ -0,0 +1,71 @@
+name: Tests
+
+on: [push, pull_request]
+
+jobs:
+  local-tests:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - uses: astral-sh/setup-uv@v3
+    - run: uv python install 3.12 && uv sync --dev
+    
+    # Fast local validation  
+    - name: Code quality checks
+      run: |
+        uv run ruff check .
+        uv run pyright
+    
+    - name: Unit tests
+      run: uv run pytest tests/unit/ --cov=src/rootly_mcp_server --cov-report=xml
+    
+    - name: Local integration tests
+      env:
+        ROOTLY_API_TOKEN: ${{ secrets.ROOTLY_API_TOKEN }}
+      run: uv run pytest tests/integration/local/ -x
+    
+    - name: Upload coverage
+      uses: codecov/codecov-action@v4
+      with:
+        file: ./coverage.xml
+
+  container-tests:
+    runs-on: ubuntu-latest
+    needs: local-tests
+    steps:
+    - uses: actions/checkout@v4
+    - uses: astral-sh/setup-uv@v3
+    - run: uv python install 3.12 && uv sync --dev
+    
+    # Build and run the Docker container
+    - name: Build Docker image
+      run: docker build -t rootly-mcp-server .
+    
+    - name: Start MCP server container
+      env:
+        ROOTLY_API_TOKEN: ${{ secrets.ROOTLY_API_TOKEN }}
+      run: |
+        docker run -d \
+          --name rootly-mcp-server \
+          -p 8000:8000 \
+          -e ROOTLY_API_TOKEN="${ROOTLY_API_TOKEN}" \
+          rootly-mcp-server
+    
+    # Wait for container to be ready
+    - name: Wait for container startup
+      run: |
+        echo "⏳ Waiting for container to start..."
+        timeout 30s bash -c 'until curl -f http://localhost:8000/health || curl -f http://localhost:8000/; do sleep 2; done'
+        echo "✅ Container is ready!"
+    
+    # Test the containerized server
+    - name: Test containerized MCP server
+      env:
+        ROOTLY_API_TOKEN: ${{ secrets.ROOTLY_API_TOKEN }}
+        MCP_SERVER_URL: "http://localhost:8000"
+      run: uv run pytest tests/integration/remote/test_essential.py -v --timeout=60
+    
+    # Cleanup
+    - name: Stop container
+      if: always()
+      run: docker stop rootly-mcp-server && docker rm rootly-mcp-server

{rootly_mcp_server-2.0.10 → rootly_mcp_server-2.0.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rootly-mcp-server
-Version: 2.0.10
+Version: 2.0.12
 Summary: A Model Context Protocol server for Rootly APIs using OpenAPI spec
 Project-URL: Homepage, https://github.com/Rootly-AI-Labs/Rootly-MCP-server
 Project-URL: Issues, https://github.com/Rootly-AI-Labs/Rootly-MCP-server/issues
@@ -17,8 +17,10 @@ Requires-Python: >=3.12
 Requires-Dist: brotli>=1.0.0
 Requires-Dist: fastmcp>=2.9.0
 Requires-Dist: httpx>=0.24.0
+Requires-Dist: numpy>=1.24.0
 Requires-Dist: pydantic>=2.0.0
 Requires-Dist: requests>=2.28.0
+Requires-Dist: scikit-learn>=1.3.0
 Provides-Extra: dev
 Requires-Dist: black>=23.0.0; extra == 'dev'
 Requires-Dist: isort>=5.0.0; extra == 'dev'
@@ -43,9 +45,7 @@ An MCP server for the [Rootly API](https://docs.rootly.com/api-reference/overvie
 
 ## Installation
 
-Install via our [PyPi package](https://pypi.org/project/rootly-mcp-server/) or by cloning this repository.
-
-Configure your MCP-compatible editor (tested with Cursor and Windsurf) with the following:
+Configure your MCP-compatible editor (tested with Cursor) with one of the configurations below. The package will be automatically downloaded and installed when you first open your editor.
 
 ### With uv
 
@@ -69,7 +69,7 @@ Configure your MCP-compatible editor (tested with Cursor and Windsurf) with the
 }
 ```
 
-### With uv-tool-uvx
+### With uvx
 
 ```json
 {
@@ -139,6 +139,11 @@ Alternatively, connect directly to our hosted MCP server:
 - **Dynamic Tool Generation**: Automatically creates MCP resources from Rootly's OpenAPI (Swagger) specification
 - **Smart Pagination**: Defaults to 10 items per request for incident endpoints to prevent context window overflow
 - **API Filtering**: Limits exposed API endpoints for security and performance
+- **AI-Powered Incident Analysis**: Smart tools that learn from historical incident data
+  - **`find_related_incidents`**: Uses TF-IDF similarity analysis to find historically similar incidents
+  - **`suggest_solutions`**: Mines past incident resolutions to recommend actionable solutions
+- **MCP Resources**: Exposes incident and team data as structured resources for easy AI reference
+- **Intelligent Pattern Recognition**: Automatically identifies services, error types, and resolution patterns
 
 ### Whitelisted Endpoints
 
@@ -180,10 +185,49 @@ By default, the following Rootly API endpoints are exposed to the AI agent (see
 We limit exposed API paths for two key reasons:
 
 1. **Context Management**: Rootly's comprehensive API can overwhelm AI agents, affecting their ability to perform simple tasks effectively
-2. **Security**: Control which information and actions are accessible through the MCP server
+2. **Security**: Controls which information and actions are accessible through the MCP server
 
 To expose additional paths, modify the `allowed_paths` variable in `src/rootly_mcp_server/server.py`.
 
+### AI-Powered Smart Tools
+
+The MCP server includes intelligent tools that analyze historical incident data to provide actionable insights:
+
+#### `find_related_incidents`
+Finds historically similar incidents using machine learning text analysis:
+```
+find_related_incidents(incident_id="12345", similarity_threshold=0.3, max_results=5)
+```
+- **Input**: Incident ID, similarity threshold (0.0-1.0), max results
+- **Output**: Similar incidents with confidence scores, matched services, and resolution times
+- **Use Case**: Get context from past incidents to understand patterns and solutions
+
+#### `suggest_solutions` 
+Recommends solutions by analyzing how similar incidents were resolved:
+```
+suggest_solutions(incident_id="12345", max_solutions=3)
+# OR for new incidents:
+suggest_solutions(incident_title="Payment API errors", incident_description="Users getting 500 errors during checkout")
+```
+- **Input**: Either incident ID OR title/description text
+- **Output**: Actionable solution recommendations with confidence scores and time estimates  
+- **Use Case**: Get AI-powered suggestions based on successful past resolutions
+
+#### How It Works
+- **Text Similarity**: Uses TF-IDF vectorization and cosine similarity (scikit-learn)
+- **Service Detection**: Automatically identifies affected services from incident text
+- **Pattern Recognition**: Finds common error types, resolution patterns, and time estimates
+- **Fallback Mode**: Works without ML libraries using keyword-based similarity
+- **Solution Mining**: Extracts actionable steps from resolution summaries
+
+#### Data Requirements
+For optimal results, ensure your Rootly incidents have descriptive:
+- **Titles**: Clear, specific incident descriptions
+- **Summaries**: Detailed resolution steps when closing incidents
+- **Service Tags**: Proper service identification
+
+Example good resolution summary: `"Restarted auth-service, cleared Redis cache, and increased connection pool from 10 to 50"`
+
 ## About Rootly AI Labs
 
 This project was developed by [Rootly AI Labs](https://labs.rootly.ai/), where we're building the future of system reliability and operational excellence. As an open-source incubator, we share ideas, experiment, and rapidly prototype solutions that benefit the entire community.
@@ -219,9 +263,7 @@ uv pip install <package>
 
 ### 3. Verify Installation
 
-Run the test client to ensure everything is configured correctly:
+The server should now be ready to use with your MCP-compatible editor.
 
-```bash
-python src/rootly_mcp_server/test_client.py
-```
+**For developers:** Additional testing tools are available in the `tests/` directory.
 

{rootly_mcp_server-2.0.10 → rootly_mcp_server-2.0.12}/README.md

@@ -17,9 +17,7 @@ An MCP server for the [Rootly API](https://docs.rootly.com/api-reference/overvie
 
 ## Installation
 
-Install via our [PyPi package](https://pypi.org/project/rootly-mcp-server/) or by cloning this repository.
-
-Configure your MCP-compatible editor (tested with Cursor and Windsurf) with the following:
+Configure your MCP-compatible editor (tested with Cursor) with one of the configurations below. The package will be automatically downloaded and installed when you first open your editor.
 
 ### With uv
 
@@ -43,7 +41,7 @@ Configure your MCP-compatible editor (tested with Cursor and Windsurf) with the
 }
 ```
 
-### With uv-tool-uvx
+### With uvx
 
 ```json
 {
@@ -113,6 +111,11 @@ Alternatively, connect directly to our hosted MCP server:
 - **Dynamic Tool Generation**: Automatically creates MCP resources from Rootly's OpenAPI (Swagger) specification
 - **Smart Pagination**: Defaults to 10 items per request for incident endpoints to prevent context window overflow
 - **API Filtering**: Limits exposed API endpoints for security and performance
+- **AI-Powered Incident Analysis**: Smart tools that learn from historical incident data
+  - **`find_related_incidents`**: Uses TF-IDF similarity analysis to find historically similar incidents
+  - **`suggest_solutions`**: Mines past incident resolutions to recommend actionable solutions
+- **MCP Resources**: Exposes incident and team data as structured resources for easy AI reference
+- **Intelligent Pattern Recognition**: Automatically identifies services, error types, and resolution patterns
 
 ### Whitelisted Endpoints
 
@@ -154,10 +157,49 @@ By default, the following Rootly API endpoints are exposed to the AI agent (see
 We limit exposed API paths for two key reasons:
 
 1. **Context Management**: Rootly's comprehensive API can overwhelm AI agents, affecting their ability to perform simple tasks effectively
-2. **Security**: Control which information and actions are accessible through the MCP server
+2. **Security**: Controls which information and actions are accessible through the MCP server
 
 To expose additional paths, modify the `allowed_paths` variable in `src/rootly_mcp_server/server.py`.
 
+### AI-Powered Smart Tools
+
+The MCP server includes intelligent tools that analyze historical incident data to provide actionable insights:
+
+#### `find_related_incidents`
+Finds historically similar incidents using machine learning text analysis:
+```
+find_related_incidents(incident_id="12345", similarity_threshold=0.3, max_results=5)
+```
+- **Input**: Incident ID, similarity threshold (0.0-1.0), max results
+- **Output**: Similar incidents with confidence scores, matched services, and resolution times
+- **Use Case**: Get context from past incidents to understand patterns and solutions
+
+#### `suggest_solutions` 
+Recommends solutions by analyzing how similar incidents were resolved:
+```
+suggest_solutions(incident_id="12345", max_solutions=3)
+# OR for new incidents:
+suggest_solutions(incident_title="Payment API errors", incident_description="Users getting 500 errors during checkout")
+```
+- **Input**: Either incident ID OR title/description text
+- **Output**: Actionable solution recommendations with confidence scores and time estimates  
+- **Use Case**: Get AI-powered suggestions based on successful past resolutions
+
+#### How It Works
+- **Text Similarity**: Uses TF-IDF vectorization and cosine similarity (scikit-learn)
+- **Service Detection**: Automatically identifies affected services from incident text
+- **Pattern Recognition**: Finds common error types, resolution patterns, and time estimates
+- **Fallback Mode**: Works without ML libraries using keyword-based similarity
+- **Solution Mining**: Extracts actionable steps from resolution summaries
+
+#### Data Requirements
+For optimal results, ensure your Rootly incidents have descriptive:
+- **Titles**: Clear, specific incident descriptions
+- **Summaries**: Detailed resolution steps when closing incidents
+- **Service Tags**: Proper service identification
+
+Example good resolution summary: `"Restarted auth-service, cleared Redis cache, and increased connection pool from 10 to 50"`
+
 ## About Rootly AI Labs
 
 This project was developed by [Rootly AI Labs](https://labs.rootly.ai/), where we're building the future of system reliability and operational excellence. As an open-source incubator, we share ideas, experiment, and rapidly prototype solutions that benefit the entire community.
@@ -193,9 +235,7 @@ uv pip install <package>
 
 ### 3. Verify Installation
 
-Run the test client to ensure everything is configured correctly:
+The server should now be ready to use with your MCP-compatible editor.
 
-```bash
-python src/rootly_mcp_server/test_client.py
-```
+**For developers:** Additional testing tools are available in the `tests/` directory.
 

{rootly_mcp_server-2.0.10 → rootly_mcp_server-2.0.12}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rootly-mcp-server"
-version = "2.0.10"
+version = "2.0.12"
 description = "A Model Context Protocol server for Rootly APIs using OpenAPI spec"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -21,6 +21,8 @@ dependencies = [
     "httpx>=0.24.0",    # For async HTTP client
     "pydantic>=2.0.0",  # For data validation
     "brotli>=1.0.0",    # For Brotli compression support in httpx
+    "scikit-learn>=1.3.0", # For text similarity and ML utilities
+    "numpy>=1.24.0",    # For numerical operations
 ]
 
 [project.urls]
@@ -50,10 +52,35 @@ rootly-mcp-server = "rootly_mcp_server.__main__:main"
 dev = ["black>=23.0.0", "isort>=5.0.0"]
 
 [tool.uv]
-dev-dependencies = ["pyright>=1.1.389", "ruff>=0.7.3", "pytest>=8.0.0"]
+dev-dependencies = [
+    "pyright>=1.1.404",
+    "ruff>=0.7.3",
+    "pytest>=8.0.0",
+    "pytest-cov>=4.0.0", # Coverage reporting
+    "pytest-asyncio>=0.23.0", # Async testing support
+    "pytest-mock>=3.12.0", # Mocking utilities
+    "pytest-timeout>=2.2.0", # Test timeout handling
+    "respx>=0.20.0", # HTTP request mocking
+    "sseclient-py>=1.8.0", # Server-Sent Events client for remote tests
+]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
 python_files = "test_*.py"
 python_classes = "Test*"
 python_functions = "test_*"
+addopts = [
+    "-v",                          # Verbose output
+    "--strict-markers",            # Require marker registration
+    "--tb=short",                  # Short traceback format
+    "--cov=src/rootly_mcp_server", # Coverage for main package
+    "--cov-report=term-missing",   # Show missing lines in coverage
+    "--cov-report=xml",            # XML coverage for CI
+]
+markers = [
+    "unit: Unit tests",
+    "integration: Integration tests", 
+    "remote: Remote server tests (require API token)",
+    "slow: Tests that take longer to run",
+]
+asyncio_mode = "auto"              # Auto-detect async tests

{rootly_mcp_server-2.0.10 → rootly_mcp_server-2.0.12}/src/rootly_mcp_server/__init__.py

@@ -13,7 +13,7 @@ Features:
 from .server import RootlyMCPServer
 from .client import RootlyClient
 
-__version__ = "2.0.1"
+__version__ = "2.0.12"
 __all__ = [
     'RootlyMCPServer',
     'RootlyClient',

{rootly_mcp_server-2.0.10 → rootly_mcp_server-2.0.12}/src/rootly_mcp_server/client.py

@@ -121,7 +121,7 @@ class RootlyClient:
             # Add response details if available
             if hasattr(e, "response") and e.response is not None:
                 try:
-                    error_response["status_code"] = e.response.status_code
+                    error_response["status_code"] = str(e.response.status_code)
                     error_response["response_text"] = e.response.text
                 except Exception:
                     pass