Integration

Pingdom integration

Pingdom (SolarWinds) monitors websites and services from probe servers around the world. Create, update, pause and delete uptime checks, read check status, raw test results, outages, average response times and root cause analyses, manage maintenance windows, alerting contacts and teams, list probe servers and sent alerts, run a one-off test or traceroute, and manage transaction (TMS) checks with their status and performance reports. Bulk deletes of checks, maintenance windows and occurrences are not exposed. Authentication is a Pingdom API token (created in My Pingdom) sent as a Bearer token; writes need a token with Read/Write access.

Connect Pingdom How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Pingdom.Built from the 46 Pingdom tools below, on the connection you add once.

What you can do with Pingdom

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Check, 6 operations

bulk_update_checksBulk update checksPUTPauses, unpauses or changes the test resolution of several uptime checks at once. checkids is required here: the vendor applies the change to ALL checks when it is left out.
create_checkCreate checkPOSTCreates an uptime check (http, httpcustom, tcp, ping, dns, udp, smtp, pop3 or imap) on a host, tested every resolution minutes from Pingdom probes, and returns its id and name.
delete_checkDelete checkDELETEDeletes an uptime check. This is irreversible: all data collected for the check is lost.
get_checkGet checkGETReturns the full settings and current state of an uptime check: type-specific settings, status, last test and last error times, last response time, resolution, tags and alerting setup.
list_checksList checksGETReturns a list overview of all checks.
update_checkUpdate checkPUTModifies an uptime check. Only the settings you pass change; to clear a value, pass an empty value. The check type cannot be changed after creation.

Contact, 5 operations

create_contactCreate contactPOSTCreates a new contact with at least one contact method (notification target)
delete_contactDelete contactDELETEDeletes a contact with its contact methods (notification targets)
get_contactGet contactGETReturns a contact with its contact methods (notification targets)
list_contactsList contactsGETReturns a list of all contacts with their contact methods (notification targets)
update_contactUpdate contactPUTReplaces a contact: name, paused state and notification targets are all required and overwrite the current values.

Maintenance, 5 operations

create_maintenance_windowCreate maintenance windowPOSTCreates a maintenance window during which the given uptime and transaction checks raise no alerts, optionally repeating every n days, weeks or months.
delete_maintenance_windowDelete maintenance windowDELETEDeletes a maintenance window. Only a future maintenance window can be deleted.
get_maintenance_windowGet maintenance windowGETReturns the maintenance window specified by its id.
list_maintenance_windowsList maintenance windowsGETReturns a list of user's maintenance windows.
update_maintenance_windowUpdate maintenance windowPUTModifies a maintenance window: description, start and end, recurrence and the checks it covers. Only the settings you pass change.

Team, 5 operations

create_teamCreate teamPOSTCreates a new team with or without members
delete_teamDelete teamDELETEDeletes a team
get_teamGet teamGETReturns a team with its members
list_teamsList teamsGETReturns a list of all teams and their members
update_teamUpdate teamPUTReplaces a team's name and member list (both required).

Transaction check, 5 operations

create_transaction_checkCreate transaction checkPOSTCreates a transaction (TMS) check: a scripted browser journey (go to a URL, fill fields, click, verify content) run at an interval from a region. Returns its id and name.
delete_transaction_checkDelete transaction checkDELETEDeletes a transaction (TMS) check.
get_transaction_checkGet transaction checkGETReturns a transaction (TMS) check: its steps, interval, region, status, alerting contacts and teams, tags and last downtime.
list_transaction_checksList transaction checksGETLists the transaction (TMS) checks: id, name, type (script or recording), status, interval, region, tags and last downtime. Filter by tags or type.
update_transaction_checkUpdate transaction checkPUTModifies a transaction (TMS) check. Only the settings you pass change. Returns the updated check.

Maintenance occurrence, 4 operations

delete_maintenance_occurrenceDelete maintenance occurrenceDELETEDeletes the maintenance occurrence specified by its identifier. Note that only future occurrences can be deleted.
get_maintenance_occurrenceGet maintenance occurrenceGETGets a maintenance occurrence details specified by its identifier.
list_maintenance_occurrencesList maintenance occurrencesGETReturns a list of maintenance occurrences.
update_maintenance_occurrenceUpdate maintenance occurrencePUTModifies a maintenance occurrence specified by its identifier.

Check summary, 3 operations

get_check_average_summaryGet check average summaryGETReturns the average response time of an uptime check over a period, optionally its uptime and downtime totals, and response times split by country or by probe.
get_check_hours_of_dayGet check hours of dayGETReturns the average response time of an uptime check for each hour of the day (0-23) over a period (by default the last week): what an average day looks like.
get_check_performance_summaryGet check performance summaryGETReturns an uptime check's average response time (and optionally uptime) per hour, day or week over a period. Useful for graphs.

Probe, 2 operations

list_check_probesList check probesGETLists the identifiers of the probes that tested an uptime check during a period. from is required.
list_probesList probesGETReturns a list of all Pingdom probe servers for Uptime and Transaction checks.

Transaction status report, 2 operations

get_transaction_check_status_reportGet transaction check status reportGETLists the status changes of one transaction check over a period (RFC 3339 from and to, by default the last week), oldest first unless order is desc.
list_transaction_status_reportsList transaction status reportsGETLists the status changes of every transaction check in the organization over a period (RFC 3339 from and to, by default the last week), for an overview of all checks.

Alert, 1 operation

list_alertsList alertsGETLists the alerts (actions) Pingdom sent for your account: which check, to whom, by which medium and when. Filter by time range, check ids, user ids, status or medium.

Analysis, 1 operation

list_check_analysesList check analysesGETLists the latest root cause analyses Pingdom ran for a check (one per confirmed down event), with the time of the first and the confirming test.

Credit, 1 operation

get_creditsGet creditsGETReturns the account's check and SMS credits: check limit and checks available, uptime and transaction checks used, SMS credits left and SMS auto-refill settings.

Outage, 1 operation

list_check_outagesList check outagesGETLists the status changes (up, down, unknown, with start and end times) of an uptime check over a period, by default the last week, oldest first unless order is desc.

Reference, 1 operation

get_reference_dataGet reference dataGETGet a reference of regions, timezones and date/time/number formats and their identifiers.

Result, 1 operation

list_check_resultsList check resultsGETLists raw test results for an uptime check (one per probe test: time, status, response time, probe) over a period, by default the last day, at most 1000 per call.

Test, 1 operation

run_single_testRun single testGETRuns one test right now from a Pingdom probe against a host and returns its status and response time. Pingdom says this is meant to be used sparingly, not as a monitoring solution.

Traceroute, 1 operation

run_tracerouteRun tracerouteGETRuns a traceroute from a Pingdom probe to a host and returns the raw traceroute output.

Transaction performance report, 1 operation

get_transaction_check_performance_reportGet transaction check performance reportGETReturns a transaction check's response times per hour, day or week (optionally uptime and downtime), with per-step detail. The hour resolution covers at most one week and a day, day at most six months and a day.

Use Pingdom from Claude Code, Cursor or Codex

Connect Pingdom in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Pingdom operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Pingdom

Create your workspace
Sign up free. Nothing to install.
Connect Pingdom once
Add your Pingdom connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.