# OneUptime MCP server

> Manage incidents, alerts, monitors, status pages, on-call and telemetry in your OneUptime project.

- Listing: https://mcp.tc/i/oneuptime
- Connect: use the server's own URL `https://oneuptime.com/mcp` (sign-in optional); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: optional (works without sign-in)
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: OneUptime
- Homepage: <https://oneuptime.com/docs/ai/mcp-server>
- Repository: <https://github.com/OneUptime/oneuptime/tree/HEAD/packages/App/FeatureSet/MCP>

## About

Connects an assistant to a OneUptime project. The tools follow a create, get, list, update, delete and count pattern across many resources, including teams, labels, status pages, security cases, security detections and security playbooks. Monitors, incidents, alerts, on-call and telemetry are also covered by the server.

The server is hosted at https://oneuptime.com/mcp over streamable HTTP. MCP clients sign in with a OneUptime account through OAuth 2.1 in the browser. Unattended agents can instead send a project API key in the x-api-key header.

## What it can do

- Create, update, list and delete teams and labels
- Manage status pages and their settings
- Open and update security cases and case notes
- Create and edit security detections and playbooks
- Count and filter resources with queries, sorting and pagination
- Work with incidents, alerts, monitors and on-call in a project

## Tools (199)

- `create_team`: Create a new team in the project. (can modify or delete data)
- `get_team`: Retrieve a team by ID. (read-only)
- `list_teams`: List and search teams with filtering and pagination. (read-only)
- `update_team`: Update an existing team. (can modify or delete data)
- `delete_team`: Permanently delete a team. (can modify or delete data)
- `count_teams`: Count teams, optionally filtered. (read-only)
- `create_label`: Create a new label. (can modify or delete data)
- `get_label`: Retrieve a label by ID. (read-only)
- `list_labels`: List and search labels. (read-only)
- `update_label`: Update an existing label. (can modify or delete data)
- `delete_label`: Permanently delete a label. (can modify or delete data)
- `count_labels`: Count labels, optionally filtered. (read-only)
- `create_security_case`: Create a new security case. (can modify or delete data)
- `get_security_case`: Retrieve a security case by ID. (read-only)
- `list_security_cases`: List and search security cases. (read-only)
- `update_security_case`: Update a security case. (can modify or delete data)
- `delete_security_case`: Permanently delete a security case. (can modify or delete data)
- `count_security_cases`: Count security cases, optionally filtered. (read-only)
- `create_security_case_note`: Add a note to a security case. (can modify or delete data)
- `get_security_case_note`: Retrieve a security case note by ID. (read-only)
- `list_security_case_notes`: List and search security case notes. (read-only)
- `update_security_case_note`: Update a security case note. (can modify or delete data)
- `delete_security_case_note`: Permanently delete a security case note. (can modify or delete data)
- `count_security_case_notes`: Count security case notes. (read-only)
- `create_security_detection`: Create a new security detection. (can modify or delete data)
- `get_security_detection`: Retrieve a security detection by ID. (read-only)
- `list_security_detections`: List and search security detections. (read-only)
- `update_security_detection`: Update a security detection. (can modify or delete data)
- `delete_security_detection`: Permanently delete a security detection. (can modify or delete data)
- `count_security_detections`: Count security detections. (read-only)
- `create_security_playbook`: Create a security playbook with trigger and steps. (can modify or delete data)
- `get_security_playbook`: Retrieve a security playbook by ID. (read-only)
- `list_security_playbooks`: List and search security playbooks. (read-only)
- `update_security_playbook`: Update a security playbook. (can modify or delete data)
- `delete_security_playbook`: Permanently delete a security playbook. (can modify or delete data)
- `count_security_playbooks`: Count security playbooks. (read-only)
- `create_status_page`: Create a new status page. (can modify or delete data)
- `get_status_page`: Retrieve a status page by ID. (read-only)
- `list_status_pages`: List and search status pages. (read-only)
- `update_status_page`: Update a status page. (can modify or delete data)
- `delete_status_page`: Permanently delete a Status Page from OneUptime. (can modify or delete data)
- `count_status_pages`: Count the total number of Status Pages in OneUptime, optionally filtered by query criteria. (read-only)
- `create_on_call_policy`: Create a new On-Call Policy in OneUptime. (can modify or delete data)
- `get_on_call_policy`: Retrieve a single On-Call Policy by its unique ID from OneUptime. (read-only)
- `list_on_call_duty_policies`: List and search On-Call Duty Policies from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_on_call_policy`: Update an existing On-Call Policy in OneUptime. (can modify or delete data)
- `delete_on_call_policy`: Permanently delete a On-Call Policy from OneUptime. (can modify or delete data)
- `count_on_call_duty_policies`: Count the total number of On-Call Duty Policies in OneUptime, optionally filtered by query criteria. (read-only)
- `create_monitor`: Create a new Monitor in OneUptime. (can modify or delete data)
- `get_monitor`: Retrieve a single Monitor by its unique ID from OneUptime. (read-only)
- `list_monitors`: List and search Monitors from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_monitor`: Update an existing Monitor in OneUptime. (can modify or delete data)
- `delete_monitor`: Permanently delete a Monitor from OneUptime. (can modify or delete data)
- `count_monitors`: Count the total number of Monitors in OneUptime, optionally filtered by query criteria. (read-only)
- `create_monitor_status`: Create a new Monitor Status in OneUptime. (can modify or delete data)
- `get_monitor_status`: Retrieve a single Monitor Status by its unique ID from OneUptime. (read-only)
- `list_monitor_statuses`: List and search Monitor Statuses from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_monitor_status`: Update an existing Monitor Status in OneUptime. (can modify or delete data)
- `delete_monitor_status`: Permanently delete a Monitor Status from OneUptime. (can modify or delete data)
- `count_monitor_statuses`: Count the total number of Monitor Statuses in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident_state`: Create a new Incident State in OneUptime. (can modify or delete data)
- `get_incident_state`: Retrieve a single Incident State by its unique ID from OneUptime. (read-only)
- `list_incident_states`: List and search Incident States from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident_state`: Update an existing Incident State in OneUptime. (can modify or delete data)
- `delete_incident_state`: Permanently delete a Incident State from OneUptime. (can modify or delete data)
- `count_incident_states`: Count the total number of Incident States in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident`: Create a new Incident in OneUptime. (can modify or delete data)
- `get_incident`: Retrieve a single Incident by its unique ID from OneUptime. (read-only)
- `list_incidents`: List and search Incidents from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident`: Update an existing Incident in OneUptime. (can modify or delete data)
- `delete_incident`: Permanently delete a Incident from OneUptime. (can modify or delete data)
- `count_incidents`: Count the total number of Incidents in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident_state_timeline`: Create a new Incident State Timeline in OneUptime. (can modify or delete data)
- `get_incident_state_timeline`: Retrieve a single Incident State Timeline by its unique ID from OneUptime. (read-only)
- `list_incident_state_timelines`: List and search Incident State Timelines from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident_state_timeline`: Update an existing Incident State Timeline in OneUptime. (can modify or delete data)
- `delete_incident_state_timeline`: Permanently delete a Incident State Timeline from OneUptime. (can modify or delete data)
- `count_incident_state_timelines`: Count the total number of Incident State Timelines in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident_internal_note`: Create a new Incident Internal Note in OneUptime. (can modify or delete data)
- `get_incident_internal_note`: Retrieve a single Incident Internal Note by its unique ID from OneUptime. (read-only)
- `list_incident_internal_notes`: List and search Incident Internal Notes from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident_internal_note`: Update an existing Incident Internal Note in OneUptime. (can modify or delete data)
- `delete_incident_internal_note`: Permanently delete a Incident Internal Note from OneUptime. (can modify or delete data)
- `count_incident_internal_notes`: Count the total number of Incident Internal Notes in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident_public_note`: Create a new Incident Public Note in OneUptime. (can modify or delete data)
- `get_incident_public_note`: Retrieve a single Incident Public Note by its unique ID from OneUptime. (read-only)
- `list_incident_public_notes`: List and search Incident Public Notes from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident_public_note`: Update an existing Incident Public Note in OneUptime. (can modify or delete data)
- `delete_incident_public_note`: Permanently delete a Incident Public Note from OneUptime. (can modify or delete data)
- `count_incident_public_notes`: Count the total number of Incident Public Notes in OneUptime, optionally filtered by query criteria. (read-only)
- `create_incident_severity`: Create a new Incident Severity in OneUptime. (can modify or delete data)
- `get_incident_severity`: Retrieve a single Incident Severity by its unique ID from OneUptime. (read-only)
- `list_incident_severities`: List and search Incident Severities from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_incident_severity`: Update an existing Incident Severity in OneUptime. (can modify or delete data)
- `delete_incident_severity`: Permanently delete a Incident Severity from OneUptime. (can modify or delete data)
- `count_incident_severities`: Count the total number of Incident Severities in OneUptime, optionally filtered by query criteria. (read-only)
- `create_postmortem_status`: Create a new Postmortem Status in OneUptime. (can modify or delete data)
- `get_postmortem_status`: Retrieve a single Postmortem Status by its unique ID from OneUptime. (read-only)
- `list_postmortem_statuses`: List and search Postmortem Statuses from OneUptime with optional filtering, pagination, and sorting. (read-only)
- `update_postmortem_status`: Update an existing Postmortem Status in OneUptime. (can modify or delete data)
- … and 99 more on the listing page.

