# Oneuptime MCP MCP Server > **Oneuptime MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Oneuptime 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/oneuptime-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About OneUptime MCP Server enables AI agents to manage monitoring, incidents, alerts, status pages, on-call operations, and observability data through OneUptime. --- ## Details - Server ID: `oneuptime-mcp` - Version: 1.0.0 - Tools: 169 - Authentication: None — this server takes no credential - 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 — Oneuptime MCP has to be in the toolset first. In order: 1. Add Oneuptime MCP to your toolset at https://mewcp.com/mcp/oneuptime-mcp 2. Nothing to connect — Oneuptime MCP needs no credential 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 (169) 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. - `create_team` _(write)_ — Create a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your… - `get_team` _(read)_ — Retrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID. - `list_teams` _(read)_ — List and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count. - `update_team` _(write)_ — Update an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the… - `delete_team` _(destructive)_ — Permanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_teams` _(read)_ — Count the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if… - `create_label` _(write)_ — Create a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from… - `get_label` _(read)_ — Retrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID. - `list_labels` _(read)_ — List and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count. - `update_label` _(write)_ — Update an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see… - `delete_label` _(destructive)_ — Permanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_labels` _(read)_ — Count the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if… - `create_status_page` _(write)_ — Create a new Status Page in OneUptime. Returns the created Status Page object with its ID. Use this to add new Status Pages to your project. Note: projectId is… - `get_status_page` _(read)_ — Retrieve a single Status Page by its unique ID from OneUptime. Use list_status_pages first if you need to find the ID. - `list_status_pages` _(read)_ — List and search Status Pages from OneUptime with optional filtering, pagination, and sorting. Returns an array of Status Page objects plus the total matching… - `update_status_page` _(write)_ — Update an existing Status Page in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_status_page… - `delete_status_page` _(destructive)_ — Permanently delete a Status Page from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_status_pages` _(read)_ — Count the total number of Status Pages in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_on_call_policy` _(write)_ — Create a new On-Call Policy in OneUptime. Returns the created On-Call Policy object with its ID. Use this to add new On-Call Duty Policies to your project.… - `get_on_call_policy` _(read)_ — Retrieve a single On-Call Policy by its unique ID from OneUptime. Use list_on_call_duty_policies first if you need to find the ID. - `list_on_call_duty_policies` _(read)_ — List and search On-Call Duty Policies from OneUptime with optional filtering, pagination, and sorting. Returns an array of On-Call Policy objects plus the… - `update_on_call_policy` _(write)_ — Update an existing On-Call Policy in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_on_call_policy… - `delete_on_call_policy` _(destructive)_ — Permanently delete a On-Call Policy from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_on_call_duty_policies` _(read)_ — Count the total number of On-Call Duty Policies in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports,… - `create_monitor` _(write)_ — Create a new Monitor in OneUptime. Returns the created Monitor object with its ID. Use this to add new Monitors to your project. Note: projectId is inferred… - `get_monitor` _(read)_ — Retrieve a single Monitor by its unique ID from OneUptime. Use list_monitors first if you need to find the ID. - `list_monitors` _(read)_ — List and search Monitors from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor objects plus the total matching count. - `update_monitor` _(write)_ — Update an existing Monitor in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor afterwards to… - `delete_monitor` _(destructive)_ — Permanently delete a Monitor from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_monitors` _(read)_ — Count the total number of Monitors in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if… - `create_monitor_status` _(write)_ — Create a new Monitor Status in OneUptime. Returns the created Monitor Status object with its ID. Use this to add new Monitor Statuses to your project. Note:… - `get_monitor_status` _(read)_ — Retrieve a single Monitor Status by its unique ID from OneUptime. Use list_monitor_statuses first if you need to find the ID. - `list_monitor_statuses` _(read)_ — List and search Monitor Statuses from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor Status objects plus the total… - `update_monitor_status` _(write)_ — Update an existing Monitor Status in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor_status… - `delete_monitor_status` _(destructive)_ — Permanently delete a Monitor Status from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_monitor_statuses` _(read)_ — Count the total number of Monitor Statuses in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_incident_state` _(write)_ — Create a new Incident State in OneUptime. Returns the created Incident State object with its ID. Use this to add new Incident States to your project. Note:… - `get_incident_state` _(read)_ — Retrieve a single Incident State by its unique ID from OneUptime. Use list_incident_states first if you need to find the ID. - `list_incident_states` _(read)_ — List and search Incident States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident State objects plus the total… - `update_incident_state` _(write)_ — Update an existing Incident State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_state… - `delete_incident_state` _(destructive)_ — Permanently delete a Incident State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_states` _(read)_ — Count the total number of Incident States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_incident` _(write)_ — Create a new Incident in OneUptime. Returns the created Incident object with its ID. Use this to add new Incidents to your project. Note: projectId is inferred… - `get_incident` _(read)_ — Retrieve a single Incident by its unique ID from OneUptime. Use list_incidents first if you need to find the ID. - `list_incidents` _(read)_ — List and search Incidents from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident objects plus the total matching count. - `update_incident` _(write)_ — Update an existing Incident in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident afterwards to… - `delete_incident` _(destructive)_ — Permanently delete a Incident from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incidents` _(read)_ — Count the total number of Incidents in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking… - `create_incident_state_timeline` _(write)_ — Create a new Incident State Timeline in OneUptime. Returns the created Incident State Timeline object with its ID. Use this to add new Incident State Timelines… - `get_incident_state_timeline` _(read)_ — Retrieve a single Incident State Timeline by its unique ID from OneUptime. Use list_incident_state_timelines first if you need to find the ID. - `list_incident_state_timelines` _(read)_ — List and search Incident State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident State Timeline objects… - `update_incident_state_timeline` _(write)_ — Update an existing Incident State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_incident_state_timeline` _(destructive)_ — Permanently delete a Incident State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_state_timelines` _(read)_ — Count the total number of Incident State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards,… - `create_incident_internal_note` _(write)_ — Create a new Incident Internal Note in OneUptime. Returns the created Incident Internal Note object with its ID. Use this to add new Incident Internal Notes to… - `get_incident_internal_note` _(read)_ — Retrieve a single Incident Internal Note by its unique ID from OneUptime. Use list_incident_internal_notes first if you need to find the ID. - `list_incident_internal_notes` _(read)_ — List and search Incident Internal Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Internal Note objects… - `update_incident_internal_note` _(write)_ — Update an existing Incident Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_incident_internal_note` _(destructive)_ — Permanently delete a Incident Internal Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_internal_notes` _(read)_ — Count the total number of Incident Internal Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports,… - `create_incident_public_note` _(write)_ — Create a new Incident Public Note in OneUptime. Returns the created Incident Public Note object with its ID. Use this to add new Incident Public Notes to your… - `get_incident_public_note` _(read)_ — Retrieve a single Incident Public Note by its unique ID from OneUptime. Use list_incident_public_notes first if you need to find the ID. - `list_incident_public_notes` _(read)_ — List and search Incident Public Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Public Note objects plus… - `update_incident_public_note` _(write)_ — Update an existing Incident Public Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_incident_public_note` _(destructive)_ — Permanently delete a Incident Public Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_public_notes` _(read)_ — Count the total number of Incident Public Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports,… - `create_incident_severity` _(write)_ — Create a new Incident Severity in OneUptime. Returns the created Incident Severity object with its ID. Use this to add new Incident Severities to your project.… - `get_incident_severity` _(read)_ — Retrieve a single Incident Severity by its unique ID from OneUptime. Use list_incident_severities first if you need to find the ID. - `list_incident_severities` _(read)_ — List and search Incident Severities from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Severity objects plus the… - `update_incident_severity` _(write)_ — Update an existing Incident Severity in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_incident_severity` _(destructive)_ — Permanently delete a Incident Severity from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_severities` _(read)_ — Count the total number of Incident Severities in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_alert_state` _(write)_ — Create a new Alert State in OneUptime. Returns the created Alert State object with its ID. Use this to add new Alert States to your project. Note: projectId is… - `get_alert_state` _(read)_ — Retrieve a single Alert State by its unique ID from OneUptime. Use list_alert_states first if you need to find the ID. - `list_alert_states` _(read)_ — List and search Alert States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert State objects plus the total matching… - `update_alert_state` _(write)_ — Update an existing Alert State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_state… - `delete_alert_state` _(destructive)_ — Permanently delete a Alert State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_alert_states` _(read)_ — Count the total number of Alert States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_alert` _(write)_ — Create a new Alert in OneUptime. Returns the created Alert object with its ID. Use this to add new Alerts to your project. Note: projectId is inferred from… - `get_alert` _(read)_ — Retrieve a single Alert by its unique ID from OneUptime. Use list_alerts first if you need to find the ID. - `list_alerts` _(read)_ — List and search Alerts from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert objects plus the total matching count. - `update_alert` _(write)_ — Update an existing Alert in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert afterwards to see… - `delete_alert` _(destructive)_ — Permanently delete a Alert from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_alerts` _(read)_ — Count the total number of Alerts in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if… - `create_alert_state_timeline` _(write)_ — Create a new Alert State Timeline in OneUptime. Returns the created Alert State Timeline object with its ID. Use this to add new Alert State Timelines to your… - `get_alert_state_timeline` _(read)_ — Retrieve a single Alert State Timeline by its unique ID from OneUptime. Use list_alert_state_timelines first if you need to find the ID. - `list_alert_state_timelines` _(read)_ — List and search Alert State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert State Timeline objects plus… - `update_alert_state_timeline` _(write)_ — Update an existing Alert State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_alert_state_timeline` _(destructive)_ — Permanently delete a Alert State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_alert_state_timelines` _(read)_ — Count the total number of Alert State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports,… - `create_alert_internal_note` _(write)_ — Create a new Alert Internal Note in OneUptime. Returns the created Alert Internal Note object with its ID. Use this to add new Alert Internal Notes to your… - `get_alert_internal_note` _(read)_ — Retrieve a single Alert Internal Note by its unique ID from OneUptime. Use list_alert_internal_notes first if you need to find the ID. - `list_alert_internal_notes` _(read)_ — List and search Alert Internal Notes from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert Internal Note objects plus the… - `update_alert_internal_note` _(write)_ — Update an existing Alert Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_alert_internal_note` _(destructive)_ — Permanently delete a Alert Internal Note from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_alert_internal_notes` _(read)_ — Count the total number of Alert Internal Notes in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_alert_severity` _(write)_ — Create a new Alert Severity in OneUptime. Returns the created Alert Severity object with its ID. Use this to add new Alert Severities to your project. Note:… - `get_alert_severity` _(read)_ — Retrieve a single Alert Severity by its unique ID from OneUptime. Use list_alert_severities first if you need to find the ID. - `list_alert_severities` _(read)_ — List and search Alert Severities from OneUptime with optional filtering, pagination, and sorting. Returns an array of Alert Severity objects plus the total… - `update_alert_severity` _(write)_ — Update an existing Alert Severity in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_severity… - `delete_alert_severity` _(destructive)_ — Permanently delete a Alert Severity from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_alert_severities` _(read)_ — Count the total number of Alert Severities in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_incident_alert` _(write)_ — Create a new Incident Alert in OneUptime. Returns the created Incident Alert object with its ID. Use this to add new Incident Alerts to your project. Note:… - `get_incident_alert` _(read)_ — Retrieve a single Incident Alert by its unique ID from OneUptime. Use list_incident_alerts first if you need to find the ID. - `list_incident_alerts` _(read)_ — List and search Incident Alerts from OneUptime with optional filtering, pagination, and sorting. Returns an array of Incident Alert objects plus the total… - `update_incident_alert` _(write)_ — Update an existing Incident Alert in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_alert… - `delete_incident_alert` _(destructive)_ — Permanently delete a Incident Alert from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_incident_alerts` _(read)_ — Count the total number of Incident Alerts in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or… - `create_monitor_status_event` _(write)_ — Create a new Monitor Status Event in OneUptime. Returns the created Monitor Status Event object with its ID. Use this to add new Monitor Status Events to your… - `get_monitor_status_event` _(read)_ — Retrieve a single Monitor Status Event by its unique ID from OneUptime. Use list_monitor_status_events first if you need to find the ID. - `list_monitor_status_events` _(read)_ — List and search Monitor Status Events from OneUptime with optional filtering, pagination, and sorting. Returns an array of Monitor Status Event objects plus… - `update_monitor_status_event` _(write)_ — Update an existing Monitor Status Event in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_monitor_status_event` _(destructive)_ — Permanently delete a Monitor Status Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_monitor_status_events` _(read)_ — Count the total number of Monitor Status Events in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports,… - `create_status_page_announcement` _(write)_ — Create a new Status Page Announcement in OneUptime. Returns the created Status Page Announcement object with its ID. Use this to add new Status Page… - `get_status_page_announcement` _(read)_ — Retrieve a single Status Page Announcement by its unique ID from OneUptime. Use list_status_page_announcements first if you need to find the ID. - `list_status_page_announcements` _(read)_ — List and search Status Page Announcements from OneUptime with optional filtering, pagination, and sorting. Returns an array of Status Page Announcement objects… - `update_status_page_announcement` _(write)_ — Update an existing Status Page Announcement in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_status_page_announcement` _(destructive)_ — Permanently delete a Status Page Announcement from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_status_page_announcements` _(read)_ — Count the total number of Status Page Announcements in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards,… - `create_scheduled_maintenance_state` _(write)_ — Create a new Scheduled Maintenance State in OneUptime. Returns the created Scheduled Maintenance State object with its ID. Use this to add new Scheduled… - `get_scheduled_maintenance_state` _(read)_ — Retrieve a single Scheduled Maintenance State by its unique ID from OneUptime. Use list_scheduled_maintenance_states first if you need to find the ID. - `list_scheduled_maintenance_states` _(read)_ — List and search Scheduled Maintenance States from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled Maintenance State… - `update_scheduled_maintenance_state` _(write)_ — Update an existing Scheduled Maintenance State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_scheduled_maintenance_state` _(destructive)_ — Permanently delete a Scheduled Maintenance State from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_scheduled_maintenance_states` _(read)_ — Count the total number of Scheduled Maintenance States in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards,… - `create_scheduled_maintenance_event` _(write)_ — Create a new Scheduled Maintenance Event in OneUptime. Returns the created Scheduled Maintenance Event object with its ID. Use this to add new Scheduled… - `get_scheduled_maintenance_event` _(read)_ — Retrieve a single Scheduled Maintenance Event by its unique ID from OneUptime. Use list_scheduled_maintenance_events first if you need to find the ID. - `list_scheduled_maintenance_events` _(read)_ — List and search Scheduled Maintenance Events from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled Maintenance Event… - `update_scheduled_maintenance_event` _(write)_ — Update an existing Scheduled Maintenance Event in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use… - `delete_scheduled_maintenance_event` _(destructive)_ — Permanently delete a Scheduled Maintenance Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_scheduled_maintenance_events` _(read)_ — Count the total number of Scheduled Maintenance Events in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards,… - `create_scheduled_maintenance_state_timeline` _(write)_ — Create a new Scheduled Maintenance State Timeline in OneUptime. Returns the created Scheduled Maintenance State Timeline object with its ID. Use this to add… - `get_scheduled_maintenance_state_timeline` _(read)_ — Retrieve a single Scheduled Maintenance State Timeline by its unique ID from OneUptime. Use list_scheduled_maintenance_state_timelines first if you need to… - `list_scheduled_maintenance_state_timelines` _(read)_ — List and search Scheduled Maintenance State Timelines from OneUptime with optional filtering, pagination, and sorting. Returns an array of Scheduled… - `update_scheduled_maintenance_state_timeline` _(write)_ — Update an existing Scheduled Maintenance State Timeline in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged.… - `delete_scheduled_maintenance_state_timeline` _(destructive)_ — Permanently delete a Scheduled Maintenance State Timeline from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. - `count_scheduled_maintenance_state_timelines` _(read)_ — Count the total number of Scheduled Maintenance State Timelines in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for… - `list_logs` _(read)_ — Query Logs telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field… - `count_logs` _(read)_ — Count Logs telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_spans` _(read)_ — Query Spans telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field… - `count_spans` _(read)_ — Count Spans telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_metrics` _(read)_ — Query Metrics telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each… - `count_metrics` _(read)_ — Count Metrics telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_exception_instances` _(read)_ — Query Exception Instances telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g.… - `count_exception_instances` _(read)_ — Count Exception Instances telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_monitor_logs` _(read)_ — Query Monitor Logs telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50).… - `count_monitor_logs` _(read)_ — Count Monitor Logs telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_kubernetes_cost_allocations` _(read)_ — Query Kubernetes Cost Allocations telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small… - `count_kubernetes_cost_allocations` _(read)_ — Count Kubernetes Cost Allocations telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_security_events` _(read)_ — Query Security Events telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50).… - `count_security_events` _(read)_ — Count Security Events telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_change_events` _(read)_ — Query Change Events telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50).… - `count_change_events` _(read)_ — Count Change Events telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `list_threat_intel_indicators` _(read)_ — Query Threat Intel Indicators telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g.… - `count_threat_intel_indicators` _(read)_ — Count Threat Intel Indicators telemetry records in OneUptime, optionally filtered. Prefer counting with a time-range filter. - `acknowledge_incident` _(write)_ — Acknowledge an incident: marks it as being worked on by moving it to the project's 'Acknowledged' state. Equivalent to pressing 'Acknowledge' in the OneUptime… - `resolve_incident` _(write)_ — Resolve an incident: moves it to the project's 'Resolved' state. Equivalent to pressing 'Resolve' in the OneUptime dashboard. - `acknowledge_alert` _(write)_ — Acknowledge an alert: marks it as being worked on by moving it to the project's 'Acknowledged' state. - `resolve_alert` _(write)_ — Resolve an alert: moves it to the project's 'Resolved' state. - `add_incident_note` _(write)_ — Add a note to an incident. Internal notes are visible to your team only; public notes are posted to the status page for subscribers/customers. Markdown is… - `add_alert_note` _(write)_ — Add an internal note to an alert, visible to your team. Markdown is supported. - `oneuptime_whoami` _(read)_ — Get the project your API key belongs to (ID and name). Call this first to understand your context. Note: create tools infer projectId from the API key… - `oneuptime_help` _(read)_ — Get help and guidance for using the OneUptime MCP server. Returns information about available resources and common operations. Use this tool first to… - `oneuptime_list_resources` _(read)_ — List all available OneUptime resources and their supported operations. Use this to discover what resources you can manage through the MCP server. - `get_public_status_page_overview` _(read)_ — Get the complete overview of a public status page including current status, resources, active incidents, scheduled maintenance, and announcements. This tool… - `get_public_status_page_incidents` _(read)_ — Get incidents from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access… - `get_public_status_page_scheduled_maintenance` _(read)_ — Get scheduled maintenance events from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can… - `get_public_status_page_announcements` _(read)_ — Get announcements from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer 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: 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 and restart Claude Desktop 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__ 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)