ContentStudio API plan is now available. Create automations using Claude, Zapier, n8n, make, etc. Explore plan!

contentstudio-cli

Run your social media from the terminal

Schedule posts, manage approvals, and upload media with the ContentStudio CLI. Run commands in bash and CI pipelines, or let Claude Code, Cursor, or Codex handle them.

$npm install -g contentstudio-cli

Set up with your agent Read the CLI guide

Works with your ContentStudio API key · npm or pnpm · every command speaks JSON

$contentstudio auth:login --api-key cs_••••••••# saves your key locally and verifies it$contentstudio --json accounts:list --platform linkedin{ "ok": true, "data": [ … ] }$contentstudio --json posts:create -c "Excited to share our Q2 roadmap" -i <linkedin_id> -t scheduled -s "2026-05-01 09:00:00"{ "ok": true, "data": { … } }

Set it up once, then let your agent drive

The CLI comes with a skill file that teaches your AI agent every ContentStudio command. Paste the setup into your agent, or run it yourself.

1
Set up ContentStudio in Claude Code
Install the CLI and the skill, then log in with your API key.
Set up ContentStudio so I can manage social posts from here. 1. Install the CLI: npm install -g contentstudio-cli 2. Add the skill: npx skills add contentstudioio/contentstudio-agent 3. Ask me for my API key, then run: contentstudio auth:login --api-key <key> 4. Confirm it works: contentstudio workspaces:list
Set up ContentStudio in Cursor
The Agent runs each step in the integrated terminal and, by default, asks before running commands.
Set up ContentStudio so I can manage social posts from here. 1. Install the CLI: npm install -g contentstudio-cli 2. Add the skill for Cursor: npx skills add contentstudioio/contentstudio-agent 3. Ask me for my API key, then run: contentstudio auth:login --api-key <key> 4. Confirm it works: contentstudio workspaces:list
Set up ContentStudio in Codex
Install the CLI and the skill, then log in with your API key.
Set up ContentStudio so I can manage social posts from here. 1. Install the CLI: npm install -g contentstudio-cli 2. Add the skill for Codex: npx skills add contentstudioio/contentstudio-agent 3. Ask me for my API key, then run: contentstudio auth:login --api-key <key> 4. Confirm it works: contentstudio workspaces:list
Connect ContentStudio to OpenClaw
OpenClaw installs the ContentStudio skill from ClawHub. Then add the CLI and log in.
```
$openclaw skills install @contentstudio-official/contentstudio$npm install -g contentstudio-cli$contentstudio auth:login --api-key cs_...
```
Set up ContentStudio from your terminal
Install, log in once, and set your active workspace. You can also authenticate with CONTENTSTUDIO_API_KEY.
```
$npm install -g contentstudio-cli$contentstudio auth:login --api-key cs_...$contentstudio workspaces:use <workspace_id>
```
2
Then just ask
Once the skill is in, your agent picks the right commands on its own.
- Schedule this changelog as a LinkedIn post for Monday at 9 AM.
- Upload the images in ./launch and make one Instagram post each.
- Show me what's still in draft for this week.
- Approve the two menu posts in Bloom Bakery.

Try a command

Explore six commands you can use for everyday social media tasks. Select one to see how it works.

Schedule a post

# Scheduled post to a Facebook page with one image$contentstudio --json posts:create -c "Our latest blog post is live!" -i <account_id> -t scheduled -s "2026-05-01 10:00:00" -m https://example.com/hero.jpg{ "ok": true, "data": { … } }

Post to three networks at once

# Repeat -i for each account$contentstudio --json posts:create -c "Cross-platform announcement" -i <facebook_id> -i <linkedin_id> -i <twitter_id> -t scheduled -s "2026-05-01 09:00:00"{ "ok": true, "data": { … } }

Upload a local file

# Upload a local file$contentstudio --json media:upload --file ./hero.jpg# the response includes an _id you can pass as --media-id$contentstudio --json posts:create -c "Post with library asset" -i <account_id> -t draft --media-id <media_library_id>{ "ok": true, "data": { … } }

Preview before you send

# Prints the full request body and exits without touching the API$contentstudio --json posts:create --dry-run -c "Test" -i <account_id> -t scheduled -s "2026-05-01 10:00"

