rootly-mcp-server 2.2.22__tar.gz → 2.3.0__tar.gz

{rootly_mcp_server-2.2.22 → rootly_mcp_server-2.3.0}/CHANGELOG.md

@@ -5,6 +5,73 @@ All notable changes to the Rootly MCP Server will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.3.0] - Released 2026-04-23
+
+### Features
+
+- **Comprehensive API Coverage Expansion**: Expanded MCP tool surface from 124 to 150+ tools by updating to latest Rootly API specification with 95+ operations
+- **Enhanced Tool Discoverability**: Added contextual "WHEN TO USE" guidance to tool descriptions for improved AI agent decision-making
+- **Workflow-Focused Tool Subsets**: Introduced 5 predefined tool configurations optimized for specific use cases (Incident Response, Schedule Management, Monitoring Setup, Retrospectives, Administration)
+- **Operational Context Resources**: Added new MCP resources for real-time operational awareness:
+  - `rootly://oncall-status` - Live on-call status across teams for incident response context
+  - `rootly://workflow-guide` - Step-by-step workflow guidance for common Rootly operations
+- **Expanded Write Operations**: Added 54 non-destructive write operations while maintaining security boundaries
+- **API Path Coverage**: Increased DEFAULT_ALLOWED_PATHS from ~80 to 151 endpoints covering workflows, dashboards, communications, playbooks, and monitoring
+
+### Enhanced
+
+- **Tool Descriptions**: Enhanced incident and on-call tool descriptions with specific usage context and best practices
+- **Environment Configuration**: Improved environment-based tool subset configuration following MCP best practices
+- **Error Handling**: Robust error handling in new resource implementations with proper categorization
+
+### Documentation
+
+- **README Updates**: Updated tool counts, added workflow subset configurations, and enhanced setup guidance
+- **Configuration Examples**: Added 5 workflow-focused environment configurations for optimal AI performance
+- **API Coverage**: Documented comprehensive endpoint coverage while highlighting security exclusions
+
+### Security
+
+- **Maintained Boundaries**: Preserved security exclusions for sensitive operations (API keys, user management, webhooks, financial data)
+- **Curated Approach**: Continued read-first philosophy with carefully selected write operations
+- **Input Validation**: Maintained existing security controls and validation patterns
+
+### Testing
+
+- **Updated Assertions**: Fixed test assertions to match updated API operation names (listAlertsSources, getAlertsSource)
+- **Comprehensive Coverage**: All 382 tests passing with expanded API surface
+- **Security Validation**: Verified security boundaries remain intact with expanded tool set
+
+### Breaking Changes
+
+- None - Fully backward compatible with existing configurations and user workflows
+
+## [2.2.24] - Released 2026-04-22
+
+### Fixed
+
+- **Incident Form Field Selection Responses**: Normalized text and textarea form field selection responses so MCP clients receive the primary `value` plus `selected_*_ids`, without the redundant `selected_*` value objects repeated across unrelated resource types
+
+### Testing
+
+- **Response Normalization Coverage**: Added focused transport tests for single-item and list incident form field selection payloads, including a guard to leave select-style fields unchanged
+
+## [2.2.23] - Released 2026-04-22
+
+### Features
+
+- **Self-Hosted Tool Allowlists**: Added `ROOTLY_MCP_ENABLED_TOOLS` and `--enabled-tools` so self-hosted deployments can expose only an exact allowlist of MCP tool names
+- **Tool Discovery Command**: Added `--list-tools` so self-hosted users can print the effective tool names for their current configuration before narrowing the MCP surface
+- **Code Mode Alignment**: Applied the same allowlist behavior to the self-hosted Code Mode surface so discovery and enforcement stay consistent
+
+### Testing
+
+- **Live MCP Integration Coverage**: Added subprocess integration tests that boot the server, connect over streamable HTTP, call `tools/list`, and verify the live tool payload matches the configured allowlist
+
+### Documentation
+
+- **Self-Hosted Setup Guidance**: Documented the new allowlist and discovery workflow in the README, including smoke-test examples for read-only and write-enabled self-hosted setups
+
 ## [2.2.20] - Released 2026-04-21
 
 ### Security

