Can I use Podio as a CLI?

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

Can I expose Podio through MCP?

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

Where are Podio credentials stored?

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

Can I deny write access for Podio MCP tools?

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

productivity

Podio CLI for Cron Jobs

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

7 functions 7 read 0 write Manual OAuth token auth

Submit Podio feedback View package source

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

Command Shape

# Podio CLI for Cron Jobs
kosmokrator integrations:configure podio --set access_token="$PODIO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call podio.podio_list_spaces '{"org_id":1}' --json

Discovery Before Execution

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

kosmo integrations:docs podio --json
kosmo integrations:docs podio.podio_list_spaces --json
kosmo integrations:schema podio.podio_list_spaces --json
kosmo integrations:search "Podio" --json
kosmo integrations:list --json

Useful Podio CLI Functions

Function	Type	Parameters	Description
`podio.podio_list_spaces`	Read	org_id	List all workspaces (spaces) in a Podio organization. Returns space IDs, names, URLs, and membership details. Use this to discover available workspaces before exploring their apps and items.
`podio.podio_get_space`	Read	space_id	Get detailed information about a specific Podio workspace, including its name, description, URL, and settings. Use the space ID obtained from podio_list_spaces.
`podio.podio_list_apps`	Read	space_id	List all apps in a Podio workspace. Returns app IDs, names, item counts, and configuration. Use this to discover available apps before querying their items.
`podio.podio_get_app`	Read	app_id	Get detailed information about a specific Podio app, including its field definitions, layout, and configuration. Use this to understand the data structure before listing or filtering items.
`podio.podio_list_items`	Read	app_id, limit, offset, sort_by, sort_desc, filters	List and filter items in a Podio app. Supports filtering by field values, sorting, and pagination. Use podio_get_app first to understand the available fields for filtering.
`podio.podio_get_item`	Read	item_id	Get detailed information about a specific Podio item, including all field values, references, and metadata. Use the item ID obtained from podio_list_items.
`podio.podio_get_current_user`	Read	none	Get the status of the currently authenticated Podio user, including profile information, active organization memberships, 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 Podio CLI Pages

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