Approve with a note

$contentstudio --json posts:approve <post_id> --comment "LGTM, ship it"{ "ok": true, "data": { … } }# Preview without acting$contentstudio --json posts:approve <post_id> --dry-run

Check another workspace

# Switch workspace for one command. Your saved default stays the same.$contentstudio --json --workspace <other_workspace_id> accounts:list{ "ok": true, "data": [ … ] }

Find the command for any task

Commands are grouped by what they manage. Add --json to get structured output that your scripts and AI agents can read.

Group	Command	What it does
auth	`auth:login --api-key cs_…`	Save and verify your key
	`auth:status`	Show stored config
	`auth:whoami`	Check the key against the API
	`auth:logout`	Forget credentials
workspaces	`workspaces:list`	All workspaces on your account
	`workspaces:use <id>`	Set the active one
	`workspaces:current`	Show the active one
discovery	`accounts:list`	Connected social accounts
	`campaigns:list`	Campaigns and folders
	`categories:list`	Content categories
	`labels:list`	Labels
	`team:list`	Team members
posts	`posts:list`	Filter by status or date
	`posts:create`	Flags or a JSON body
	`posts:delete <id>`	Add --delete-from-social to remove it live
	`posts:approve <id>`	Approve with an optional comment
	`posts:reject <id>`	Send it back with a reason
comments	`comments:list <post_id>`	Comments and notes on a post
	`comments:add … --note`	Internal note, not public
	`comments:add … --mention <id>`	Tag a teammate
media	`media:list`	Filter by type, sort, search
	`media:upload --file <path>`	Upload a local file
	`media:upload --url <url>`	Import from a link

Global flags: --json --workspace <id> --base-url <url> --version --help. Run contentstudio <command> --help for every option.

Copy-ready automation recipes

Use these scripts as a starting point for common social media workflows. Find the recipe you need, update the account details and content, and run it with the ContentStudio CLI.

Schedule a daily post for the next 7 days.

1#!/bin/bash2ACCOUNT="<facebook_page_id>"3CONTENT=(4  "Monday motivation 💪"5  "Tuesday tips: keep it simple"6  "Wednesday wisdom from the team"7  "Throwback Thursday"8  "Friday vibes 🎉"9  "Weekend prep — try this"10  "Sunday reflections"11)12for i in "${!CONTENT[@]}"; do13  DATE=$(date -d "+$((i+1)) day 09:00" '+%F %T')14  contentstudio --json posts:create \15    -c "${CONTENT[$i]}" \16    -i "$ACCOUNT" \17    -t scheduled \18    -s "$DATE"19done

Cross-platform campaign: the same post on multiple platforms.

1#!/bin/bash2TIME="2026-05-01 10:00:00"3FB=$(contentstudio --json accounts:list --platform facebook | jq -r '.data[0]._id')4LI=$(contentstudio --json accounts:list --platform linkedin | jq -r '.data[0]._id')5TW=$(contentstudio --json accounts:list --platform twitter  | jq -r '.data[0]._id')6contentstudio --json posts:create \7  -c "Big launch today 🚀" \8  -i "$FB" -i "$LI" -i "$TW" \9  -t scheduled \10  -s "$TIME" \11  -m https://example.com/launch.jpg

Upload a folder of images, one post per image.

1#!/bin/bash2ACCOUNT="<instagram_id>"3for img in ./photos/*.jpg; do4  RESP=$(contentstudio --json media:upload --file "$img")5  MEDIA_ID=$(echo "$RESP" | jq -r '.data._id')6  TIME=$(date -d "+1 hour" '+%F %T')7  contentstudio --json posts:create \8    -c "$(basename "$img" .jpg)" \9    -i "$ACCOUNT" \10    -t scheduled \11    -s "$TIME" \12    --media-id "$MEDIA_ID" \13    --post-type feed14done

Bulk-delete drafts older than 30 days.

1#!/bin/bash2CUTOFF=$(date -d '-30 days' '+%Y-%m-%d')3contentstudio --json posts:list --status draft --date-to "$CUTOFF" --per-page 100 \4  | jq -r '.data[]._id' \5  | while read id; do6      contentstudio --json posts:delete "$id"7    done

Auto-approve posts from a trusted creator.

