Can I use Sprout Social as a CLI?

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

Can I expose Sprout Social through MCP?

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

Where are Sprout Social credentials stored?

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

Can I deny write access for Sprout Social MCP tools?

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

marketing

Sprout Social CLI for Shell Scripts

Use the Sprout Social CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Manual OAuth token auth

Submit Sprout Social feedback View package source

Sprout Social CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Sprout Social CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Sprout Social CLI for Shell Scripts
kosmokrator integrations:configure sproutsocial --set access_token="$SPROUTSOCIAL_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call sproutsocial.sproutsocial_list_profiles '{}' --json

Discovery Before Execution

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

kosmo integrations:docs sproutsocial --json
kosmo integrations:docs sproutsocial.sproutsocial_list_profiles --json
kosmo integrations:schema sproutsocial.sproutsocial_list_profiles --json
kosmo integrations:search "Sprout Social" --json
kosmo integrations:list --json

Useful Sprout Social CLI Functions

Function	Type	Parameters	Description
`sproutsocial.sproutsocial_list_profiles`	Read	none	List all social media profiles connected to the Sprout Social account. Returns profile IDs, service types (e.g., Twitter, Facebook, LinkedIn), and display names.
`sproutsocial.sproutsocial_get_profile`	Read	profileId	Get details of a specific social media profile in Sprout Social by its ID. Returns profile service type, display name, and account metadata.
`sproutsocial.sproutsocial_list_posts`	Read	count, page, status	List posts across social profiles in Sprout Social. Optionally filter by status (sent, scheduled, draft) and paginate results.
`sproutsocial.sproutsocial_create_post`	Write	text, profileIds, scheduledAt, media	Create and schedule a new social media post in Sprout Social. Provide the text content, target profile IDs, and optionally a scheduled time or media attachments.
`sproutsocial.sproutsocial_list_messages`	Read	count, page	List inbox messages and conversations in Sprout Social. Returns message IDs, sender info, and content snippets with pagination support.
`sproutsocial.sproutsocial_get_message`	Read	messageId	Get details of a specific message in Sprout Social by its ID. Returns sender info, message content, attachments, and conversation metadata.
`sproutsocial.sproutsocial_get_current_user`	Read	none	Get the currently authenticated Sprout Social user profile. Returns the user name, email, and account info.

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 Sprout Social CLI Pages

CI Sprout Social CLI for CI. Cron Jobs Sprout Social CLI for cron jobs. Headless Automation Sprout Social CLI for headless automation. Coding Agents Sprout Social CLI for coding agents.