> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uptimeio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Let AI assistants such as Claude Code and Cursor read your monitors and incidents, and manage them on paid plans

UptimeIO has a remote [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server. Connect an MCP-compatible AI assistant to it and you can ask things like "which monitors are down?" or "pause the staging monitor" in plain language.

## Endpoint

```
https://api.uptimeio.com/mcp
```

The server uses an [API key](https://docs.uptimeio.com/account/api-keys.md) for access. Send it as `Authorization: Bearer YOUR_API_KEY`.

> [!NOTE]
>
> Use a **Read Only** key unless you want the assistant to make changes. Write tools need a **Read & Write** key on the Pro or Scale plan.

## Connect your assistant

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --transport http uptimeio https://api.uptimeio.com/mcp \
>   --header "Authorization: Bearer uio_YOUR_API_KEY"
> ```

> [tab] Cursor
>
> Add this to `.cursor/mcp.json` (or `~/.cursor/mcp.json` for all projects):
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "uptimeio": {
>       "url": "https://api.uptimeio.com/mcp",
>       "headers": {
>         "Authorization": "Bearer uio_YOUR_API_KEY"
>       }
>     }
>   }
> }
> ```

Keep the key out of files you commit to source control.

## Available tools

### Read tools (all plans)

| Tool | What it does |
| - | - |
| `list_monitors` | Lists monitors with status, uptime and response time over the last 30 days. Filter by status, type or search text. |
| `get_monitor` | Shows one monitor: its settings, current status, 7-day stats and recent pause and resume history. Header values and request bodies are masked. |
| `get_response_times` | Response time statistics and a time series for a monitor over 24 hours, 7, 30 or 90 days, within your plan's response time history. |
| `list_incidents` | Lists incidents, newest first. Filter by status, monitor or start time. |
| `get_incident` | Shows one incident with its updates and affected monitors. |
| `get_incident_timeline` | Shows the check attempts behind an incident, with response times and timing breakdown in milliseconds. For heartbeat monitors it shows the heartbeat events. |
| `list_status_pages` | Lists your status pages with their public URLs and monitor counts. |

### Write tools (Pro and Scale, Read & Write key)

| Tool | What it does |
| - | - |
| `create_monitor` | Creates a monitor. Plan limits, minimum intervals and target safety checks apply as in the dashboard. |
| `pause_monitor` | Pauses a monitor. It is not checked and raises no incidents until resumed. |
| `resume_monitor` | Resumes a paused monitor and starts checking immediately. Fails if your plan's active monitor limit is reached. |
| `acknowledge_incident` | Marks an open incident as acknowledged, with an optional note. |
| `schedule_maintenance` | Schedules a maintenance window for monitors that appear on your status pages. |

Tools follow the same rules as the dashboard. Your role in the organization decides what you can do, and a key restricted to one project only reaches that project. Times are returned in UTC.

## Plan differences

| | Free | Pro | Scale |
| - | - | - | - |
| Read tools | Yes | Yes | Yes |
| Write tools | No | Yes, with a Read & Write key | Yes, with a Read & Write key |
| Tool calls per minute | 10 | 200 | 500 |

* Tool calls per minute are shared by all API keys in your organization.
* When the limit is reached, the tool tells the assistant how many seconds to wait.
* On a Free plan or with a Read Only key, a write tool returns: "This API key is read-only. Create a read/write key on a paid plan to make changes."

## Troubleshooting

| Problem | What to do |
| - | - |
| `401` when connecting | The key is missing, wrong, expired or deleted. Create a new key in **Settings > API Keys**. |
| A write tool says the key is read-only | Create a **Read & Write** key. This needs the Pro or Scale plan. |
| "Rate limit reached" or "Too many requests" | Wait the number of seconds shown, then try again. |
| "Monitor not found" | The monitor does not exist, was deleted, or is outside the key's project. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.