Can I use Pingdom as a CLI?

Yes. KosmoKrator exposes a Pingdom CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pingdom through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pingdom tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pingdom credentials stored?

Pingdom credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pingdom MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Pingdom CLI for AI Agents

Use the Pingdom CLI from KosmoKrator to call Pingdom tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write API key auth

Submit Pingdom feedback View package source

Pingdom CLI Setup

Pingdom can be configured headlessly with `kosmokrator integrations:configure pingdom`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure pingdom --set api_key="$PINGDOM_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor pingdom --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_key`	`PINGDOM_API_KEY`	Secret `secret`	yes	API Key
`url`	`PINGDOM_URL`	URL `url`	no	API Base URL

Call Pingdom Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call pingdom.pingdom_list_checks '{
  "limit": 1,
  "offset": 1,
  "status": "example_status",
  "tags": "example_tags"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:pingdom pingdom_list_checks '{
  "limit": 1,
  "offset": 1,
  "status": "example_status",
  "tags": "example_tags"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs pingdom --json
kosmo integrations:docs pingdom.pingdom_list_checks --json
kosmo integrations:schema pingdom.pingdom_list_checks --json
kosmo integrations:search "Pingdom" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Pingdom.

`pingdom.pingdom_list_checks`

Read read

List all uptime checks in Pingdom. Returns check IDs, names, hostnames, statuses, and last test times.

Parameters: limit, offset, status, tags

Generic CLI call

kosmo integrations:call pingdom.pingdom_list_checks '{"limit":1,"offset":1,"status":"example_status","tags":"example_tags"}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_list_checks '{"limit":1,"offset":1,"status":"example_status","tags":"example_tags"}' --json

`pingdom.pingdom_get_check`

Read read

Get detailed information about a specific Pingdom uptime check, including configuration, current status, and last test results.

Parameters: check_id

Generic CLI call

kosmo integrations:call pingdom.pingdom_get_check '{"check_id":1}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_get_check '{"check_id":1}' --json

`pingdom.pingdom_create_check`

Write write

Create a new uptime check in Pingdom. Supports HTTP, HTTPS, TCP, ping, DNS, UDP, SMTP, POP3, and IMAP check types.

Parameters: name, host, type, resolution, url, port, tags, send_string, expect_string, contactids

Generic CLI call

kosmo integrations:call pingdom.pingdom_create_check '{"name":"example_name","host":"example_host","type":"example_type","resolution":1,"url":"example_url","port":1,"tags":"example_tags","send_string":"example_send_string"}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_create_check '{"name":"example_name","host":"example_host","type":"example_type","resolution":1,"url":"example_url","port":1,"tags":"example_tags","send_string":"example_send_string"}' --json

`pingdom.pingdom_list_results`

Read read

List summary results for a Pingdom uptime check. Returns response times and status summaries.

Parameters: check_id, from, to, limit, offset

Generic CLI call

kosmo integrations:call pingdom.pingdom_list_results '{"check_id":1,"from":1,"to":1,"limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_list_results '{"check_id":1,"from":1,"to":1,"limit":1,"offset":1}' --json

`pingdom.pingdom_get_results`

Read read

Get detailed test results for a Pingdom uptime check, including individual probe responses and response times.

Parameters: check_id, from, to, limit, offset, probes, status

Generic CLI call

kosmo integrations:call pingdom.pingdom_get_results '{"check_id":1,"from":1,"to":1,"limit":1,"offset":1,"probes":"example_probes","status":"example_status"}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_get_results '{"check_id":1,"from":1,"to":1,"limit":1,"offset":1,"probes":"example_probes","status":"example_status"}' --json

`pingdom.pingdom_list_alerts`

Read read

List alerts for the Pingdom account. Returns alert details including check ID, contact, and alert type.

Parameters: limit, offset, check_id, status

Generic CLI call

kosmo integrations:call pingdom.pingdom_list_alerts '{"limit":1,"offset":1,"check_id":1,"status":"example_status"}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_list_alerts '{"limit":1,"offset":1,"check_id":1,"status":"example_status"}' --json

`pingdom.pingdom_get_current_user`

Read read

Get details of the currently authenticated Pingdom user, including account info and credits.

Parameters: none

Generic CLI call

kosmo integrations:call pingdom.pingdom_get_current_user '{}' --json

Provider shortcut

kosmo integrations:pingdom pingdom_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`pingdom.pingdom_list_checks`

List all uptime checks in Pingdom. Returns check IDs, names, hostnames, statuses, and last test times.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_list_checks --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of checks to return (default: 100).
`offset`	integer	no	Offset for pagination (default: 0).
`status`	string	no	Filter by status: "up", "down", "paused", "unknown".
`tags`	string	no	Filter by tag (comma-separated).

`pingdom.pingdom_get_check`

Get detailed information about a specific Pingdom uptime check, including configuration, current status, and last test results.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_get_check --json

Parameter	Type	Required	Description
`check_id`	integer	yes	The ID of the check to retrieve.

`pingdom.pingdom_create_check`

Create a new uptime check in Pingdom. Supports HTTP, HTTPS, TCP, ping, DNS, UDP, SMTP, POP3, and IMAP check types.

Operation: Write write
Schema command: kosmo integrations:schema pingdom.pingdom_create_check --json

Parameter	Type	Required	Description
`name`	string	yes	Name of the check.
`host`	string	yes	Target hostname or IP address.
`type`	string	yes	Check type: "http", "https", "tcp", "ping", "dns", "udp", "smtp", "pop3", "imap".
`resolution`	integer	no	Check interval in minutes (1, 5, 15, 30, 60). Default: 5.
`url`	string	no	URL path for HTTP/HTTPS checks (e.g., "/health").
`port`	integer	no	Target port for TCP/UDP checks.
`tags`	string	no	Comma-separated tags for the check.
`send_string`	string	no	String to send for TCP/UDP checks.
`expect_string`	string	no	Expected response string for TCP checks.
`contactids`	string	no	Comma-separated contact IDs to alert.

`pingdom.pingdom_list_results`

List summary results for a Pingdom uptime check. Returns response times and status summaries.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_list_results --json

Parameter	Type	Required	Description
`check_id`	integer	yes	The ID of the check.
`from`	integer	no	Start timestamp (Unix epoch) for the results window.
`to`	integer	no	End timestamp (Unix epoch) for the results window.
`limit`	integer	no	Maximum number of results to return.
`offset`	integer	no	Offset for pagination.

`pingdom.pingdom_get_results`

Get detailed test results for a Pingdom uptime check, including individual probe responses and response times.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_get_results --json

Parameter	Type	Required	Description
`check_id`	integer	yes	The ID of the check.
`from`	integer	no	Start timestamp (Unix epoch) for the results window.
`to`	integer	no	End timestamp (Unix epoch) for the results window.
`limit`	integer	no	Maximum number of results to return.
`offset`	integer	no	Offset for pagination.
`probes`	string	no	Comma-separated probe IDs to filter by.
`status`	string	no	Filter by result status: "up", "down", "unconfirmed_down".

`pingdom.pingdom_list_alerts`

List alerts for the Pingdom account. Returns alert details including check ID, contact, and alert type.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_list_alerts --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of alerts to return (default: 100).
`offset`	integer	no	Offset for pagination (default: 0).
`check_id`	integer	no	Filter alerts by check ID.
`status`	string	no	Filter by alert status: "sent", "not_sent", "scheduled".

`pingdom.pingdom_get_current_user`

Get details of the currently authenticated Pingdom user, including account info and credits.

Operation: Read read
Schema command: kosmo integrations:schema pingdom.pingdom_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.