Upcron MCP Server

Connect an MCP-compatible assistant or automation client to Upcron.

The Upcron MCP server exposes monitoring operations as structured tools and resources for MCP clients. It lets an authorized client inspect projects, monitors and heartbeats, check status, manage maintenance windows and work with incidents without scraping the dashboard.

Connection

The hosted MCP endpoint is:

https://upcron.io/mcp

Authenticate the connection with an Upcron Sanctum bearer token:

{
  "mcpServers": {
    "upcron": {
      "url": "https://upcron.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_UPCRON_TOKEN"
      }
    }
  }
}

Never commit the token or expose it in a client-side application. Revoke it from your API token settings if it is exposed.

Available capabilities

• List and inspect projects, monitors and heartbeats
• Read monitor and heartbeat status
• Create, update, pause, resume and delete monitors or heartbeats
• List and inspect incidents
• Create and manage maintenance windows
• List available monitoring zones
• Create, update, fire and delete notification triggers
• Manage components and inspect status pages
• Read dashboard KPIs, subscription usage and plan information

Scope operations to a project

Most resource operations are project-scoped. Give the client the project ID when asking it to create or inspect a monitor, heartbeat, component, maintenance window or notification trigger. This keeps operations unambiguous when an account has more than one project.

Security and permissions

• MCP requests require Sanctum authentication.
• Authorization follows the authenticated user's Upcron organization and project access.
• Use a dedicated token for an assistant or automation and revoke it independently when no longer needed.
• Prefer read-only requests for assistants that only need monitoring context.

Troubleshooting