Agents & API

MCP server

UpButler runs a remote MCP server. All 94 tools map one-to-one to REST operations, so your coding agent can monitor services, run status pages and handle incidents from the conversation.

#Connect

claude mcp add --transport http upbutler https://upbutler.com/mcp \
  --header "Authorization: Bearer ub_live_..."

{
  "mcpServers": {
    "upbutler": {
      "url": "https://upbutler.com/mcp",
      "headers": { "Authorization": "Bearer ub_live_..." }
    }
  }
}

{
  "servers": {
    "upbutler": {
      "type": "http",
      "url": "https://upbutler.com/mcp",
      "headers": { "Authorization": "Bearer ub_live_..." }
    }
  }
}

{
  "mcpServers": {
    "upbutler": {
      "type": "http",
      "url": "https://upbutler.com/mcp",
      "headers": { "Authorization": "Bearer ub_live_..." }
    }
  }
}

No key yet? Connect without the header and call agent_bootstrap. It returns a key, and you reconnect with it. People create keys in the dashboard under /app/settings/api-keys. Agents can mint their own with keys_create and an agent name, so incident timelines show which agent acted.

#Server instructions

On initialize, the server gives your model this primer:

UpButler monitors services and runs status pages. Typical flows:
- Start monitoring + publish: services_add {name, url, statusPage}.
- Your own jobs: services_add with periodSec to get a heartbeat URL, then call it after each run.
- Report problems you detect: incidents_create; post progress with incidents_update; finish with incidents_resolve.
- React to other services: public_subscribe with a webhook URL, or poll events_list with after=<last id>.
- Many components at once: pages_push {pageId, statuses:{key: status}}.
No API key yet? Call agent_bootstrap to get one, then reconnect with Authorization: Bearer <key>.

#Public tools (no key)

These tools work without authentication, so an agent can read any public UpButler status page and subscribe to it:

• agent_bootstrap: Create a workspace + API key with no human in the loop
• heartbeat_ping: Send a heartbeat (no API key needed — the token is the secret)
• components_push: Push one component status by its push token (no API key needed)
• public_status: Public status of a page (no auth)
• public_incidents: Public incident history of a page
• public_incident: One public incident with its updates
• public_subscribe: Subscribe to a status page (email, webhook, Slack or Discord)
• public_subscriber_get: View a subscription (requires its manage token)
• public_subscriber_update: Change which components a subscription follows (requires the manage token)
• public_unsubscribe: Unsubscribe (requires the manage token)
• public_responseTimes: Public response-time series of a component (p50/p95)
• plans_list: Available plans and limits

Every other tool needs a key. Write tools need the write scope.

#Tools

Generated from the server's operation registry. Arguments are the same as the REST endpoint's path, query and body fields, merged into one object, and each tool advertises its full JSON Schema in tools/list. Tool annotations mark GET tools readOnlyHint and DELETE tools destructiveHint.

#Agents

#Monitors

#Status pages

#Components

#Incidents

#Alerts

#Public status

#Workspace

#Events

#Billing

#Import

#On-call

#Deploys

#Digest

Not exposed as tools: workspaces.list, workspaces.create, workspaces.switch, members.invite, members.revokeInvite, members.remove, billing.portal, profile.contact.get, profile.contact.update, me.security, me.sessions.revoke, me.sessions.revokeOthers, me.2fa.setup, me.2fa.enable, me.2fa.disable, me.2fa.recoveryCodes, me.identities.unlink, workspace.security.update. These are dashboard or REST-only operations.

#Results and errors

A successful call returns the REST response twice: as structuredContent, and as pretty-printed JSON in a text content block. A failing call returns isError: true with the standard error envelope, including hint, as text. That makes errors easy for a model to act on.

#Talk to it with curl

# List tools (works without a key)
curl -s -X POST https://upbutler.com/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

# Call a tool
curl -s -X POST https://upbutler.com/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $UPBUTLER_API_KEY" \
  -d '{
    "jsonrpc": "2.0", "id": 2, "method": "tools/call",
    "params": { "name": "services_add", "arguments": { "name": "Search API", "url": "https://api.example.com/health", "statusPage": "acme" } }
  }'

GET https://upbutler.com/mcp returns a small JSON description of the endpoint. Batched JSON-RPC requests are supported. Sessions aren't required: every request is authenticated on its own.