rootly-mcp-server 2.1.1__py3-none-any.whl → 2.1.3__py3-none-any.whl

{rootly_mcp_server-2.1.1.dist-info → rootly_mcp_server-2.1.3.dist-info}/METADATA

@@ -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.dist-info → rootly_mcp_server-2.1.3.dist-info}/RECORD

@@ -3,16 +3,17 @@ rootly_mcp_server/__main__.py,sha256=mt74vaOpfHnX5rTO0CFAeulatR_9K3NBNCaLAhBLxlc
 rootly_mcp_server/client.py,sha256=Qca2R9cgBxXcyobQj4RHl8gdxLB4Jphq0RIr61DAVKw,6542
 rootly_mcp_server/exceptions.py,sha256=67J_wlfOICg87eUipbkARzn_6u_Io82L-5cVnk2UPr0,4504
 rootly_mcp_server/monitoring.py,sha256=k1X7vK65FOTrCrOsLUXrFm6AJxKpXt_a0PzL6xdPuVU,11681
+rootly_mcp_server/och_client.py,sha256=tz_Qw8NwAmrlSjtl-V6WNVChiIofyur06YJZRfYotKE,2737
 rootly_mcp_server/pagination.py,sha256=2hZSO4DLUEJZbdF8oDfIt2_7X_XGBG1jIxN8VGmeJBE,2420
 rootly_mcp_server/security.py,sha256=YkMoVALZ3XaKnMu3yF5kVf3SW_jdKHllSMwVLk1OlX0,11556
-rootly_mcp_server/server.py,sha256=IQ2lZNZKckLRFr2ALjRL9AAjGWTsfQq4jkhlh0-BUig,109962
+rootly_mcp_server/server.py,sha256=9XcQ5_yOv4ofMRjXoDg3LsPFb8qDiOHEFz9dPNfwl7o,163221
 rootly_mcp_server/smart_utils.py,sha256=c7S-8H151GfmDw6dZBDdLH_cCmR1qiXkKEYSKc0WwUY,23481
 rootly_mcp_server/texttest.json,sha256=KV9m13kWugmW1VEpU80Irp50uCcLgJtV1YT-JzMogQg,154182
 rootly_mcp_server/utils.py,sha256=TWG1MaaFKrU1phRhU6FgHuZAEv91JOe_1w0L2OrPJMY,4406
 rootly_mcp_server/validators.py,sha256=z1Lvel2SpOFLo1cPdQGSrX2ySt6zqR42w0R6QV9c2Cc,4092
 rootly_mcp_server/data/__init__.py,sha256=KdWD6hiRssHXt0Ywgj3wjNHY1sx-XSPEqVHqrTArf54,143
-rootly_mcp_server-2.1.1.dist-info/METADATA,sha256=iaXmvsZRLzSyYHpERE-xdn0Rd6rrrCXbO57lWZeIBHs,13560
-rootly_mcp_server-2.1.1.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
-rootly_mcp_server-2.1.1.dist-info/entry_points.txt,sha256=NE33b8VgigVPGBkboyo6pvN1Vz35HZtLybxMO4Q03PI,70
-rootly_mcp_server-2.1.1.dist-info/licenses/LICENSE,sha256=c9w9ZZGl14r54tsP40oaq5adTVX_HMNHozPIH2ymzmw,11341
-rootly_mcp_server-2.1.1.dist-info/RECORD,,
+rootly_mcp_server-2.1.3.dist-info/METADATA,sha256=321Q8VyO2kJGCHbpEyf1NT73jZpB7Eb-KxbECDZcnVs,9892
+rootly_mcp_server-2.1.3.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
+rootly_mcp_server-2.1.3.dist-info/entry_points.txt,sha256=NE33b8VgigVPGBkboyo6pvN1Vz35HZtLybxMO4Q03PI,70
+rootly_mcp_server-2.1.3.dist-info/licenses/LICENSE,sha256=c9w9ZZGl14r54tsP40oaq5adTVX_HMNHozPIH2ymzmw,11341
+rootly_mcp_server-2.1.3.dist-info/RECORD,,