rootly-mcp-server 2.1.1__tar.gz → 2.1.3__tar.gz

{rootly_mcp_server-2.1.1 → rootly_mcp_server-2.1.3}/.gitignore

@@ -189,6 +189,8 @@ swagger.json
 test_output/
 *.tmp
 
-# Markdown files (exclude all except README)
+# Markdown files (exclude all except README and CONTRIBUTING)
 *.md
-!README.md
+!README.md
+!CONTRIBUTING.md
+!CHANGELOG.md.beads/

rootly_mcp_server-2.1.3/CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing to Rootly MCP Server
+
+## Submitting Changes
+
+1. Fork the repository and create a feature branch
+2. Make your changes with clear, atomic commits
+3. Open a Pull Request with a description that clearly explains:
+   - What the change does
+   - Why it's needed
+   - Any breaking changes or migration steps
+
+## Developer Setup
+
+### Prerequisites
+- Python 3.12 or higher
+- [`uv`](https://github.com/astral-sh/uv) for dependency management
+
+### 1. Set Up Virtual Environment
+
+Create and activate a virtual environment:
+
+```bash
+uv venv .venv
+source .venv/bin/activate  # Always activate before running scripts
+```
+
+### 2. Install Dependencies
+
+Install all project dependencies:
+
+```bash
+uv pip install .
+```
+
+To add new dependencies during development:
+```bash
+uv pip install <package>
+```
+
+### 3. Set Up Git Hooks (Recommended)
+
+Install pre-commit hooks to automatically run linting and tests before commits:
+
+```bash
+./scripts/setup-hooks.sh
+```
+
+This ensures code quality by running:
+- Ruff linting
+- Pyright type checking
+- Unit tests
+
+### 4. Verify Installation
+
+The server should now be ready to use with your MCP-compatible editor.
+
+Additional testing tools are available in the `tests/` directory.

{rootly_mcp_server-2.1.1 → rootly_mcp_server-2.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rootly-mcp-server
-Version: 2.1.1
+Version: 2.1.3
 Summary: Secure Model Context Protocol server for Rootly APIs with AI SRE capabilities, comprehensive error handling, and input validation
 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
@@ -113,27 +113,6 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
 }
 ```
 
-To customize `allowed_paths` and access additional Rootly API paths, clone the repository and use this configuration:
-
-```json
-{
-  "mcpServers": {
-    "rootly": {
-      "command": "uv",
-      "args": [
-        "run",
-        "--directory",
-        "/path/to/rootly-mcp-server",
-        "rootly-mcp-server"
-      ],
-      "env": {
-        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
-      }
-    }
-  }
-}
-```
-
 ### Connect to Hosted MCP Server
 
 Alternatively, connect directly to our hosted MCP server:
@@ -168,6 +147,41 @@ Alternatively, connect directly to our hosted MCP server:
   - **`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
+- **On-Call Health Integration**: Detects burnout risk in scheduled responders
+
+## On-Call Health Integration
+
+Rootly MCP integrates with [On-Call Health](https://oncallhealth.ai) to detect burnout risk in scheduled responders.
+
+### Setup
+
+Set the `ONCALLHEALTH_API_KEY` environment variable:
+
+```json
+{
+  "mcpServers": {
+    "rootly": {
+      "command": "uvx",
+      "args": ["rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "your_rootly_token",
+        "ONCALLHEALTH_API_KEY": "och_live_your_key"
+      }
+    }
+  }
+}
+```
+
+### Usage
+
+```
+check_oncall_burnout_risk(
+    start_date="2026-02-09",
+    end_date="2026-02-15"
+)
+```
+
+Returns at-risk users who are scheduled, recommended safe replacements, and action summaries.
 
 ## Example Skills
 
@@ -196,103 +210,6 @@ cp examples/skills/rootly-incident-responder.md .claude/skills/
 
 This skill demonstrates a complete incident response workflow using Rootly's intelligent tools combined with GitHub integration for code correlation.
 
-### Available Tools
-
-**Alerts**
-- `listIncidentAlerts`
-- `listAlerts`
-- `attachAlert`
-- `createAlert`
-
-**Environments**
-- `listEnvironments`
-- `createEnvironment`
-
-**Functionalities**
-- `listFunctionalities`
-- `createFunctionality`
-
-**Workflows**
-- `listWorkflows`
-- `createWorkflow`
-
-**Incidents**
-- `listIncidentActionItems`
-- `createIncidentActionItem`
-- `listIncident_Types`
-- `createIncidentType`
-- `search_incidents`
-- `find_related_incidents`
-- `suggest_solutions`
-
-**On-Call**
-- `get_oncall_shift_metrics`
-- `get_oncall_handoff_summary`
-- `get_shift_incidents`
-
-**Services & Severities**
-- `listServices`
-- `createService`
-- `listSeverities`
-- `createSeverity`
-
-**Teams & Users**
-- `listTeams`
-- `createTeam`
-- `listUsers`
-- `getCurrentUser`
-
-**Meta**
-- `list_endpoints`
-
-### Why Path Limiting?
-
-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**: 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`.
-
-### Smart Analysis Tools
-
-The MCP server includes intelligent tools that analyze historical incident data to provide actionable insights:
-
-#### `find_related_incidents`
-Finds historically similar incidents using text similarity analysis:
-```
-find_related_incidents(incident_id="12345", similarity_threshold=0.15, 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 intelligent 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"`
-
 ### On-Call Shift Metrics
 
 Get on-call shift metrics for any time period, grouped by user, team, or schedule. Includes primary/secondary role tracking, shift counts, hours, and days on-call.
@@ -344,52 +261,9 @@ get_shift_incidents(
 Returns: `incidents` list + `summary` (counts, avg resolution time, grouping)
 
 
-## Developer Setup & Troubleshooting
-
-### Prerequisites
-- Python 3.12 or higher
-- [`uv`](https://github.com/astral-sh/uv) for dependency management
-
-### 1. Set Up Virtual Environment
-
-Create and activate a virtual environment:
-
-```bash
-uv venv .venv
-source .venv/bin/activate  # Always activate before running scripts
-```
-
-### 2. Install Dependencies
-
-Install all project dependencies:
-
-```bash
-uv pip install .
-```
-
-To add new dependencies during development:
-```bash
-uv pip install <package>
-```
-
-### 3. Set Up Git Hooks (Recommended for Contributors)
-
-Install pre-commit hooks to automatically run linting and tests before commits:
-
-```bash
-./scripts/setup-hooks.sh
-```
-
-This ensures code quality by running:
-- Ruff linting
-- Pyright type checking
-- Unit tests
-
-### 4. Verify Installation
-
-The server should now be ready to use with your MCP-compatible editor.
+## Contributing
 
-**For developers:** Additional testing tools are available in the `tests/` directory.
+See [CONTRIBUTING.md](CONTRIBUTING.md) for developer setup and guidelines.
 
 ## Play with it on Postman
 [<img src="https://run.pstmn.io/button.svg" alt="Run In Postman" style="width: 128px; height: 32px;">](https://god.gw.postman.com/run-collection/45004446-1074ba3c-44fe-40e3-a932-af7c071b96eb?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D45004446-1074ba3c-44fe-40e3-a932-af7c071b96eb%26entityType%3Dcollection%26workspaceId%3D4bec6e3c-50a0-4746-85f1-00a703c32f24)

{rootly_mcp_server-2.1.1 → rootly_mcp_server-2.1.3}/README.md

@@ -74,27 +74,6 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
 }
 ```
 
-To customize `allowed_paths` and access additional Rootly API paths, clone the repository and use this configuration:
-
-```json
-{
-  "mcpServers": {
-    "rootly": {
-      "command": "uv",
-      "args": [
-        "run",
-        "--directory",
-        "/path/to/rootly-mcp-server",
-        "rootly-mcp-server"
-      ],
-      "env": {
-        "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
-      }
-    }
-  }
-}
-```
-
 ### Connect to Hosted MCP Server
 
 Alternatively, connect directly to our hosted MCP server:
@@ -129,6 +108,41 @@ Alternatively, connect directly to our hosted MCP server:
   - **`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
+- **On-Call Health Integration**: Detects burnout risk in scheduled responders
+
+## On-Call Health Integration
+
+Rootly MCP integrates with [On-Call Health](https://oncallhealth.ai) to detect burnout risk in scheduled responders.
+
+### Setup
+
+Set the `ONCALLHEALTH_API_KEY` environment variable:
+
+```json
+{
+  "mcpServers": {
+    "rootly": {
+      "command": "uvx",
+      "args": ["rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "your_rootly_token",
+        "ONCALLHEALTH_API_KEY": "och_live_your_key"
+      }
+    }
+  }
+}
+```
+
+### Usage
+
+```
+check_oncall_burnout_risk(
+    start_date="2026-02-09",
+    end_date="2026-02-15"
+)
+```
+
+Returns at-risk users who are scheduled, recommended safe replacements, and action summaries.
 
 ## Example Skills
 
@@ -157,103 +171,6 @@ cp examples/skills/rootly-incident-responder.md .claude/skills/
 
 This skill demonstrates a complete incident response workflow using Rootly's intelligent tools combined with GitHub integration for code correlation.
 
-### Available Tools
-
-**Alerts**
-- `listIncidentAlerts`
-- `listAlerts`
-- `attachAlert`
-- `createAlert`
-
-**Environments**
-- `listEnvironments`
-- `createEnvironment`
-
-**Functionalities**
-- `listFunctionalities`
-- `createFunctionality`
-
-**Workflows**
-- `listWorkflows`
-- `createWorkflow`
-
-**Incidents**
-- `listIncidentActionItems`
-- `createIncidentActionItem`
-- `listIncident_Types`
-- `createIncidentType`
-- `search_incidents`
-- `find_related_incidents`
-- `suggest_solutions`
-
-**On-Call**
-- `get_oncall_shift_metrics`
-- `get_oncall_handoff_summary`
-- `get_shift_incidents`
-
-**Services & Severities**
-- `listServices`
-- `createService`
-- `listSeverities`
-- `createSeverity`
-
-**Teams & Users**
-- `listTeams`
-- `createTeam`
-- `listUsers`
-- `getCurrentUser`
-
-**Meta**
-- `list_endpoints`
-
-### Why Path Limiting?
-
-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**: 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`.
-
-### Smart Analysis Tools
-
-The MCP server includes intelligent tools that analyze historical incident data to provide actionable insights:
-
-#### `find_related_incidents`
-Finds historically similar incidents using text similarity analysis:
-```
-find_related_incidents(incident_id="12345", similarity_threshold=0.15, 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 intelligent 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"`
-
 ### On-Call Shift Metrics
 
 Get on-call shift metrics for any time period, grouped by user, team, or schedule. Includes primary/secondary role tracking, shift counts, hours, and days on-call.
@@ -305,52 +222,9 @@ get_shift_incidents(
 Returns: `incidents` list + `summary` (counts, avg resolution time, grouping)
 
 
-## Developer Setup & Troubleshooting
-
-### Prerequisites
-- Python 3.12 or higher
-- [`uv`](https://github.com/astral-sh/uv) for dependency management
-
-### 1. Set Up Virtual Environment
-
-Create and activate a virtual environment:
-
-```bash
-uv venv .venv
-source .venv/bin/activate  # Always activate before running scripts
-```
-
-### 2. Install Dependencies
-
-Install all project dependencies:
-
-```bash
-uv pip install .
-```
-
-To add new dependencies during development:
-```bash
-uv pip install <package>
-```
-
-### 3. Set Up Git Hooks (Recommended for Contributors)
-
-Install pre-commit hooks to automatically run linting and tests before commits:
-
-```bash
-./scripts/setup-hooks.sh
-```
-
-This ensures code quality by running:
-- Ruff linting
-- Pyright type checking
-- Unit tests
-
-### 4. Verify Installation
-
-The server should now be ready to use with your MCP-compatible editor.
+## Contributing
 
-**For developers:** Additional testing tools are available in the `tests/` directory.
+See [CONTRIBUTING.md](CONTRIBUTING.md) for developer setup and guidelines.
 
 ## Play with it on Postman
 [<img src="https://run.pstmn.io/button.svg" alt="Run In Postman" style="width: 128px; height: 32px;">](https://god.gw.postman.com/run-collection/45004446-1074ba3c-44fe-40e3-a932-af7c071b96eb?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D45004446-1074ba3c-44fe-40e3-a932-af7c071b96eb%26entityType%3Dcollection%26workspaceId%3D4bec6e3c-50a0-4746-85f1-00a703c32f24)

{rootly_mcp_server-2.1.1 → rootly_mcp_server-2.1.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rootly-mcp-server"
-version = "2.1.1"
+version = "2.1.3"
 description = "Secure Model Context Protocol server for Rootly APIs with AI SRE capabilities, comprehensive error handling, and input validation"
 readme = "README.md"
 requires-python = ">=3.10"

rootly_mcp_server-2.1.3/src/rootly_mcp_server/och_client.py

@@ -0,0 +1,71 @@
+"""On-Call Health API client for burnout risk analysis."""
+
+import os
+from typing import Any
+
+import httpx
+
+
+class OnCallHealthClient:
+    def __init__(self, api_key: str | None = None, base_url: str | None = None):
+        self.api_key: str = api_key or os.environ.get("ONCALLHEALTH_API_KEY", "")
+        self.base_url: str = base_url or os.environ.get(
+            "ONCALLHEALTH_API_URL", "https://api.oncallhealth.ai"
+        )
+
+    async def get_analysis(self, analysis_id: int) -> dict[str, Any]:
+        """Fetch analysis by ID."""
+        async with httpx.AsyncClient() as client:
+            response = await client.get(
+                f"{self.base_url}/analyses/{analysis_id}",
+                headers={"X-API-Key": self.api_key},
+                timeout=30.0,
+            )
+            response.raise_for_status()
+            return response.json()
+
+    async def get_latest_analysis(self) -> dict[str, Any]:
+        """Fetch most recent analysis."""
+        async with httpx.AsyncClient() as client:
+            response = await client.get(
+                f"{self.base_url}/analyses",
+                headers={"X-API-Key": self.api_key},
+                params={"limit": 1},
+                timeout=30.0,
+            )
+            response.raise_for_status()
+            data = response.json()
+            analyses = data.get("analyses", [])
+            if not analyses:
+                raise ValueError("No analyses found")
+            return analyses[0]
+
+    def extract_at_risk_users(
+        self, analysis: dict[str, Any], threshold: float = 50.0
+    ) -> tuple[list[dict[str, Any]], list[dict[str, Any]]]:
+        """Extract at-risk and safe users from analysis."""
+        members = analysis.get("analysis_data", {}).get("team_analysis", {}).get("members", [])
+
+        at_risk: list[dict[str, Any]] = []
+        safe: list[dict[str, Any]] = []
+
+        for member in members:
+            user_data: dict[str, Any] = {
+                "user_name": member.get("user_name"),
+                "rootly_user_id": member.get("rootly_user_id"),
+                "och_score": member.get("och_score", 0),
+                "risk_level": member.get("risk_level", "unknown"),
+                "burnout_score": member.get("burnout_score", 0),
+                "incident_count": member.get("incident_count", 0),
+            }
+
+            if user_data["och_score"] >= threshold:
+                at_risk.append(user_data)
+            elif user_data["och_score"] < 20:  # Safe threshold
+                safe.append(user_data)
+
+        # Sort at-risk by score descending, safe by score ascending
+        at_risk.sort(key=lambda x: x["och_score"], reverse=True)
+        safe.sort(key=lambda x: x["och_score"])
+
+        return at_risk, safe