Can I use PagerDuty as a CLI?

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

Can I expose PagerDuty through MCP?

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

Where are PagerDuty credentials stored?

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

Can I deny write access for PagerDuty MCP tools?

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

productivity

PagerDuty CLI for Headless Automation

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

7 functions 7 read 0 write API token auth

Submit PagerDuty feedback View package source

PagerDuty 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 PagerDuty CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# PagerDuty CLI for Headless Automation
kosmokrator integrations:configure pagerduty --set api_token="$PAGERDUTY_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call pagerduty.pagerduty_list_incidents '{"status":"example_status","urgency":"example_urgency","service_id":"example_service_id","team_id":"example_team_id","limit":1,"offset":1}' --json

Discovery Before Execution

Agents and scripts can inspect PagerDuty docs and schemas before choosing a function.

kosmo integrations:docs pagerduty --json
kosmo integrations:docs pagerduty.pagerduty_list_incidents --json
kosmo integrations:schema pagerduty.pagerduty_list_incidents --json
kosmo integrations:search "PagerDuty" --json
kosmo integrations:list --json

Useful PagerDuty CLI Functions

Function	Type	Parameters	Description
`pagerduty.pagerduty_list_incidents`	Read	status, urgency, service_id, team_id, limit, offset	List PagerDuty incidents. Filter by status (triggered, acknowledged, resolved), urgency (high, low), service ID, or team ID. Returns a paginated list of incidents.
`pagerduty.pagerduty_get_incident`	Read	id	Get full details for a single PagerDuty incident, including status, urgency, assignments, alerts, and timeline.
`pagerduty.pagerduty_list_services`	Read	team_id, limit, offset	List PagerDuty services. Optionally filter by team ID. Returns a paginated list of services with status and escalation policy info.
`pagerduty.pagerduty_get_service`	Read	id	Get full details for a single PagerDuty service, including status, escalation policy, integrations, and alert settings.
`pagerduty.pagerduty_list_teams`	Read	limit, offset	List PagerDuty teams. Returns a paginated list of teams with their names, descriptions, and parent team info.
`pagerduty.pagerduty_get_team`	Read	id	Get full details for a single PagerDuty team, including name, description, parent team, and default role.
`pagerduty.pagerduty_get_current_user`	Read	none	Get the profile of the currently authenticated PagerDuty user — name, email, role, time zone, and other account details.

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 PagerDuty CLI Pages

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