1#!/bin/bash2TRUSTED_USER_ID="<user_id>"3contentstudio --json posts:list --status pending_approval --per-page 50 \4  | jq -r --arg u "$TRUSTED_USER_ID" '.data[] | select(.created_by == $u) | ._id' \5  | while read id; do6      contentstudio --json posts:approve "$id" --comment "auto-approved (trusted creator)"7    done

Post types and platform options

Create simple posts with command flags. For platform-specific settings, such as TikTok privacy or YouTube categories, pass a JSON file using --body post.json.

Platform	Post types	How to set it
Facebook	Feed, Reel, Story, Reel + Story	`--post-type reel+story`
Instagram	Feed, Reel, Story	`--post-type feed \| reel \| story`
LinkedIn	Feed with image	`Flags`
X (Twitter)	Feed with image	`Flags`
YouTube	Videos and Shorts	`youtube_options: title, privacy, category, tags, license, made for kids`
TikTok	Video	`tiktok_options: privacy, duet, stitch, comments, disclosure flags`
Pinterest	Image pins	`pinterest_options: title, destination link`
Google Business Profile	Events	`gmb_options: topic type, dates, title, CTA`

Connect accounts from the terminal

OAuth platforms
Facebook, Instagram, X, LinkedIn, YouTube, TikTok, Pinterest, Google Business Profile, Threads, and Tumblr. You get a one-time link to open in your browser.
```
$contentstudio --json accounts:connect facebook
```
Bluesky
No browser needed. Connect with your handle and an app password from bsky.app → Settings → App Passwords.
```
$contentstudio --json accounts:add-bluesky --handle you.bsky.social --app-password xxxx-xxxx-xxxx-xxxx
```
Use an app password, never your main password.

Facebook Groups

Add a group by name, with an optional cover image.

$contentstudio --json accounts:add-facebook-group --name "My Community Group"

CLI, MCP server, or API?

Each option connects to your ContentStudio account. Choose the one that fits how you want to work.

	CLI (terminal)	MCP server	REST API
What it's for	Scripts, CI, and coding agents	AI assistants you talk to	Building ContentStudio into your product
Sign-in	API key	Your ContentStudio account	API key
Strong at	Local uploads, bulk jobs, dry runs	Analytics, inbox, conversation	Custom apps and pipelines
Used by	Bash scripts, CI/CD, Claude Code, Cursor, Codex	ChatGPT, Claude, Cursor, Grok, any MCP client	Your own backend

Every AI agent ContentStudio connects to

One account, one set of tools. Pick the agent you already work in, or browse all of them below.

Building something custom? Browse every ContentStudio integration.

FAQs

Book a 30 min call

Have questions? Schedule a quick call and we will guide you through everything.

Book a free call

What is the ContentStudio CLI?

A command-line tool that controls your ContentStudio workspace from the terminal. It schedules posts, uploads media, handles approvals, and manages comments through the same API your dashboard uses, so every change shows up there right away.

How do I install it?

Run npm install -g contentstudio-cli (or pnpm install -g contentstudio-cli), then check it with contentstudio --version.

Where do I get an API key?

In your ContentStudio dashboard, go to Settings → API Keys → Generate new key. It starts with cs_. Then run contentstudio auth:login --api-key cs_....

Do I need to log in every time?

No. auth:login saves your key locally, so you do it once. Check it anytime with contentstudio auth:status.

How do I use it with Claude Code, Cursor, or Codex?

Install the skill with npx skills add contentstudioio/contentstudio-agent and pick your agent when prompted. After that, your agent uses the CLI without extra prompting.

How do I preview a command without sending it?

Add --dry-run to any command that changes something. It prints the full request and exits without calling the API.

When do I need a JSON body instead of flags?

For platform-specific settings like TikTok privacy, YouTube categories, Pinterest links, or Google Business events, and for first comments, labels, campaigns, and approvals. Pass the file with --body /path/to/post.json.

What happens if I hit a rate limit?

The CLI retries automatically on 429 and 5xx errors, up to 2 times with exponential backoff, so you don't need your own retry logic.

Why am I getting a NotFoundError?

Usually the post, account, or file belongs to a different workspace. Check which one is active with workspaces:current, or pass --workspace <id> for that command.