rootly-mcp-server 2.0.14__tar.gz → 2.0.15__tar.gz

{rootly_mcp_server-2.0.14 → rootly_mcp_server-2.0.15}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rootly-mcp-server
-Version: 2.0.14
+Version: 2.0.15
 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
@@ -63,7 +63,7 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
         "run",
         "--from",
         "rootly-mcp-server",
-        "rootly-mcp-server",
+        "rootly-mcp-server"
       ],      
       "env": {
         "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
@@ -83,7 +83,7 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
       "args": [
         "--from",
         "rootly-mcp-server",
-        "rootly-mcp-server",
+        "rootly-mcp-server"
       ],      
       "env": {
         "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
@@ -143,46 +143,60 @@ 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
+- **Intelligent Incident Analysis**: Smart tools that analyze 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
-
-By default, the following Rootly API endpoints are exposed to the AI agent (see `allowed_paths` in `src/rootly_mcp_server/server.py`):
-
-```
-/v1/incidents
-/v1/incidents/{incident_id}/alerts
-/v1/alerts
-/v1/alerts/{alert_id}
-/v1/severities
-/v1/severities/{severity_id}
-/v1/teams
-/v1/teams/{team_id}
-/v1/services
-/v1/services/{service_id}
-/v1/functionalities
-/v1/functionalities/{functionality_id}
-/v1/incident_types
-/v1/incident_types/{incident_type_id}
-/v1/incident_action_items
-/v1/incident_action_items/{incident_action_item_id}
-/v1/incidents/{incident_id}/action_items
-/v1/workflows
-/v1/workflows/{workflow_id}
-/v1/workflow_runs
-/v1/workflow_runs/{workflow_run_id}
-/v1/environments
-/v1/environments/{environment_id}
-/v1/users
-/v1/users/{user_id}
-/v1/users/me
-/v1/status_pages
-/v1/status_pages/{status_page_id}
-```
+### 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?
 
@@ -193,14 +207,14 @@ We limit exposed API paths for two key reasons:
 
 To expose additional paths, modify the `allowed_paths` variable in `src/rootly_mcp_server/server.py`.
 
-### AI-Powered Smart Tools
+### 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 machine learning text analysis:
+Finds historically similar incidents using text similarity analysis:
 ```
-find_related_incidents(incident_id="12345", similarity_threshold=0.3, max_results=5)
+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
@@ -215,7 +229,7 @@ suggest_solutions(incident_title="Payment API errors", incident_description="Use
 ```
 - **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
+- **Use Case**: Get intelligent suggestions based on successful past resolutions
 
 #### How It Works
 - **Text Similarity**: Uses TF-IDF vectorization and cosine similarity (scikit-learn)
@@ -232,6 +246,56 @@ For optimal results, ensure your Rootly incidents have descriptive:
 
 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.
+
+```
+get_oncall_shift_metrics(
+    start_date="2025-10-01",
+    end_date="2025-10-31",
+    group_by="user"
+)
+```
+
+### On-Call Handoff Summary
+
+Complete handoff: current/next on-call + incidents during shifts.
+
+```python
+# All on-call (any timezone)
+get_oncall_handoff_summary(
+    team_ids="team-1,team-2",
+    timezone="America/Los_Angeles"
+)
+
+# Regional filter - only show APAC on-call during APAC business hours
+get_oncall_handoff_summary(
+    timezone="Asia/Tokyo",
+    filter_by_region=True
+)
+```
+
+Regional filtering shows only people on-call during business hours (9am-5pm) in the specified timezone.
+
+Returns: `schedules` with `current_oncall`, `next_oncall`, and `shift_incidents`
+
+### Shift Incidents
+
+Incidents during a time period, with filtering by severity/status/tags.
+
+```python
+get_shift_incidents(
+    start_time="2025-10-20T09:00:00Z",
+    end_time="2025-10-20T17:00:00Z",
+    severity="critical",  # optional
+    status="resolved",    # optional
+    tags="database,api"   # optional
+)
+```
+
+Returns: `incidents` list + `summary` (counts, avg resolution time, grouping)
+
 ## 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.
@@ -265,7 +329,20 @@ To add new dependencies during development:
 uv pip install <package>
 ```
 
-### 3. Verify Installation
+### 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.
 

{rootly_mcp_server-2.0.14 → rootly_mcp_server-2.0.15}/README.md

@@ -35,7 +35,7 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
         "run",
         "--from",
         "rootly-mcp-server",
-        "rootly-mcp-server",
+        "rootly-mcp-server"
       ],      
       "env": {
         "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
@@ -55,7 +55,7 @@ Configure your MCP-compatible editor (tested with Cursor) with one of the config
       "args": [
         "--from",
         "rootly-mcp-server",
-        "rootly-mcp-server",
+        "rootly-mcp-server"
       ],      
       "env": {
         "ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
@@ -115,46 +115,60 @@ 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
+- **Intelligent Incident Analysis**: Smart tools that analyze 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
-
-By default, the following Rootly API endpoints are exposed to the AI agent (see `allowed_paths` in `src/rootly_mcp_server/server.py`):
-
-```
-/v1/incidents
-/v1/incidents/{incident_id}/alerts
-/v1/alerts
-/v1/alerts/{alert_id}
-/v1/severities
-/v1/severities/{severity_id}
-/v1/teams
-/v1/teams/{team_id}
-/v1/services
-/v1/services/{service_id}
-/v1/functionalities
-/v1/functionalities/{functionality_id}
-/v1/incident_types
-/v1/incident_types/{incident_type_id}
-/v1/incident_action_items
-/v1/incident_action_items/{incident_action_item_id}
-/v1/incidents/{incident_id}/action_items
-/v1/workflows
-/v1/workflows/{workflow_id}
-/v1/workflow_runs
-/v1/workflow_runs/{workflow_run_id}
-/v1/environments
-/v1/environments/{environment_id}
-/v1/users
-/v1/users/{user_id}
-/v1/users/me
-/v1/status_pages
-/v1/status_pages/{status_page_id}
-```
+### 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?
 
@@ -165,14 +179,14 @@ We limit exposed API paths for two key reasons:
 
 To expose additional paths, modify the `allowed_paths` variable in `src/rootly_mcp_server/server.py`.
 
-### AI-Powered Smart Tools
+### 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 machine learning text analysis:
+Finds historically similar incidents using text similarity analysis:
 ```
-find_related_incidents(incident_id="12345", similarity_threshold=0.3, max_results=5)
+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
@@ -187,7 +201,7 @@ suggest_solutions(incident_title="Payment API errors", incident_description="Use
 ```
 - **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
+- **Use Case**: Get intelligent suggestions based on successful past resolutions
 
 #### How It Works
 - **Text Similarity**: Uses TF-IDF vectorization and cosine similarity (scikit-learn)
@@ -204,6 +218,56 @@ For optimal results, ensure your Rootly incidents have descriptive:
 
 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.
+
+```
+get_oncall_shift_metrics(
+    start_date="2025-10-01",
+    end_date="2025-10-31",
+    group_by="user"
+)
+```
+
+### On-Call Handoff Summary
+
+Complete handoff: current/next on-call + incidents during shifts.
+
+```python
+# All on-call (any timezone)
+get_oncall_handoff_summary(
+    team_ids="team-1,team-2",
+    timezone="America/Los_Angeles"
+)
+
+# Regional filter - only show APAC on-call during APAC business hours
+get_oncall_handoff_summary(
+    timezone="Asia/Tokyo",
+    filter_by_region=True
+)
+```
+
+Regional filtering shows only people on-call during business hours (9am-5pm) in the specified timezone.
+
+Returns: `schedules` with `current_oncall`, `next_oncall`, and `shift_incidents`
+
+### Shift Incidents
+
+Incidents during a time period, with filtering by severity/status/tags.
+
+```python
+get_shift_incidents(
+    start_time="2025-10-20T09:00:00Z",
+    end_time="2025-10-20T17:00:00Z",
+    severity="critical",  # optional
+    status="resolved",    # optional
+    tags="database,api"   # optional
+)
+```
+
+Returns: `incidents` list + `summary` (counts, avg resolution time, grouping)
+
 ## 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.
@@ -237,7 +301,20 @@ To add new dependencies during development:
 uv pip install <package>
 ```
 
-### 3. Verify Installation
+### 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.
 

{rootly_mcp_server-2.0.14 → rootly_mcp_server-2.0.15}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rootly-mcp-server"
-version = "2.0.14"
+version = "2.0.15"
 description = "A Model Context Protocol server for Rootly APIs using OpenAPI spec"
 readme = "README.md"
 requires-python = ">=3.12"

rootly_mcp_server-2.0.15/scripts/setup-hooks.sh

@@ -0,0 +1,66 @@
+#!/bin/bash
+# Setup git hooks for this repository
+# Run this script after cloning: ./scripts/setup-hooks.sh
+
+set -e
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+HOOKS_DIR="$REPO_ROOT/.git/hooks"
+
+echo "🔧 Setting up git hooks..."
+
+# Create pre-commit hook
+cat > "$HOOKS_DIR/pre-commit" << 'EOF'
+#!/bin/bash
+# Pre-commit hook to run linting and type checking
+# This ensures code quality before committing
+
+set -e
+
+echo "🔍 Running pre-commit checks..."
+echo ""
+
+# 1. Ruff linting
+echo "📝 Checking code style with ruff..."
+if ! uv run ruff check .; then
+    echo "❌ Ruff linting failed!"
+    echo "💡 Try running: uv run ruff check . --fix"
+    exit 1
+fi
+echo "✅ Ruff passed!"
+echo ""
+
+# 2. Pyright type checking
+echo "🔍 Running type checks with pyright..."
+if ! uv run pyright; then
+    echo "❌ Type checking failed!"
+    echo "💡 Fix type errors or add type: ignore comments"
+    exit 1
+fi
+echo "✅ Pyright passed!"
+echo ""
+
+# 3. Run unit tests (quick check)
+echo "🧪 Running unit tests..."
+if ! uv run pytest tests/unit/ -q --tb=line; then
+    echo "❌ Tests failed!"
+    echo "💡 Fix failing tests before committing"
+    exit 1
+fi
+echo "✅ Tests passed!"
+echo ""
+
+echo "✅ All pre-commit checks passed! Proceeding with commit..."
+exit 0
+EOF
+
+chmod +x "$HOOKS_DIR/pre-commit"
+
+echo "✅ Git hooks installed successfully!"
+echo ""
+echo "The following checks will run before every commit:"
+echo "  1. Ruff linting"
+echo "  2. Pyright type checking"
+echo "  3. Unit tests"
+echo ""
+echo "To skip hooks (not recommended): git commit --no-verify"