Can I use Patreon as a CLI?

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

Can I expose Patreon through MCP?

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

Where are Patreon credentials stored?

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

Can I deny write access for Patreon MCP tools?

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

productivity

Patreon CLI for AI Agents

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

Patreon CLI Setup

Patreon can be configured headlessly with `kosmokrator integrations:configure patreon`.

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 patreon --set access_token="$PATREON_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor patreon --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_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`	`PATREON_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`PATREON_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 patreon.patreon_list_campaigns '{}' --json

Provider shortcut

kosmo integrations:patreon patreon_list_campaigns '{}' --json

Discovery

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

Discovery commands

kosmo integrations:docs patreon --json
kosmo integrations:docs patreon.patreon_list_campaigns --json
kosmo integrations:schema patreon.patreon_list_campaigns --json
kosmo integrations:search "Patreon" --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.

`patreon.patreon_list_campaigns`

List all campaigns for the authenticated Patreon creator. Returns campaign IDs, names, descriptions, and patron counts.

Read read

Parameters: none

Generic call

kosmo integrations:call patreon.patreon_list_campaigns '{}' --json

Shortcut

kosmo integrations:patreon patreon_list_campaigns '{}' --json

`patreon.patreon_get_campaign`

Get detailed information about a single Patreon campaign by its ID. Returns full campaign data including description, patron count, and creation date.

Read read

Parameters: campaign_id

Generic call

kosmo integrations:call patreon.patreon_get_campaign '{"campaign_id":"example_campaign_id"}' --json

Shortcut

kosmo integrations:patreon patreon_get_campaign '{"campaign_id":"example_campaign_id"}' --json

`patreon.patreon_list_members`

List members (patrons) for a Patreon campaign. Returns member IDs, names, email addresses, pledge amounts, and patron status.

Read read

Parameters: campaign_id

Generic call

kosmo integrations:call patreon.patreon_list_members '{"campaign_id":"example_campaign_id"}' --json

Shortcut

kosmo integrations:patreon patreon_list_members '{"campaign_id":"example_campaign_id"}' --json

`patreon.patreon_get_member`

Get detailed information about a single Patreon member by their ID. Returns member data including pledge details, patron status, and tier information.

Read read

Parameters: member_id

Generic call

kosmo integrations:call patreon.patreon_get_member '{"member_id":"example_member_id"}' --json

Shortcut

kosmo integrations:patreon patreon_get_member '{"member_id":"example_member_id"}' --json

`patreon.patreon_list_posts`

List posts for a Patreon campaign. Returns post IDs, titles, publication dates, and content metadata.

Read read

Parameters: campaign_id

Generic call

kosmo integrations:call patreon.patreon_list_posts '{"campaign_id":"example_campaign_id"}' --json

Shortcut

kosmo integrations:patreon patreon_list_posts '{"campaign_id":"example_campaign_id"}' --json

`patreon.patreon_get_post`

Get detailed information about a single Patreon post by its ID. Returns full post data including title, content, publish date, and tier access.

Read read

Parameters: post_id

Generic call

kosmo integrations:call patreon.patreon_get_post '{"post_id":"example_post_id"}' --json

Shortcut

kosmo integrations:patreon patreon_get_post '{"post_id":"example_post_id"}' --json

`patreon.patreon_get_current_user`

Get the profile of the currently authenticated Patreon user. Useful to verify the connection and see account details.

Read read

Parameters: none

Generic call

kosmo integrations:call patreon.patreon_get_current_user '{}' --json

Shortcut

kosmo integrations:patreon patreon_get_current_user '{}' --json

Function Schemas

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

patreon.patreon_list_campaigns 0 parameters

Schema command

kosmo integrations:schema patreon.patreon_list_campaigns --json

Parameter	Type	Required	Description
No parameters.

patreon.patreon_get_campaign 1 parameters

Schema command

kosmo integrations:schema patreon.patreon_get_campaign --json

Parameter	Type	Required	Description
`campaign_id`	string	yes	The ID of the campaign to retrieve.

patreon.patreon_list_members 1 parameters

Schema command

kosmo integrations:schema patreon.patreon_list_members --json

Parameter	Type	Required	Description
`campaign_id`	string	yes	The ID of the campaign to list members for.

patreon.patreon_get_member 1 parameters

Schema command

kosmo integrations:schema patreon.patreon_get_member --json

Parameter	Type	Required	Description
`member_id`	string	yes	The ID of the member to retrieve.

patreon.patreon_list_posts 1 parameters

Schema command

kosmo integrations:schema patreon.patreon_list_posts --json

Parameter	Type	Required	Description
`campaign_id`	string	yes	The ID of the campaign to list posts for.

patreon.patreon_get_post 1 parameters

Schema command

kosmo integrations:schema patreon.patreon_get_post --json

Parameter	Type	Required	Description
`post_id`	string	yes	The ID of the post to retrieve.

patreon.patreon_get_current_user 0 parameters

Schema command

kosmo integrations:schema patreon.patreon_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.