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 Headless Automation

Use the Pingdom CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API key auth

Submit Pingdom feedback View package source

Pingdom CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Pingdom CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Pingdom CLI for Headless Automation
kosmokrator integrations:configure pingdom --set api_key="$PINGDOM_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call pingdom.pingdom_list_checks '{"limit":1,"offset":1,"status":"example_status","tags":"example_tags"}' --json

Discovery Before Execution

Agents and scripts can inspect Pingdom docs and schemas 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

Useful Pingdom CLI Functions

Function	Type	Parameters	Description
`pingdom.pingdom_list_checks`	Read	limit, offset, status, tags	List all uptime checks in Pingdom. Returns check IDs, names, hostnames, statuses, and last test times.
`pingdom.pingdom_get_check`	Read	check_id	Get detailed information about a specific Pingdom uptime check, including configuration, current status, and last test results.
`pingdom.pingdom_create_check`	Write	name, host, type, resolution, url, port, tags, send_string, expect_string, contactids	Create a new uptime check in Pingdom. Supports HTTP, HTTPS, TCP, ping, DNS, UDP, SMTP, POP3, and IMAP check types.
`pingdom.pingdom_list_results`	Read	check_id, from, to, limit, offset	List summary results for a Pingdom uptime check. Returns response times and status summaries.
`pingdom.pingdom_get_results`	Read	check_id, from, to, limit, offset, probes, status	Get detailed test results for a Pingdom uptime check, including individual probe responses and response times.
`pingdom.pingdom_list_alerts`	Read	limit, offset, check_id, status	List alerts for the Pingdom account. Returns alert details including check ID, contact, and alert type.
`pingdom.pingdom_get_current_user`	Read	none	Get details of the currently authenticated Pingdom user, including account info and credits.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Pingdom CLI Pages

CI Pingdom CLI for CI. Cron Jobs Pingdom CLI for cron jobs. Shell Scripts Pingdom CLI for shell scripts. Coding Agents Pingdom CLI for coding agents.