## Example prompts

- "List all status pages in my OneUptime project"
- "Create a security case for suspicious logins and assign it to the SRE team"
- "How many teams do we have in OneUptime?"
- "Add a note to security case 123 saying the account was locked"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http oneuptime https://oneuptime.com/mcp
```

2. Start Claude Code and type `/mcp`. **oneuptime** should show as connected. To sign in for more access, pick it and choose **Authenticate**.

Add `--scope user` to make it available in every project, not just this one. Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **OneUptime** and paste this URL:

```url
https://oneuptime.com/mcp
```

3. Click **Add**, then **Connect**. Signing in to OneUptime is optional.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=OneUptime&connectorUrl=https%3A%2F%2Foneuptime.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://oneuptime.com/mcp` and click **Add**.

3. Click **Connect**. Signing in to OneUptime is optional.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://oneuptime.com/mcp` as the server URL, then for authentication choose **No authentication**, or **OAuth** to sign in to OneUptime for more access.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=oneuptime&config=eyJ1cmwiOiJodHRwczovL29uZXVwdGltZS5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "oneuptime": {
      "url": "https://oneuptime.com/mcp"
    }
  }
}
```

Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=oneuptime&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Foneuptime.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"oneuptime","type":"http","url":"https://oneuptime.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "oneuptime": {
      "type": "http",
      "url": "https://oneuptime.com/mcp"
    }
  }
}
```

Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "oneuptime": {
      "serverUrl": "https://oneuptime.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### Codex

```bash
codex mcp add oneuptime --url https://oneuptime.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.oneuptime]
url = "https://oneuptime.com/mcp"
```

Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http oneuptime https://oneuptime.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth oneuptime` to sign in (optional).

This adds it to the current project. Add `-s user` to use it everywhere. Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "oneuptime": {
      "type": "http",
      "url": "https://oneuptime.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://oneuptime.com/mcp`.

Works without a key. An API key from OneUptime raises the limits: send it as `x-api-key: <YOUR_API_KEY>`.

## Recent changes

- 2026-11-17 08:53 UTC: New version 14.3.0 (was 14.2.0), reported by the server. Source: automatic check.
- 2026-11-15 17:56 UTC: New version 14.1.0 (was 14.0.110), reported by the server. Source: automatic check.
- 2026-11-14 14:51 UTC: New version 14.0.110 (was 14.0.107), reported by the server. Source: automatic check.
- 2026-11-11 08:50 UTC: New version 14.0.106 (was 14.0.105), reported by the server. Source: automatic check.
- 2026-11-09 14:50 UTC: New version 14.0.105 (was 14.0.104), reported by the server. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/oneuptime#history (Atom feed: https://mcp.tc/i/oneuptime/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 14.3.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-19
- Updated: 2026-10-23

---
Source: https://mcp.tc/i/oneuptime (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
