Can I use RunPod as a CLI?

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

Can I expose RunPod through MCP?

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

Where are RunPod credentials stored?

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

Can I deny write access for RunPod MCP tools?

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

productivity

RunPod CLI for Cron Jobs

Use the RunPod CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Bearer token auth

Submit RunPod feedback View package source

RunPod CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The RunPod CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# RunPod CLI for Cron Jobs
kosmokrator integrations:configure runpod --set access_token="$RUNPOD_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call runpod.runpod_list_pods '{}' --json

Discovery Before Execution

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

kosmo integrations:docs runpod --json
kosmo integrations:docs runpod.runpod_list_pods --json
kosmo integrations:schema runpod.runpod_list_pods --json
kosmo integrations:search "RunPod" --json
kosmo integrations:list --json

Useful RunPod CLI Functions

Function	Type	Parameters	Description
`runpod.runpod_list_pods`	Read	none	List all GPU pods in your RunPod account. Returns pod IDs, names, status, GPU types, and runtime details.
`runpod.runpod_get_pod`	Read	pod_id	Get detailed information about a specific RunPod GPU pod, including its status, GPU type, runtime, ports, and configuration. Use the pod ID obtained from runpod_list_pods.
`runpod.runpod_list_templates`	Read	none	List all available RunPod templates. Returns template IDs, names, images, and machine configurations.
`runpod.runpod_list_network_volumes`	Read	none	List all network volumes in your RunPod account. Returns volume IDs, names, sizes, and data center information.
`runpod.runpod_list_endpoints`	Read	none	List all RunPod endpoints. Returns endpoint IDs, names, statuses, and configuration details.
`runpod.runpod_list_serverless`	Read	none	List all serverless endpoints in your RunPod account. Returns endpoint IDs, names, statuses, and worker configurations.
`runpod.runpod_get_current_user`	Read	none	Get the profile of the currently authenticated RunPod user, including name, email, and 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 RunPod CLI Pages

CI RunPod CLI for CI. Shell Scripts RunPod CLI for shell scripts. Headless Automation RunPod CLI for headless automation. Coding Agents RunPod CLI for coding agents.