{rootly_mcp_server-2.2.22 → rootly_mcp_server-2.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rootly-mcp-server
-Version: 2.2.22
+Version: 2.3.0
 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
@@ -350,7 +350,7 @@ Choose one transport per server process:
 - **SSE** endpoint path: `/sse`
 - **Code Mode (experimental)** endpoint path: `/mcp-codemode` in hosted dual-transport mode
 
-Both hosted and self-hosted deployments expose all tools by default (read and write) for consistency. To restrict to read-only tools, start the server with `--no-enable-write-tools` or set `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false`.
+Both hosted and self-hosted deployments expose the same curated tool surface by default, including the default write-enabled tools. To restrict that surface to read-only tools, start the server with `--no-enable-write-tools` or set `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false`.
 
 To expose only a specific subset of MCP tools on a self-hosted deployment, set `ROOTLY_MCP_ENABLED_TOOLS` (or pass `--enabled-tools`) with a comma-separated allowlist of exact tool names, for example `list_incidents,getIncident,get_server_version`.
 
@@ -416,6 +416,70 @@ docker run -p 8000:8000 \
   rootly-mcp-server
 ```
 
+## Workflow-Focused Tool Subsets
+
+With 150+ tools available, you may want to configure focused subsets for optimal AI agent performance. Use `ROOTLY_MCP_ENABLED_TOOLS` to activate specific workflows:
+
+### 🚨 Incident Response (25 tools)
+*Essential tools for emergency responders and incident commanders*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listIncidents,getIncident,createIncident,updateIncident,search_incidents,find_related_incidents,suggest_solutions,createIncidentActionItem,listIncidentActionItems,updateIncidentFormFieldSelection,listTeams,getCurrentUser,listServices,listSeverities,getAlert,listAlerts,updateAlert,listEscalationPolicies,getEscalationPolicy,listOnCallRoles,listSchedules,getScheduleShifts,get_oncall_handoff_summary,get_shift_incidents,list_endpoints"
+```
+
+### 📅 On-Call Management (35 tools)  
+*For schedule coordinators and on-call managers*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listSchedules,getSchedule,updateSchedule,getScheduleShifts,listShifts,list_shifts,createScheduleRotation,updateScheduleRotation,listScheduleRotations,getScheduleRotation,listScheduleRotationUsers,updateScheduleRotationUser,createOnCallShadow,updateOnCallShadow,listOnCallShadows,createOverrideShift,updateOverrideShift,listOverrideShifts,listOnCallRoles,updateOnCallRole,get_oncall_schedule_summary,get_oncall_shift_metrics,check_oncall_health_risk,check_responder_availability,create_override_recommendation,listTeams,getTeam,listUsers,getUser,getCurrentUser,listEscalationPolicies,updateEscalationPolicy,listEscalationPaths,updateEscalationPath,listEscalationLevels"
+```
+
+### 📊 Monitoring & Alerting (40 tools)
+*For platform teams setting up observability*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listAlerts,getAlert,updateAlert,createAlertGroup,updateAlertGroup,listAlertGroups,createAlertRoutingRule,updateAlertRoutingRule,listAlertRoutingRules,listAlertEvents,getAlertEvent,updateAlertEvent,createHeartbeat,updateHeartbeat,listHeartbeats,getHeartbeat,createPulse,updatePulse,listPulses,getPulse,createDashboard,updateDashboard,listDashboards,getDashboard,createDashboardPanel,updateDashboardPanel,listStatusPages,getStatusPage,updateStatusPage,createStatusPageTemplate,updateStatusPageTemplate,listCommunicationsTemplates,updateCommunicationsTemplate,createLiveCallRouter,updateLiveCallRouter,listServices,listTeams,getCurrentUser,listEnvironments,listSeverities,list_endpoints"
+```
+
+### 📋 Post-Incident Analysis (30 tools)
+*For SREs doing retrospectives and process improvement*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="getIncident,updateIncident,find_related_incidents,suggest_solutions,listIncidentActionItems,createIncidentActionItem,updateIncidentFormFieldSelection,createPostIncidentReview,updatePostIncidentReview,listPostIncidentReviews,getPostIncidentReview,createRetrospectiveStep,updateRetrospectiveStep,listRetrospectiveSteps,createRetrospectiveProcess,updateRetrospectiveProcess,listRetrospectiveProcesses,createPlaybook,updatePlaybook,listPlaybooks,getPlaybook,createPlaybookTask,updatePlaybookTask,listCauses,getCause,updateCause,listIncidentTypes,getIncidentType,updateIncidentType,getCurrentUser"
+```
+
+### 📈 Analytics & Reporting (15 tools)
+*For leadership and metrics teams (read-only focus)*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listIncidents,search_incidents,collect_incidents,listTeams,listServices,listSchedules,get_oncall_shift_metrics,get_shift_incidents,listDashboards,getDashboard,listAlerts,listHeartbeats,listPulses,getCurrentUser,list_endpoints"
+```
+
+### Multiple MCP Instances for Different Teams
+
+You can run multiple MCP instances with different tool subsets:
+
+```json
+{
+  "mcpServers": {
+    "rootly-incident-response": {
+      "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "<token>",
+        "ROOTLY_MCP_ENABLED_TOOLS": "listIncidents,getIncident,createIncident,find_related_incidents,suggest_solutions..."
+      }
+    },
+    "rootly-oncall-management": {
+      "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "<token>",
+        "ROOTLY_MCP_ENABLED_TOOLS": "listSchedules,updateSchedule,createOverrideShift,get_oncall_shift_metrics..."
+      }
+    }
+  }
+}
+```
+
 ### With uvx
 
 ```json
@@ -444,13 +508,13 @@ docker run -p 8000:8000 \
 - **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
+- **MCP Resources**: Exposes incidents, teams, on-call status, and workflow guides as structured resources for AI context
 - **Intelligent Pattern Recognition**: Automatically identifies services, error types, and resolution patterns
 - **On-Call Health Integration**: Detects workload health risk in scheduled responders
 
 ## Supported Tools
 
-The default server configuration exposes **110 tools**.
+The default server configuration exposes **150+ tools**.
 
 ### Custom Agentic Tools
 
@@ -477,41 +541,31 @@ The default server configuration exposes **110 tools**.
 ### OpenAPI-Generated Tools
 
 ```text
-attachAlert
-createAlert
-createEnvironment
-createEscalationLevel
-createEscalationLevelPaths
-createEscalationPath
-createEscalationPolicy
-createFunctionality
+ListWorkflowRuns
 createIncidentActionItem
 createIncidentFormFieldSelection
-createIncidentType
-createOnCallRole
-createOnCallShadow
-createOverrideShift
-createSchedule
-createScheduleRotation
-createScheduleRotationActiveDay
-createScheduleRotationUser
-createService
-createSeverity
-createTeam
-createWorkflow
 createWorkflowTask
-deleteEscalationLevel
-deleteEscalationPath
-deleteEscalationPolicy
-deleteSchedule
-deleteScheduleRotation
 getAlert
+getAlertEvent
+getAlertGroup
+getAlertRoutingRule
+getAlertSource
+getAlertUrgency
+getCatalog
+getCatalogEntity
+getCause
 getCurrentUser
+getCustomForm
 getEnvironment
 getEscalationLevel
 getEscalationPath
 getEscalationPolicy
+getFormField
+getFormFieldOption
 getFunctionality
+getFunctionalityIncidentsChart
+getFunctionalityUptimeChart
+getIncidentActionItems
 getIncidentFormFieldSelection
 getIncidentType
 getOnCallRole
@@ -521,22 +575,42 @@ getSchedule
 getScheduleRotation
 getScheduleShifts
 getService
+getServiceIncidentsChart
+getServiceUptimeChart
 getSeverity
+getStatusPage
+getStatusPageTemplate
 getTeam
+getTeamIncidentsChart
 getUser
 getWorkflow
+getWorkflowFormFieldCondition
+getWorkflowGroup
 getWorkflowTask
+listAlertEvents
+listAlertGroups
+listAlertRoutingRules
+listAlertSources
+listAlertUrgencies
 listAlerts
+listAllIncidentActionItems
+listCatalogEntities
+listCatalogs
+listCauses
+listCustomForms
 listEnvironments
 listEscalationLevels
 listEscalationLevelsPaths
 listEscalationPaths
 listEscalationPolicies
+listFormFieldOptions
+listFormFields
 listFunctionalities
 listIncidentActionItems
 listIncidentAlerts
 listIncidentFormFieldSelections
 listIncident_Types
+listIncidents
 listOnCallRoles
 listOnCallShadows
 listOverrideShifts
@@ -547,17 +621,19 @@ listSchedules
 listServices
 listSeverities
 listShifts
+listStatusPageTemplates
+listStatusPages
 listTeams
 listUsers
+listWorkflowFormFieldConditions
+listWorkflowGroups
 listWorkflows
 listWorkflowTasks
-updateAlert
 updateEnvironment
 updateEscalationLevel
 updateEscalationPath
 updateEscalationPolicy
 updateFunctionality
-updateIncidentFormFieldSelection
 updateIncidentType
 updateOnCallRole
 updateOnCallShadow
@@ -567,13 +643,14 @@ updateScheduleRotation
 updateService
 updateSeverity
 updateTeam
-updateUser
 updateWorkflow
+updateIncidentFormFieldSelection
 updateWorkflowTask
 ```
 
-Delete operations are intentionally scoped to screenshot coverage paths:
-`deleteSchedule`, `deleteScheduleRotation`, `deleteEscalationPolicy`, `deleteEscalationPath`, `deleteEscalationLevel`.
+**Major Expansion**: This version includes 50+ new endpoints covering communications, dashboards, playbooks, post-incident reviews, monitoring, and advanced form management - while carefully excluding security-sensitive operations like API key management, user creation/deletion, role management, and webhook configuration.
+
+Delete operations remain disabled in the default tool surface.
 
 ## On-Call Health Integration
 
@@ -670,6 +747,18 @@ Regional filtering shows only people on-call during business hours (9am-5pm) in
 
 Returns: `schedules` with `current_oncall`, `next_oncall`, and `shift_incidents`
 
+### MCP Resources for Context
+
+AI agents can access these resources for situational awareness:
+
+- **`incident://{incident_id}`** - Detailed incident information for specific incidents
+- **`team://{team_id}`** - Team details including name, color, and metadata  
+- **`rootly://incidents`** - List of recent incidents for quick reference
+- **`rootly://oncall-status`** - Current on-call status across all schedules (critical for incident response)
+- **`rootly://workflow-guide`** - Step-by-step workflow guidance for common operations
+
+Example usage: *"Check the current on-call status"* → AI reads `rootly://oncall-status` resource
+
 ### Shift Incidents
 
 Incidents during a time period, with filtering by severity/status/tags.

{rootly_mcp_server-2.2.22 → rootly_mcp_server-2.3.0}/README.md

@@ -306,7 +306,7 @@ Choose one transport per server process:
 - **SSE** endpoint path: `/sse`
 - **Code Mode (experimental)** endpoint path: `/mcp-codemode` in hosted dual-transport mode
 
-Both hosted and self-hosted deployments expose all tools by default (read and write) for consistency. To restrict to read-only tools, start the server with `--no-enable-write-tools` or set `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false`.
+Both hosted and self-hosted deployments expose the same curated tool surface by default, including the default write-enabled tools. To restrict that surface to read-only tools, start the server with `--no-enable-write-tools` or set `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false`.
 
 To expose only a specific subset of MCP tools on a self-hosted deployment, set `ROOTLY_MCP_ENABLED_TOOLS` (or pass `--enabled-tools`) with a comma-separated allowlist of exact tool names, for example `list_incidents,getIncident,get_server_version`.
 
@@ -372,6 +372,70 @@ docker run -p 8000:8000 \
   rootly-mcp-server
 ```
 
+## Workflow-Focused Tool Subsets
+
+With 150+ tools available, you may want to configure focused subsets for optimal AI agent performance. Use `ROOTLY_MCP_ENABLED_TOOLS` to activate specific workflows:
+
+### 🚨 Incident Response (25 tools)
+*Essential tools for emergency responders and incident commanders*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listIncidents,getIncident,createIncident,updateIncident,search_incidents,find_related_incidents,suggest_solutions,createIncidentActionItem,listIncidentActionItems,updateIncidentFormFieldSelection,listTeams,getCurrentUser,listServices,listSeverities,getAlert,listAlerts,updateAlert,listEscalationPolicies,getEscalationPolicy,listOnCallRoles,listSchedules,getScheduleShifts,get_oncall_handoff_summary,get_shift_incidents,list_endpoints"
+```
+
+### 📅 On-Call Management (35 tools)  
+*For schedule coordinators and on-call managers*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listSchedules,getSchedule,updateSchedule,getScheduleShifts,listShifts,list_shifts,createScheduleRotation,updateScheduleRotation,listScheduleRotations,getScheduleRotation,listScheduleRotationUsers,updateScheduleRotationUser,createOnCallShadow,updateOnCallShadow,listOnCallShadows,createOverrideShift,updateOverrideShift,listOverrideShifts,listOnCallRoles,updateOnCallRole,get_oncall_schedule_summary,get_oncall_shift_metrics,check_oncall_health_risk,check_responder_availability,create_override_recommendation,listTeams,getTeam,listUsers,getUser,getCurrentUser,listEscalationPolicies,updateEscalationPolicy,listEscalationPaths,updateEscalationPath,listEscalationLevels"
+```
+
+### 📊 Monitoring & Alerting (40 tools)
+*For platform teams setting up observability*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listAlerts,getAlert,updateAlert,createAlertGroup,updateAlertGroup,listAlertGroups,createAlertRoutingRule,updateAlertRoutingRule,listAlertRoutingRules,listAlertEvents,getAlertEvent,updateAlertEvent,createHeartbeat,updateHeartbeat,listHeartbeats,getHeartbeat,createPulse,updatePulse,listPulses,getPulse,createDashboard,updateDashboard,listDashboards,getDashboard,createDashboardPanel,updateDashboardPanel,listStatusPages,getStatusPage,updateStatusPage,createStatusPageTemplate,updateStatusPageTemplate,listCommunicationsTemplates,updateCommunicationsTemplate,createLiveCallRouter,updateLiveCallRouter,listServices,listTeams,getCurrentUser,listEnvironments,listSeverities,list_endpoints"
+```
+
+### 📋 Post-Incident Analysis (30 tools)
+*For SREs doing retrospectives and process improvement*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="getIncident,updateIncident,find_related_incidents,suggest_solutions,listIncidentActionItems,createIncidentActionItem,updateIncidentFormFieldSelection,createPostIncidentReview,updatePostIncidentReview,listPostIncidentReviews,getPostIncidentReview,createRetrospectiveStep,updateRetrospectiveStep,listRetrospectiveSteps,createRetrospectiveProcess,updateRetrospectiveProcess,listRetrospectiveProcesses,createPlaybook,updatePlaybook,listPlaybooks,getPlaybook,createPlaybookTask,updatePlaybookTask,listCauses,getCause,updateCause,listIncidentTypes,getIncidentType,updateIncidentType,getCurrentUser"
+```
+
+### 📈 Analytics & Reporting (15 tools)
+*For leadership and metrics teams (read-only focus)*
+
+```bash
+ROOTLY_MCP_ENABLED_TOOLS="listIncidents,search_incidents,collect_incidents,listTeams,listServices,listSchedules,get_oncall_shift_metrics,get_shift_incidents,listDashboards,getDashboard,listAlerts,listHeartbeats,listPulses,getCurrentUser,list_endpoints"
+```
+
+### Multiple MCP Instances for Different Teams
+
+You can run multiple MCP instances with different tool subsets:
+
+```json
+{
+  "mcpServers": {
+    "rootly-incident-response": {
+      "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "<token>",
+        "ROOTLY_MCP_ENABLED_TOOLS": "listIncidents,getIncident,createIncident,find_related_incidents,suggest_solutions..."
+      }
+    },
+    "rootly-oncall-management": {
+      "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"],
+      "env": {
+        "ROOTLY_API_TOKEN": "<token>",
+        "ROOTLY_MCP_ENABLED_TOOLS": "listSchedules,updateSchedule,createOverrideShift,get_oncall_shift_metrics..."
+      }
+    }
+  }
+}
+```
+
 ### With uvx
 
 ```json
