Uptrack MCP server
Connect Claude to Uptrack and manage your uptime monitoring in plain language. List monitors, create checks, read uptime and acknowledge incidents without opening the dashboard.
Connect Claude
Add the connector
In Claude, open Customize → Connectors → Add custom connector. Use this server URL:
https://api.uptrack.app/mcpSign in and approve
Claude opens the Uptrack consent page. Sign in to your Uptrack account and choose Allow. You need an Uptrack account on a paid plan. You do not need an API key or a client secret.
Ask
Turn the Uptrack connector on in a chat and ask a question. Claude asks you to approve each tool call unless you choose “Always allow”.
Example prompts
- List my monitors and tell me which ones are down.
- Show uptime and response times for my API monitor over the last 30 days.
- Create an HTTP monitor named “Marketing site” for https://example.com.
- Pause the “Staging” monitor while I deploy, then resume it.
- Acknowledge the open incident on checkout.
- Create an email alert channel named “On-call” for [email protected].
Tools
The server has 13 tools. Seven only read data. Five change data. One deletes a monitor. Every tool is limited to the organization you signed in with, and each needs an OAuth scope that you approve on the consent page.
| Tool | What it does | Scope |
|---|---|---|
list_monitors | List monitors with id, name, URL and status. | monitors:read |
get_monitor | Get one monitor with its current status and 30-day uptime. | monitors:read |
get_monitor_analytics | Uptime percentage, daily uptime and response-time percentiles (30 days by default). | analytics:read |
get_dashboard_stats | Monitor counts, ongoing incidents and 30-day uptime for the organization. | analytics:read |
list_incidents | List recent incidents (10 by default). | incidents:read |
list_status_pages | List the organization’s status pages. | status_pages:read |
list_alert_channels | List alert channels: id, name, type and whether active. | alerts:read |
create_monitor | Create a monitor. A URL and a name are required. Default type is HTTP with a 180-second interval. | monitors:write |
pause_monitor | Pause a monitor. Safe to repeat. | monitors:write |
resume_monitor | Resume a paused monitor. Safe to repeat. | monitors:write |
acknowledge_incident | Acknowledge an incident. This pauses escalation reminders. | incidents:write |
create_alert_channel | Create an email, Slack, Discord or Telegram alert channel. | alerts:write |
delete_monitordestructive | Delete a monitor by id. This is the only destructive tool. | monitors:write |
Security and data
- Sign-in uses OAuth 2.0 with PKCE (S256). Clients register by Client ID Metadata Document or by dynamic client registration.
- The organization comes from your access token. A tool call cannot read or change another organization.
- Tokens carry only the scopes you approve. A read-only token cannot call a write tool.
- Uptrack returns monitor, incident and alert-channel data that your account already holds. It does not receive your conversation.
- To disconnect, remove the connector in Claude.
Read the privacy policy for how Uptrack handles data.
For developers
The server speaks MCP over stateless Streamable HTTP at https://api.uptrack.app/mcp. It also answers on /api/mcp. Discovery documents:
Prefer plain HTTP? Use the REST API.
FAQ
Does it work with other AI clients?
Yes. Any client that supports remote MCP servers and OAuth can use the same URL.
Can Claude delete my monitors?
Only the delete_monitor tool can, and only with the monitors:write scope. Claude asks for your approval before each call. Do not choose “Always allow” for that tool if you want a check every time.
I changed my monitors, but Claude shows old tools.
Claude caches the tool list. Open the connector settings and choose “Refresh tools list”.
Where do I get help?
Email [email protected].
Monitor from your chat
Pro includes 50 monitors at 30-second checks from $3/mo, with a 30-day money-back guarantee.
See plans