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 MCP Integration for Codex

Connect Pingdom to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Pingdom feedback View package source

Connect Pingdom to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Pingdom MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-pingdom": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=pingdom",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=pingdom --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Pingdom instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Pingdom Tools Visible to Codex

Codex sees stable MCP tool names generated from the Pingdom integration catalog.

MCP tool	Source function	Type	Description
`integration__pingdom__pingdom_list_checks`	`pingdom.pingdom_list_checks`	Read	List all uptime checks in Pingdom. Returns check IDs, names, hostnames, statuses, and last test times.
`integration__pingdom__pingdom_get_check`	`pingdom.pingdom_get_check`	Read	Get detailed information about a specific Pingdom uptime check, including configuration, current status, and last test results.
`integration__pingdom__pingdom_create_check`	`pingdom.pingdom_create_check`	Write	Create a new uptime check in Pingdom. Supports HTTP, HTTPS, TCP, ping, DNS, UDP, SMTP, POP3, and IMAP check types.
`integration__pingdom__pingdom_list_results`	`pingdom.pingdom_list_results`	Read	List summary results for a Pingdom uptime check. Returns response times and status summaries.
`integration__pingdom__pingdom_get_results`	`pingdom.pingdom_get_results`	Read	Get detailed test results for a Pingdom uptime check, including individual probe responses and response times.
`integration__pingdom__pingdom_list_alerts`	`pingdom.pingdom_list_alerts`	Read	List alerts for the Pingdom account. Returns alert details including check ID, contact, and alert type.
`integration__pingdom__pingdom_get_current_user`	`pingdom.pingdom_get_current_user`	Read	Get details of the currently authenticated Pingdom user, including account info and credits.

Related Pingdom Pages

Pingdom CLIUse direct JSON commands instead of MCP discovery. Pingdom MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.