# Rootly MCP MCP Server

> **Rootly MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Rootly MCP.
>
> MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows,
> token refresh, and production-grade auto-scaling — so your AI agents can connect to
> third-party services and run freely without you managing any MCP server yourself.
>
> Server page:  https://mewcp.com/mcp/rootly-mcp
> MewCP docs:   https://docs.mewcp.com
> Full catalog: https://mewcp.com/llms.txt

---

## About

Rootly brings incident response and on-call operations into AI-assisted workflows. Investigate active and historical incidents, correlate alerts, identify available responders, review escalation schedules, find similar past outages, generate retrospectives, and manage incident workflows, services, and reliability metrics.

---

## Details

- Server ID: `rootly-mcp`
- Version: 4.1.4
- Tools: 273
- Authentication: OAuth, managed by MewCP
- Transport: http

---

## Access

The gateway URL below serves your **entire MewCP toolset**, not this server on its
own. Pasting a config snippet is not enough — Rootly MCP has to be in the toolset
first. In order:

1. Add Rootly MCP to your toolset at https://mewcp.com/mcp/rootly-mcp
2. Connect your Rootly MCP account (OAuth); MewCP stores the credential and attaches it to each call
3. Copy your MewCP API key from the dashboard (Developer)
4. Configure your client with the snippet for it below

Once connected, an agent does **not** see this server's tools as top-level tools.
It sees four meta-tools and reaches everything through them:

- `search(query)` — find tools by keyword across the toolset
- `get_schema(tools)` — full description and arguments for the tools you picked
- `list_accounts(provider)` — only when one app has several connected accounts
- `call_tool(server_maskedId, tool_name, args)` — execute

So the list below is what `search` can return for this server, not a set of
callable tool names on their own.

---

## Tools (273)

Descriptions are truncated to 160 characters; call `get_schema`
for the full text and the argument schema. Where a tool is annotated, its type
is shown — treat `destructive` as irreversible.