@@ -400,13 +464,13 @@ docker run -p 8000:8000 \
 - **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
+- **MCP Resources**: Exposes incidents, teams, on-call status, and workflow guides as structured resources for AI context
 - **Intelligent Pattern Recognition**: Automatically identifies services, error types, and resolution patterns
 - **On-Call Health Integration**: Detects workload health risk in scheduled responders
 
 ## Supported Tools
 
-The default server configuration exposes **110 tools**.
+The default server configuration exposes **150+ tools**.
 
 ### Custom Agentic Tools
 
@@ -433,41 +497,31 @@ The default server configuration exposes **110 tools**.
 ### OpenAPI-Generated Tools
 
 ```text
-attachAlert
-createAlert
-createEnvironment
-createEscalationLevel
-createEscalationLevelPaths
-createEscalationPath
-createEscalationPolicy
-createFunctionality
+ListWorkflowRuns
 createIncidentActionItem
 createIncidentFormFieldSelection
-createIncidentType
-createOnCallRole
-createOnCallShadow
-createOverrideShift
-createSchedule
-createScheduleRotation
-createScheduleRotationActiveDay
-createScheduleRotationUser
-createService
-createSeverity
-createTeam
-createWorkflow
 createWorkflowTask
-deleteEscalationLevel
-deleteEscalationPath
-deleteEscalationPolicy
-deleteSchedule
-deleteScheduleRotation
 getAlert
+getAlertEvent
+getAlertGroup
+getAlertRoutingRule
+getAlertSource
+getAlertUrgency
+getCatalog
+getCatalogEntity
+getCause
 getCurrentUser
+getCustomForm
 getEnvironment
 getEscalationLevel
 getEscalationPath
 getEscalationPolicy
+getFormField
+getFormFieldOption
 getFunctionality
+getFunctionalityIncidentsChart
+getFunctionalityUptimeChart
+getIncidentActionItems
 getIncidentFormFieldSelection
 getIncidentType
 getOnCallRole
@@ -477,22 +531,42 @@ getSchedule
 getScheduleRotation
 getScheduleShifts
 getService
+getServiceIncidentsChart
+getServiceUptimeChart
 getSeverity
+getStatusPage
+getStatusPageTemplate
 getTeam
+getTeamIncidentsChart
 getUser
 getWorkflow
+getWorkflowFormFieldCondition
+getWorkflowGroup
 getWorkflowTask
+listAlertEvents
+listAlertGroups
+listAlertRoutingRules
+listAlertSources
+listAlertUrgencies
 listAlerts
+listAllIncidentActionItems
+listCatalogEntities
+listCatalogs
+listCauses
+listCustomForms
 listEnvironments
 listEscalationLevels
 listEscalationLevelsPaths
 listEscalationPaths
 listEscalationPolicies
+listFormFieldOptions
+listFormFields
 listFunctionalities
 listIncidentActionItems
 listIncidentAlerts
 listIncidentFormFieldSelections
 listIncident_Types
+listIncidents
 listOnCallRoles
 listOnCallShadows
 listOverrideShifts
@@ -503,17 +577,19 @@ listSchedules
 listServices
 listSeverities
 listShifts
+listStatusPageTemplates
+listStatusPages
 listTeams
 listUsers
+listWorkflowFormFieldConditions
+listWorkflowGroups
 listWorkflows
 listWorkflowTasks
-updateAlert
 updateEnvironment
 updateEscalationLevel
 updateEscalationPath
 updateEscalationPolicy
 updateFunctionality
-updateIncidentFormFieldSelection
 updateIncidentType
 updateOnCallRole
 updateOnCallShadow
@@ -523,13 +599,14 @@ updateScheduleRotation
 updateService
 updateSeverity
 updateTeam
-updateUser
 updateWorkflow
+updateIncidentFormFieldSelection
 updateWorkflowTask
 ```
 
