MCP & API Keys

Overview

isthisthing.online exposes a Model Context Protocol (MCP) server so AI assistants — Claude, Cursor, VS Code and any other MCP client — can read and manage your Monitors, Incidents and Status Pages through natural language.

Instead of pasting API docs, your assistant can do things like:

• "How are my Monitors doing right now?"
• "What was uptime for the Production API over the last 30 days?"
• "Open an Incident for the checkout monitor."

1. Create an API key

1. Sign in to the dashboard.
2. Click your avatar → API Keys.
3. Click Create API Key, give it a label (e.g. Claude Desktop) and choose scopes:
   • Read — list and inspect Monitors, Incidents, Status Pages and analytics.
   • Write — create, update, pause, resume and delete Monitors and Incidents.
4. Choose workspace access:
   • All workspaces — the key can access every workspace you belong to.
   • Specific workspaces — restrict the key to the ones you select.
5. Copy the key. It is shown only once — store it somewhere safe.

API keys belong to your account, not to a single workspace. You can scope a key to all of your workspaces or only the ones you select. Revoking the key cuts off every client using it immediately.

2. Connect an MCP client

Use the server URL https://api.isthisthing.online/mcp with your key as a bearer token.

Claude Desktop

{
  "mcpServers": {
    "isthisthingonline": {
      "url": "https://api.isthisthing.online/mcp",
      "headers": {
        "Authorization": "Bearer ito_your_api_key"
      }
    }
  }
}

Cursor / VS Code (.mcp.json)

{
  "mcpServers": {
    "isthisthingonline": {
      "url": "https://api.isthisthing.online/mcp",
      "headers": {
        "Authorization": "Bearer ito_your_api_key"
      }
    }
  }
}

Generic MCP client

mcp {
  server "isthisthingonline" {
    url = "https://api.isthisthing.online/mcp"
    headers {
      Authorization = "Bearer ito_your_api_key"
    }
  }
}

3. Available tools

Tool	Description	Scope
list_workspaces	List the workspaces this key can access	Read
list_monitors	List Monitors in the workspace	Read
get_monitor	Get a single Monitor by ID	Read
get_monitor_status	Current status and uptime statistics	Read
get_uptime	Uptime percentage over a time range	Read
list_incidents	List Incidents	Read
get_incident	Get a single Incident by ID	Read
list_status_pages	List Status Pages	Read
get_status_page_status	Current Status Page status	Read
get_analytics_summary	Uptime, Incident and response-time summary	Read
get_workspace_info	Workspace info	Read
create_monitor	Create a Monitor	Write
update_monitor	Update a Monitor	Write
pause_monitor	Pause a Monitor	Write
resume_monitor	Resume a Monitor	Write
delete_monitor	Delete a Monitor	Write
create_incident	Create an Incident	Write
update_incident	Update an Incident	Write
resolve_incident	Resolve an Incident	Write

Write tools are disabled when the API key does not include the Write scope.

Security

• API keys are stored hashed (SHA-256) — the raw key is never kept.
• A key only grants access to the workspaces you selected (or all of them if you picked that option).
• Revoke a key from API Keys any time to immediately cut off access.
• Use a separate key per client so you can revoke individually.

See also

• Webhooks
• Workspaces
• Team Roles