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 AI Agents

Use the Podio CLI from KosmoKrator to call Podio tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Podio CLI Setup

Podio can be configured headlessly with `kosmokrator integrations:configure podio`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure podio --set access_token="$PODIO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor podio --json
kosmokrator integrations:status --json

Credentials

Authentication type: Manual OAuth token oauth2_manual_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`PODIO_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`PODIO_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call podio.podio_list_spaces '{"org_id":1}' --json

Provider shortcut

kosmo integrations:podio podio_list_spaces '{"org_id":1}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

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

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`podio.podio_list_spaces`

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.

Read read

Parameters: org_id

Generic call

kosmo integrations:call podio.podio_list_spaces '{"org_id":1}' --json

Shortcut

kosmo integrations:podio podio_list_spaces '{"org_id":1}' --json

`podio.podio_get_space`

Get detailed information about a specific Podio workspace, including its name, description, URL, and settings. Use the space ID obtained from podio_list_spaces.

Read read

Parameters: space_id

Generic call

kosmo integrations:call podio.podio_get_space '{"space_id":1}' --json

Shortcut

kosmo integrations:podio podio_get_space '{"space_id":1}' --json

`podio.podio_list_apps`

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.

Read read

Parameters: space_id

Generic call

kosmo integrations:call podio.podio_list_apps '{"space_id":1}' --json

Shortcut

kosmo integrations:podio podio_list_apps '{"space_id":1}' --json

`podio.podio_get_app`

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.

Read read

Parameters: app_id

Generic call

kosmo integrations:call podio.podio_get_app '{"app_id":1}' --json

Shortcut

kosmo integrations:podio podio_get_app '{"app_id":1}' --json

`podio.podio_list_items`

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.

Read read

Parameters: app_id, limit, offset, sort_by, sort_desc, filters

Generic call

kosmo integrations:call podio.podio_list_items '{"app_id":1,"limit":1,"offset":1,"sort_by":"example_sort_by","sort_desc":true,"filters":"example_filters"}' --json

Shortcut

kosmo integrations:podio podio_list_items '{"app_id":1,"limit":1,"offset":1,"sort_by":"example_sort_by","sort_desc":true,"filters":"example_filters"}' --json

`podio.podio_get_item`

Get detailed information about a specific Podio item, including all field values, references, and metadata. Use the item ID obtained from podio_list_items.

Read read

Parameters: item_id

Generic call

kosmo integrations:call podio.podio_get_item '{"item_id":1}' --json

Shortcut

kosmo integrations:podio podio_get_item '{"item_id":1}' --json

`podio.podio_get_current_user`

Get the status of the currently authenticated Podio user, including profile information, active organization memberships, and account details.

Read read

Parameters: none

Generic call

kosmo integrations:call podio.podio_get_current_user '{}' --json

Shortcut

kosmo integrations:podio podio_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

podio.podio_list_spaces 1 parameters

Schema command

kosmo integrations:schema podio.podio_list_spaces --json

Parameter	Type	Required	Description
`org_id`	integer	yes	The Podio organization ID to list spaces for.

podio.podio_get_space 1 parameters

Schema command

kosmo integrations:schema podio.podio_get_space --json

Parameter	Type	Required	Description
`space_id`	integer	yes	The Podio space (workspace) ID.

podio.podio_list_apps 1 parameters

Schema command

kosmo integrations:schema podio.podio_list_apps --json

Parameter	Type	Required	Description
`space_id`	integer	yes	The Podio space (workspace) ID to list apps for.

podio.podio_get_app 1 parameters

Schema command

kosmo integrations:schema podio.podio_get_app --json

Parameter	Type	Required	Description
`app_id`	integer	yes	The Podio app ID.

podio.podio_list_items 6 parameters

Schema command

kosmo integrations:schema podio.podio_list_items --json

Parameter	Type	Required	Description
`app_id`	integer	yes	The Podio app ID to list items from.
`limit`	integer	no	Maximum number of items to return (default: 20, max: 500).
`offset`	integer	no	Offset for pagination (default: 0).
`sort_by`	string	no	The field to sort by. Use "created_on" or "last_event_on" for built-in sorting, or a field external ID.
`sort_desc`	boolean	no	Sort in descending order (default: true).
`filters`	string	no	JSON-encoded filter object. Keys are field external IDs, values are the filter criteria. Example: '{"title":"My Item"}'

podio.podio_get_item 1 parameters

Schema command

kosmo integrations:schema podio.podio_get_item --json

Parameter	Type	Required	Description
`item_id`	integer	yes	The Podio item ID.

podio.podio_get_current_user 0 parameters

Schema command

kosmo integrations:schema podio.podio_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.