-Delete operations are intentionally scoped to screenshot coverage paths:
-`deleteSchedule`, `deleteScheduleRotation`, `deleteEscalationPolicy`, `deleteEscalationPath`, `deleteEscalationLevel`.
+**Major Expansion**: This version includes 50+ new endpoints covering communications, dashboards, playbooks, post-incident reviews, monitoring, and advanced form management - while carefully excluding security-sensitive operations like API key management, user creation/deletion, role management, and webhook configuration.
+
+Delete operations remain disabled in the default tool surface.
 
 ## On-Call Health Integration
 
@@ -626,6 +703,18 @@ Regional filtering shows only people on-call during business hours (9am-5pm) in
 
 Returns: `schedules` with `current_oncall`, `next_oncall`, and `shift_incidents`
 
+### MCP Resources for Context
+
+AI agents can access these resources for situational awareness:
+
+- **`incident://{incident_id}`** - Detailed incident information for specific incidents
+- **`team://{team_id}`** - Team details including name, color, and metadata  
+- **`rootly://incidents`** - List of recent incidents for quick reference
+- **`rootly://oncall-status`** - Current on-call status across all schedules (critical for incident response)
+- **`rootly://workflow-guide`** - Step-by-step workflow guidance for common operations
+
+Example usage: *"Check the current on-call status"* → AI reads `rootly://oncall-status` resource
+
 ### Shift Incidents
 
 Incidents during a time period, with filtering by severity/status/tags.

{rootly_mcp_server-2.2.22 → rootly_mcp_server-2.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rootly-mcp-server"
-version = "2.2.22"
+version = "2.3.0"
 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.12"