- `list_endpoints` _(read)_ — List all available Rootly API endpoints with their descriptions.
- `get_server_version` _(read)_ — Get the Rootly MCP server version. Returns the current version of the deployed MCP server. Useful for checking if the server has been updated.
- `list_incidents` _(read)_ — 🚨 List incidents with structured filters - ESSENTIAL for incident response. WHEN TO USE: • During incident response to check for related ongoing incidents •…
- `collect_incidents` _(read)_ — Collect a bounded working set of incidents across multiple pages for audits and analysis. Use this instead of list_incidents when you want a compact batch of…
- `search_incidents` _(read)_ — Search incidents with flexible pagination control. Use page_number=0 to fetch all matching results across multiple pages. Use page_number>0 to fetch a specific…
- `get_incident` _(read)_ — Retrieve a single incident with PIR-related fields for direct verification.
- `get_incident_retrospective` _(read)_ — Fetch the written retrospective for one incident. Answers "what did we learn from INC-4460" in a single call. Returns the document's title, content and status…
- `list_incident_post_mortems` _(read)_ — Browse retrospectives across incidents. Answers "the last five retrospectives", "published ones for this team since June", or "how many are still draft". Each…
- `list_incident_roles` _(read)_ — List role assignments for an incident (who is Commander, Scribe, etc.). Returns one entry per defined role with role metadata and the assigned user (or…
- `get_incident_meeting_transcripts` _(read)_ — Read what was said on an incident's calls (Rootly Meeting Scribe). Returns the spoken transcript of each recorded call for the incident, as text per speaker…
- `create_incident` _(write)_ — Create an incident with a scoped set of fields for agent-driven workflows.
- `update_incident` _(write)_ — Update native incident fields via ``PUT /v1/incidents/{id}``. Only the arguments you provide are sent, so unspecified fields — including the lifecycle…
- `find_related_incidents` _(read)_ — 🔍 Find historically similar incidents using ML similarity analysis - CRITICAL for incident response. WHEN TO USE: • EARLY in incident response to learn from…
- `suggest_solutions` _(read)_ — 💡 Get actionable solution recommendations from similar resolved incidents - KEY for incident response. WHEN TO USE: • AFTER find_related_incidents to get…
- `get_oncall_shift_metrics` _(read)_ — 📊 Get on-call workload metrics and shift statistics - ESSENTIAL for fairness and planning. WHEN TO USE: • Monthly/quarterly reviews of on-call distribution •…
- `get_oncall_handoff_summary` _(read)_ — Get current on-call handoff summary. Shows who's currently on-call and who's next. Optionally fetch incidents (set include_incidents=True, but slower). Each…
- `get_shift_incidents` _(read)_ — Get incidents and alerts that occurred during a specific shift or time period. Useful for: - Shift handoff summaries showing what happened during the shift -…
- `get_schedule_shifts` _(read)_ — List shifts for one schedule over a date range. Replaces the generated getScheduleShifts, which passed the range straight through and failed with `Datetime…
- `list_shifts` _(read)_ — List on-call shifts with reliable filtering, enrichment, and MCP-level pagination. Unlike the raw API, this tool: - Actually filters by user_ids (client-side…
- `get_oncall_schedule_summary` _(read)_ — Get compact on-call schedule summary for a date range. Returns one entry per user per schedule (not raw shifts), with aggregated hours. Optimized for AI agent…
- `check_responder_availability` _(read)_ — Check if specific users are scheduled for on-call in a date range. Use this to verify if at-risk users (from On-Call Health) are scheduled, or to check…
- `create_override_recommendation` _(read)_ — Recommend replacement responders for an override shift. Finds users in the same schedule rotation who are not already heavily loaded during the period. Returns…
- `get_alert_by_short_id` _(read)_ — Get alert details by short_id or alert URL. Use this when a user pastes an alert URL or short_id from a pager notification and wants to investigate the alert.
- `list_audits` _(read)_ — Read the Rootly audit log: who changed which configuration object, when, and what changed. Each record carries the action, the acting user, the source, and the…
- `list_investigations` _(read)_ — List AI SRE investigations you can see, newest first.
- `get_investigation` _(read)_ — Get an investigation's verdict: summary, root cause, confidence, hypotheses, evidence, causal chain and open_questions (what Rootly couldn't verify, so you can…
- `get_investigation_progress` _(read)_ — Follow a running investigation. Returns new steps and tool calls since after_cursor, waiting up to wait_seconds for them. Keep calling with…
- `start_investigation` _(write)_ — Start an AI SRE investigation on one alert or incident. Then follow it with get_investigation_progress.
- `cancel_investigation` _(destructive)_ — Cancel a running investigation.
- `list_alert_events` _(read)_ — List alert_events
- `create_alert_event` _(write)_ — Creates a new alert event
- `get_alert_event` _(read)_ — Retrieves a specific alert_event by id
- `update_alert_event` _(write)_ — Updates a specific alert event. Only alert events with kind 'note' (user-created notes) can be updated. System-generated events are immutable to maintain audit…
- `list_alert_groups` _(read)_ — List alert groups
- `create_alert_group` _(write)_ — Creates a new alert group. **Note**: For enhanced functionality and future compatibility, consider using the advanced alert grouping with `conditions` field…
- `get_alert_group` _(read)_ — Retrieves a specific alert group by id
- `update_alert_group` _(write)_ — Update a specific alert group by id. **Note**: For enhanced functionality and future compatibility, consider using the advanced alert grouping with…
- `list_alert_routes` _(read)_ — List all alert routes for the current team with filtering and pagination. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure…
- `create_alert_route` _(write)_ — Creates a new alert route from provided data. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this…
- `get_alert_route` _(read)_ — Get a specific alert route by id. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this feature,…
- `update_alert_route` _(write)_ — Update a specific alert route by id. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this feature,…
- `patch_alert_route` _(write)_ — Updates an alert route. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this feature, please…
- `list_alert_routing_rules` _(read)_ — List alert routing rules. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this endpoint. If you don't…
- `create_alert_routing_rule` _(write)_ — Creates a new alert routing rule from provided data. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of…
- `get_alert_routing_rule` _(read)_ — Retrieves a specific alert routing rule by id. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this…
- `update_alert_routing_rule` _(write)_ — Update a specific alert routing rule by id. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this…
- `list_alert_urgencies` _(read)_ — List alert urgencies
- `create_alert_urgency` _(write)_ — Creates a new alert urgency from provided data
- `get_alert_urgency` _(read)_ — Retrieves a specific alert urgency by id
- `update_alert_urgency` _(write)_ — Update a specific alert urgency by id
- `list_alerts_sources` _(read)_ — List alert sources
- `create_alerts_source` _(write)_ — Creates a new alert source from provided data
- `get_alerts_source` _(read)_ — Retrieves a specific alert source by id
- `update_alerts_source` _(write)_ — Update a specific alert source by id
- `list_incident_alerts` _(read)_ — List incident alerts
- `attach_alert` _(write)_ — Attach alerts to an incident from provided data
- `list_alerts` _(read)_ — List alerts
- `create_alert` _(write)_ — Creates a new alert from provided data
- `get_alert` _(read)_ — Retrieves a specific alert by id
- `update_alert` _(write)_ — Updates an alert
- `list_catalog_entities` _(read)_ — List Catalog Entities
- `create_catalog_entity` _(write)_ — Creates a new Catalog Entity from provided data
- `get_catalog_entity` _(read)_ — Retrieves a specific Catalog Entity by id
- `update_catalog_entity` _(write)_ — Update a specific Catalog Entity by id
- `list_catalog_entity_properties` _(read)_ — **Deprecated:** This endpoint is deprecated, please use `include=fields` on catalog entities or native catalog endpoints (teams, services, functionalities,…
- `create_catalog_entity_property` _(write)_ — **Deprecated:** This endpoint is deprecated, please use the `fields` attribute on catalog entities or native catalog endpoints (teams, services,…
- `get_catalog_entity_property` _(read)_ — **Deprecated:** This endpoint is deprecated, please use `include=fields` on catalog entities or native catalog endpoints (teams, services, functionalities,…
- `update_catalog_entity_property` _(write)_ — **Deprecated:** This endpoint is deprecated, please use the `fields` attribute on catalog entities or native catalog endpoints (teams, services,…
- `list_catalog_properties` _(read)_ — List Catalog Properties - returns catalog_properties type
- `create_catalog_property` _(write)_ — Creates a new Catalog Property - returns catalog_properties type
- `get_catalog_property` _(read)_ — Retrieves a specific Catalog Property by id - returns catalog_properties type
- `update_catalog_property` _(write)_ — Update a specific catalog_property by id - returns catalog_properties type
- `list_catalogs` _(read)_ — List catalogs
- `create_catalog` _(write)_ — Creates a new catalog from provided data
- `get_catalog` _(read)_ — Retrieves a specific catalog by id
- `update_catalog` _(write)_ — Update a specific catalog by id
- `list_causes` _(read)_ — List causes
- `create_cause` _(write)_ — Creates a new cause from provided data
- `get_cause` _(read)_ — Retrieves a specific cause by id
- `update_cause` _(write)_ — Update a specific cause by id
- `get_custom_field_option` _(read)_ — [DEPRECATED] Use form field endpoints instead. Retrieves a specific custom field option by id
- `update_custom_field_option` _(write)_ — [DEPRECATED] Use form field endpoints instead. Update a specific custom field option by id
- `list_custom_fields` _(read)_ — [DEPRECATED] Use form field endpoints instead. List Custom fields
- `create_custom_field` _(write)_ — [DEPRECATED] Use form field endpoints instead. Creates a new custom field from provided data
- `get_custom_field` _(read)_ — Retrieves a specific custom_field by id
- `update_custom_field` _(write)_ — [DEPRECATED] Use form field endpoints instead. Update a specific custom field by id
- `list_custom_forms` _(read)_ — List custom forms
- `create_custom_form` _(write)_ — Creates a new custom form from provided data
- `get_custom_form` _(read)_ — Retrieves a specific custom form by id
- `update_custom_form` _(write)_ — Update a specific custom form by id
- `get_dashboard_panel` _(read)_ — Retrieves a specific dashboard panel by id
- `update_dashboard_panel` _(write)_ — Update a specific dashboard panel by id
- `list_dashboards` _(read)_ — List dashboards
- `create_dashboard` _(write)_ — Creates a new dashboard from provided data
- `get_dashboard` _(read)_ — Retrieves a specific dashboard by id
- `update_dashboard` _(write)_ — Update a specific dashboard by id
- `list_environments` _(read)_ — List environments
- `create_environment` _(write)_ — Creates a new environment from provided data
- `get_environment` _(read)_ — Retrieves a specific environment by id
- `update_environment` _(write)_ — Update a specific environment by id
- `list_escalation_policies` _(read)_ — List escalation policies
- `create_escalation_policy` _(write)_ — Creates a new escalation policy from provided data
- `get_escalation_policy` _(read)_ — Retrieves a specific escalation policy by id
- `update_escalation_policy` _(write)_ — Update a specific escalation policy by id
- `list_escalation_levels` _(read)_ — List escalation levels
- `create_escalation_level` _(write)_ — Creates a new escalation level from provided data
- `list_escalation_levels_paths` _(read)_ — List escalation levels
- `create_escalation_level_paths` _(write)_ — Creates a new escalation level from provided data
- `get_escalation_level` _(read)_ — Retrieves a specific escalation level by id
- `update_escalation_level` _(write)_ — Update a specific escalation level by id
- `list_escalation_paths` _(read)_ — List escalation paths
- `create_escalation_path` _(write)_ — Creates a new escalation path from provided data
- `get_escalation_path` _(read)_ — Retrieves a specific escalation path by id
- `update_escalation_path` _(write)_ — Update a specific escalation path by id
- `list_form_field_options` _(read)_ — List form_field_options
- `create_form_field_option` _(write)_ — Creates a new form_field_option from provided data
- `get_form_field_option` _(read)_ — Retrieves a specific form_field_option by id
- `update_form_field_option` _(write)_ — Update a specific form_field_option by id
- `get_form_field_placement_condition` _(read)_ — Retrieves a specific form_field_placement_condition by id
- `update_form_field_placement_condition` _(write)_ — Update a specific form_field_placement_condition by id
- `get_form_field_placement` _(read)_ — Retrieves a specific form_field_placement by id
- `update_form_field_placement` _(write)_ — Update a specific form_field_placement by id
- `list_form_fields` _(read)_ — List form_fields
- `create_form_field` _(write)_ — Creates a new form_field from provided data
- `get_form_field` _(read)_ — Retrieves a specific form_field by id
- `update_form_field` _(write)_ — Update a specific form_field by id
- `get_form_set_condition` _(read)_ — Retrieves a specific form_set_condition by id
- `update_form_set_condition` _(write)_ — Update a specific form_set_condition by id
- `list_form_sets` _(read)_ — List form_sets. Without `filter[resource_type]`, returns incident form sets and, when Problem Management is enabled, problem form sets. Pass…
- `create_form_set` _(write)_ — Creates a new form_set from provided data
- `get_form_set` _(read)_ — Retrieves a specific form_set by id
- `update_form_set` _(write)_ — Update a specific form_set by id
- `list_functionalities` _(read)_ — List functionalities
- `create_functionality` _(write)_ — Creates a new functionality from provided data
- `get_functionality` _(read)_ — Retrieves a specific functionality by id
- `update_functionality` _(write)_ — Update a specific functionality by id
- `get_functionality_incidents_chart` _(read)_ — Get functionality incidents chart
- `get_functionality_uptime_chart` _(read)_ — Get functionality uptime chart
- `list_workflow_tasks` _(read)_ — List workflow tasks
- `create_workflow_task` _(write)_ — Creates a new workflow task from provided data
- `get_workflow_task` _(read)_ — Retrieves a specific workflow_task by id
- `update_workflow_task` _(write)_ — Update a specific workflow task by id
- `list_workflow_form_field_conditions` _(read)_ — List workflow form field conditions
- `create_workflow_form_field_condition` _(write)_ — Creates a new workflow form field condition from provided data
- `get_workflow_form_field_condition` _(read)_ — Retrieves a specific workflow form field condition by id
- `update_workflow_form_field_condition` _(write)_ — Update a specific workflow form field condition by id
- `list_workflow_groups` _(read)_ — List workflow groups
- `create_workflow_group` _(write)_ — Creates a new workflow group from provided data
- `get_workflow_group` _(read)_ — Retrieves a specific workflow group by id
- `update_workflow_group` _(write)_ — Update a specific workflow group by id
- `list_workflow_runs` _(read)_ — List workflow runs
- `create_workflow_run` _(write)_ — Creates a new workflow run from provided data
- `list_workflows` _(read)_ — List workflows
- `create_workflow` _(write)_ — Creates a new workflow from provided data
- `get_workflow` _(read)_ — Retrieves a specific workflow by id
- `update_workflow` _(write)_ — Update a specific workflow by id
- `list_heartbeats` _(read)_ — List heartbeats
- `create_heartbeat` _(write)_ — Creates a new heartbeat from provided data
- `get_heartbeat` _(read)_ — Retrieves a specific heartbeat by id
- `update_heartbeat` _(write)_ — Update a specific heartbeat by id
- `list_incident_action_items` _(read)_ — List incident action items
- `create_incident_action_item` _(write)_ — Creates a new action item from provided data
- `get_incident_action_items` _(read)_ — Retrieves a specific incident_action_item by id
- `update_incident_action_item` _(write)_ — Update a specific incident action item by id
- `list_all_incident_action_items` _(read)_ — List all action items for an organization
- `list_incident_custom_field_selections` _(read)_ — [DEPRECATED] Use form field endpoints instead. List incident custom field selections
- `create_incident_custom_field_selection` _(write)_ — [DEPRECATED] Use form field endpoints instead. Creates a new incident custom field selection from provided data
- `get_incident_custom_field_selection` _(read)_ — [DEPRECATED] Use form field endpoints instead. Retrieves a specific incident custom field selection by id
- `update_incident_custom_field_selection` _(write)_ — [DEPRECATED] Use form field endpoints instead. Update a specific incident custom field selection by id
- `list_incident_events` _(read)_ — List incident events
- `create_incident_event` _(write)_ — Creates a new event from provided data
- `list_incident_form_field_selections` _(read)_ — List incident form field selections
- `create_incident_form_field_selection` _(write)_ — Creates a new incident form field selection from provided data
- `get_incident_form_field_selection` _(read)_ — Retrieves a specific incident form field selection by id
- `update_incident_form_field_selection` _(write)_ — Update a specific incident form field selection by id
- `get_incident_retrospective_step` _(read)_ — Retrieves a specific incident retrospective step by id
- `update_incident_retrospective_step` _(write)_ — Update a specific incident retrospective step by id
- `get_incident_sub_status` _(read)_ — Retrieves a specific incident_sub_status by id
- `update_incident_sub_status` _(write)_ — Update a specific incident_sub_status by id
- `list_incident_types` _(read)_ — List incident types
- `create_incident_type` _(write)_ — Creates a new incident_type from provided data
- `get_incident_type` _(read)_ — Retrieves a specific incident_type by id
- `update_incident_type` _(write)_ — Update a specific incident_type by id
- `list_live_call_routers` _(read)_ — List Live Call Routers
- `create_live_call_router` _(write)_ — Creates a new Live Call Router from provided data
- `get_live_call_router` _(read)_ — Retrieves a specific Live Call Router by id
- `update_live_call_router` _(write)_ — Update a specific Live Call Router by id
- `list_meeting_recordings` _(read)_ — List all meeting recording sessions for an incident. Returns recordings sorted by session number. Each recording represents one bot session with its own…
- `list_all_meeting_recordings` _(read)_ — List meeting recordings across the organization. Returns the current user's standalone recordings plus incident-backed recordings the user can access. Supports…
- `get_meeting_recording` _(read)_ — Retrieve a single meeting recording session including its status, duration, speaker count, word count, and transcript summary.
- `list_observability_logs` _(read)_ — Search Rootly Observability logs with the Logs explorer query syntax (`service:`, `severity:`, `index:`, `trace_id:`, `@attribute:value`, `OR` inside field…
- `list_observability_patterns` _(read)_ — List log patterns (clustered log templates) with counts against the previous window of the same length. Only `service:`, `severity:` and `pattern:` filters…
- `count_observability_logs` _(read)_ — Count logs matching a Logs explorer query, grouped by `service`, `index`, `severity` or an attribute key (`@http.status_code`). Answers questions like "errors…
- `list_on_call_roles` _(read)_ — List On-Call Roles
- `create_on_call_role` _(write)_ — Creates a new On-Call Role from provided data
- `get_on_call_role` _(read)_ — Retrieves a specific On-Call Role by id
- `update_on_call_role` _(write)_ — Update a specific On-Call Role by id
- `list_on_call_shadows` _(read)_ — List shadow shifts for schedule
- `create_on_call_shadow` _(write)_ — Creates a new on call shadow configuration from provided data
- `get_on_call_shadow` _(read)_ — Retrieves a specific On Call Shadow configuration by ID
- `update_on_call_shadow` _(write)_ — Update a specific on call shadow configuration by id
- `list_override_shifts` _(read)_ — List override shifts
- `create_override_shift` _(write)_ — Creates a new override shift from provided data. If any existing override shifts overlap with the specified time range, they will be automatically deleted and…
- `get_override_shift` _(read)_ — Retrieves a specific override shift by id
- `update_override_shift` _(write)_ — Update a specific override shift by id
- `get_playbook_task` _(read)_ — Retrieves a specific playbook_task by id
- `update_playbook_task` _(write)_ — Update a specific playbook task by id
- `list_playbooks` _(read)_ — List playbooks
- `create_playbook` _(write)_ — Creates a new playbook from provided data
- `get_playbook` _(read)_ — Retrieves a specific playbook by id
- `update_playbook` _(write)_ — Update a specific playbook by id
- `list_pulses` _(read)_ — List pulses
- `create_pulse` _(write)_ — Creates a new pulse from provided data
- `get_pulse` _(read)_ — Retrieves a specific pulse by id
- `update_pulse` _(write)_ — Update a specific pulse by id
- `get_retrospective_process_group` _(read)_ — Retrieves a specific Retrospective Process Group by id
- `update_retrospective_process_group` _(write)_ — Update a specific Retrospective Process Group by id
- `list_retrospective_processes` _(read)_ — List retrospective processes
- `create_retrospective_process` _(write)_ — Creates a new retrospective process from provided data
- `get_retrospective_process` _(read)_ — Retrieves a specific retrospective process by id
- `update_retrospective_process` _(write)_ — Updates a specific retrospective process by id
- `get_retrospective_step` _(read)_ — Retrieves a specific retrospective step by id
- `update_retrospective_step` _(write)_ — Update a specific retrospective step by id
- `list_schedule_rotation_active_days` _(read)_ — List schedule rotation active days
- `create_schedule_rotation_active_day` _(write)_ — Creates a new schedule rotation active day from provided data
- `list_schedule_rotation_users` _(read)_ — List schedule rotation users
- `create_schedule_rotation_user` _(write)_ — Creates a new schedule rotation user from provided data
- `list_schedule_rotations` _(read)_ — List schedule rotations
- `create_schedule_rotation` _(write)_ — Creates a new schedule rotation from provided data
- `get_schedule_rotation` _(read)_ — Retrieves a specific schedule rotation by id
- `update_schedule_rotation` _(write)_ — Update a specific schedule rotation by id
- `list_schedules` _(read)_ — List schedules
- `create_schedule` _(write)_ — Creates a new schedule from provided data
- `get_schedule` _(read)_ — Retrieves a specific schedule by id
- `update_schedule` _(write)_ — Updates a specific schedule by id
- `list_services` _(read)_ — List services
- `create_service` _(write)_ — Creates a new service from provided data
- `get_service` _(read)_ — Retrieves a specific service by id
- `update_service` _(write)_ — Update a specific service by id
- `get_service_incidents_chart` _(read)_ — Get service incidents chart
- `get_service_uptime_chart` _(read)_ — Get service uptime chart
- `list_severities` _(read)_ — List severities
- `create_severity` _(write)_ — Creates a new severity from provided data
- `get_severity` _(read)_ — Retrieves a specific severity by id
- `update_severity` _(write)_ — Update a specific severity by id
- `list_shift_coverage_requests` _(read)_ — List active shift coverage requests for a schedule.
- `get_shift_coverage_request` _(read)_ — Retrieves a specific shift coverage request.
- `list_status_page_templates` _(read)_ — List status page templates
- `create_status_page_template` _(write)_ — Creates a new template from provided data
- `get_status_page_template` _(read)_ — Retrieves a specific status_page_template by id
- `update_status_page_template` _(write)_ — Update a specific template event by id
- `list_status_pages` _(read)_ — List status pages
- `create_status_page` _(write)_ — Creates a new status page from provided data
- `get_status_page` _(read)_ — Retrieves a specific status page by id
- `update_status_page` _(write)_ — Update a specific status page by id
- `list_sub_statuses` _(read)_ — List Sub-Statuses
- `create_sub_status` _(write)_ — Creates a new Sub-Status from provided data
- `get_sub_status` _(read)_ — Retrieves a specific Sub-Status by id
- `update_sub_status` _(write)_ — Update a specific Sub-Status by id
- `list_teams` _(read)_ — List teams
- `create_team` _(write)_ — Creates a new team from provided data
- `get_team` _(read)_ — Retrieves a specific team by id
- `update_team` _(write)_ — Update a specific team by id
- `get_team_incidents_chart` _(read)_ — Get team incidents chart
- `get_user_email_addresses` _(read)_ — Retrieves all email addresses for the specified user
- `create_user_email_address` _(write)_ — Creates a new user email address from provided data
- `list_user_notification_rules` _(read)_ — List user notification rules
- `create_user_notification_rule` _(write)_ — Creates a new user notification rule from provided data
- `get_user_phone_numbers` _(read)_ — Retrieves all phone numbers for the specified user
- `create_user_phone_number` _(write)_ — Creates a new user phone number from provided data
- `list_users` _(read)_ — List users
- `get_current_user` _(read)_ — Get current user
- `get_user` _(read)_ — Retrieves a specific user by id

---

## Connect

Gateway URL: https://gateway.mewcp.com/personal/mcp

Every request carries one header:

    Authorization: Bearer <API_KEY>

Replace `API_KEY` with your own key from the dashboard (Developer).

## Apps

### Claude Desktop

Mac & Windows app

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open Claude Desktop → Settings → Developer → "Edit Config"
2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
3. Save the file, then quit Claude Desktop completely and reopen it
4. Start a new conversation — your tool will be available

### VS Code

Copilot / Cline

- Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead.

```json
{
  "mcp.servers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have a "servers" section in your mcp.json? Just add the server entry inside it.

1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
2. Run "MCP: Open User Configuration" to open your mcp.json
3. Paste the snippet and save
4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat

### Cursor

AI-first editor

- macOS: `~/.cursor/mcp.json`
- Windows: `%USERPROFILE%\.cursor\mcp.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it.

1. Open Cursor → Settings → Cursor Settings → MCP
2. Click "Add new global MCP server"
3. Paste the snippet and save
4. Restart Cursor

### Codex

OpenAI's CLI agent

- Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers.

1. Open your Codex MCP config or project-level config file
2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects
3. Save the file and restart Codex
4. Verify the tool is available inside a fresh session

### Claude Code

Anthropic's CLI agent

- ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file and start (or restart) Claude Code
4. Or skip the file entirely and run the CLI command below instead

### OpenCode

Open-source terminal agent

- ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist.

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mewcp": {
      "type": "remote",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcp" section in your opencode.json? Just add the server entry inside it.

1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and start (or restart) OpenCode

### OpenClaw

Self-hosted agent gateway

- ~/.openclaw/openclaw.json — create it if it doesn't exist.

```json
{
  "mcp": {
    "servers": {
      "mewcp": {
        "transport": "streamable-http",
        "url": "https://gateway.mewcp.com/personal/mcp",
        "enabled": true,
        "headers": {
          "Authorization": "Bearer API_KEY"
        }
      }
    }
  }
}
```

Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers".

1. Open ~/.openclaw/openclaw.json in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and restart OpenClaw

### Antigravity

Google's agentic IDE

- ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist.

```json
{
  "mcpServers": {
    "mewcp": {
      "serverUrl": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported.

1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager)
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file — the server connects automatically

### Hermes

Nous Research's CLI agent

- config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key.

```yaml
mcp_servers:
  mewcp:
    url: "https://gateway.mewcp.com/personal/mcp"
    headers:
      Authorization: "Bearer API_KEY"
```

Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it.

1. Open config.yaml in your Hermes config directory
2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any)
3. Save the file, then run /reload-mcp in Hermes (or start a fresh session)
4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected

### DeepSeek Harness

DeepSeek's agent harness

- cordis.yml in your DSH project — or the patch file you mount plugins from.

```yaml
- id: mcp-mewcp
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: mewcp
    transport: streamable-http
    url: https://gateway.mewcp.com/personal/mcp
    headers:
      Authorization: "Bearer API_KEY"
```

One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry.

1. Open cordis.yml (or your patch file) in your DSH project
2. Paste the entry into your plugin list, keeping the leading dash and indentation
3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__<tool_name>
4. Verify with: dsh web --dump-config | grep -A3 mcp

## SDKs

### Python

fastmcp client

```python
import asyncio
from fastmcp import Client
from fastmcp.client.transports import StreamableHttpTransport

SERVER_URL = "https://gateway.mewcp.com/personal/mcp"
API_KEY = "API_KEY"

transport = StreamableHttpTransport(
    url=SERVER_URL,
    headers={
        "Authorization": f"Bearer {API_KEY}",
    }
)

async def main():
    client = Client(transport)
    async with client:
        tools = await client.list_tools()
        print(tools)

asyncio.run(main())
```

1. Install fastmcp: pip install fastmcp
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run your script

### TypeScript

MCP SDK

```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const SERVER_URL = "https://gateway.mewcp.com/personal/mcp";
const API_KEY = "API_KEY";

const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), {
  requestInit: {
    headers: {
      Authorization: `Bearer ${API_KEY}`,
    },
  },
});

const client = new Client({ name: "mewcp-client", version: "1.0.0" });
await client.connect(transport);

const tools = await client.listTools();
console.log(tools.tools.map((t) => t.name));
```

1. Install: npm install @modelcontextprotocol/sdk
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)