8 Social Media CLI Tools for Scheduling Posts in 2026

The best CLI for scheduling social media posts from a script, a cron job or a coding agent, when you need to know that each post really went out, is PostWharf's wharf: one npm install, ten networks, a dry run that checks a post against every network before anything is queued, and a delivery line per network once it has gone, from $15 a month. We make PostWharf. For other needs, the other seven sort themselves out. Postiz is open source, can run on your own server and reaches 28 or more platforms by its own count. Zernio's MIT-licensed CLI also handles DMs, broadcasts and comment-to-DM automations. bundle.social's is built JSON-first for CI runners. PostEverywhere's starts at $9 a month. ContentStudio's brings approvals and workspaces for teams. PostNitro's designs a carousel before it schedules it. OpenTweet's posts to X only.

By · · 13 min read

Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.

Start PostWharf free: creating an account takes no card, Starter's first seven days are free, and the CLI comes with every plan.

How we chose and checked them

A CLI made the list when it met three conditions:

  • It is the vendor's own command-line tool, installable from npm, not a community wrapper around someone else's API.
  • It schedules. It can book a post for a later time from the command line, not only publish one now.
  • Its install command and its networks are stated on the vendor's own CLI page or repository, so the table below can be checked.

Each rival's CLI was read on 13 November 2026, from its own CLI page or its repository README, with prices from the vendor's pricing page the same day or, where marked, from our own list of social media posting APIs, read 22 October 2026. PostWharf's facts come from the wharf source and its CLI page, read on 13 November 2026. Three other CLIs turned up in the same searches and were left out. The pages we read for PostHero and poster.ly did not say which networks they post to, and SocialClaw (npm socialclaw) is described with different network counts in different places: its npm description names 11, and other listings give 9 and 13.

PostWharf is first for the job named at the top of this page, the job it was built for. The rest are ordered by how many networks each vendor says its CLI reaches. "Not on its CLI page" in the table means the page we read did not say, not that the thing is missing.

The eight at a glance

#CLIInstallNetworks (vendor's count)JSON outputSchedulesAgent and MCP usePrice entry pointOpen source or hosted
1PostWharfnpm i -g postwharf10 that publish--json on every command but sign-in--at "tue 9am"MCP server with 21 tools, same queue$15 a month, 7 days freeHosted
2Postiznpm install -g postiz28 or moreEvery command-s with a timestampAgent skill, MCP serverCloud $29 a month for 5 channels; self-hosting freeOpen source (AGPL-3.0), cloud or self-hosted
3Zernionpm install -g @zernio/cli16 by its README's countBy default--scheduledAtSKILL.md for agents, hosted MCP serverFirst 2 accounts covered by a monthly credit, then $6 an account (3rd to 10th), as of 22 Oct 2026CLI is MIT-licensed; hosted service
4bundle.socialnpx bundlesocial-cli15By default, on stdoutposts:scheduleSKILL.md, separate MCP serverFree plan: 20 posts a month, 3 accounts; Pro $100 a monthHosted
5PostEverywherenpm install -g @posteverywhere/cli13 in its platform listEvery command-s, or --queueAgent skill, MCP serverFrom $9 a month; 7-day trialCLI is MIT-licensed; hosted service
6ContentStudionpm install -g contentstudio-cli11 connectable from the CLIWith --json-t scheduled -sSkill for Claude Code, Cursor, Codex; MCP serverNot on its CLI pageHosted
7PostNitronpm install -g @postnitro/cli6JSON in, JSON outschedule createAgent skill, Claude Code plugin, MCP serverA paid plan plus a $10 a month API add-onCode on GitHub; hosted service
8OpenTweetnpm install -g @opentweet/cliX onlyNot on its CLI page--scheduleMCP server with 43 toolsFrom $19.99 a month; 7-day trialHosted

1. PostWharf

Best for: scripts, cron jobs and coding agents that publish for a brand and have to know, per network, whether each post landed.

wharf is the CLI in the postwharf npm package. It has no dependencies, runs on Node 20 or later and signs in with one workspace key, which it can read from the environment so a CI job writes nothing to disk. It writes to the same queue as the PostWharf dashboard, the MCP server and the REST API, so a post queued from a shell is the one your team sees in the browser. It publishes to Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Threads, Pinterest, Bluesky and Telegram.

Other CLIs here share pieces of its scripting: ContentStudio has a dry run, and Zernio and PostEverywhere retry failed posts. What sets wharf apart is having all of it in one tool, with a status check a job can fail on. --dry-run runs every check a real post runs, against every network on it, and creates nothing. --idempotency-key means running the same batch twice queues each post once. wharf retry resends only to the networks where a post failed. A refused command exits non-zero with a plain sentence saying what to change, and wharf status exits non-zero when any delivery in its window failed, so a cron job goes red when a post did not land. Starter is $15 a month for one workspace and 200 posts, with unlimited channels; compare the plans.

Where it falls short: Reddit, Discord, Snapchat and WordPress are request-only, so it cannot post there yet. Bluesky and Telegram report no figures back, and analytics looks back 30 days at most. One key reaches one workspace, so switching brands means switching keys. Every command and flag is on the CLI page, and the developer overview shows how the CLI, API and MCP server share one key.

Sources: postwharf.com/cli and the wharf README in PostWharf's repository, read 13 November 2026.

2. Postiz

Best for: teams that want to run the scheduler on their own servers, or that need the longest platform list here.

The Postiz CLI installs with npm install -g postiz and wraps Postiz's public API, which its docs say covers 28 or more platforms. You sign in through a browser device flow, which saves credentials to your home folder, or with an API key, and you can point the CLI at a self-hosted instance with a custom API address. Its commands cover creating and listing posts, uploads, per-channel and per-post analytics, and turning a long YouTube video into short vertical clips. The docs say every command outputs JSON, and an agent skill and an MCP server sit alongside it.

The Postiz repository is licensed AGPL-3.0, and its README sets out two ways to run it: Postiz Cloud, with a 7-day trial and channels limited by plan, or the self-hosted edition, free apart from your own infrastructure. Postiz's cloud plans page lists Standard at $29 a month for 5 channels.

Where it falls short: self-hosting means registering your own developer app on each platform and getting it approved, which the README warns can take weeks for Meta, YouTube and TikTok. On the cloud, the channel count is capped by plan tier.

Sources: docs.postiz.com/cli/introduction and github.com/gitroomhq/postiz-app, and docs.postiz.com/cloud/plans, read 13 November 2026.

3. Zernio

Best for: scripts that work on DMs, comments and broadcasts as well as posts.

Zernio's CLI installs with npm install -g @zernio/cli and prints JSON by default. A browser login creates an API key and saves it locally, or you can set one by hand. Posts are scheduled with posts:create --scheduledAt, and posts:retry resends a failed one. The command list goes well past publishing, into inbox conversations, comment replies, review replies, contacts, broadcasts, drip sequences and comment-to-DM automations. The CLI ships a SKILL.md so agents such as Claude Code can find it, and Zernio runs a hosted MCP server at mcp.zernio.com/mcp for chat clients. The README gives the CLI's licence as MIT. The CLI README counts 16 platforms and names 13 networks: Instagram, TikTok, X, LinkedIn, Facebook, Threads, YouTube, Bluesky, Pinterest, Reddit, Snapchat, Telegram and Google Business Profile.

Zernio prices by connected account rather than by plan. As of 22 October 2026, a monthly credit covers the first two accounts, and the 3rd to 10th cost $6 each.

Where it falls short: the per-account price grows with every account past the second, and most of the command list is inbox and messaging work that a team that only schedules posts will not use.

Sources: github.com/zernio-dev/zernio-cli README and zernio.com/agents, read 13 November 2026; pricing from our list of posting APIs, read 22 October 2026.

4. bundle.social

Best for: CI runners and shell-out agents that parse every response.

bundle.social's CLI runs with npx bundlesocial-cli, so a pipeline does not need a global install, and it needs Node 20 or later. The page describes it as built for non-interactive use: JSON on stdout, status text on stderr, an exit code per command, and prompts switched off unless you ask for them. It signs in with an organisation-wide API key and covers 15 platforms through posts:create, posts:schedule, media:upload, accounts:list and analytics:get. A SKILL.md ships in the package, and a separate MCP server serves chat clients.

Its pricing page lists a free plan with API access, 20 posts and 50 comments a month on 3 social accounts, and Pro at $100 a month for 10,000 posts, with a 14-day trial.

Where it falls short: the free plan's 20 posts a month runs out quickly for a scheduled job, so anything regular needs Pro. The CLI page also lists a short command set.

Sources: bundle.social/social-media-cli and bundle.social/pricing, read 13 November 2026.

5. PostEverywhere

Best for: posting into a queue of preset time slots, at a low monthly entry price.

PostEverywhere's CLI installs with npm install -g @posteverywhere/cli, or runs through npx. You log in with a browser device flow that saves a scoped key, and a key in the environment takes over for headless runs. The page counts 17 commands, from connecting accounts and posting to listing per-platform results, retrying failed destinations and reading each platform's character limits. A post can go out now, at a time set with -s, or into the next open slot with --queue. Every command can emit JSON, and the page says piping output turns it on. An agent skill detects Claude Code, Cursor and Codex, and an MCP server covers the same API. The platform list on the page names 13, including Discord, WordPress and Google Business Profile.

Plans start at $9 a month, and the CLI's code is MIT-licensed on GitHub.

Where it falls short: its upload command imports an image or MP4 from an address, so a local file has to be hosted somewhere first, and Instagram, TikTok and LinkedIn still connect through a browser.

Sources: posteverywhere.ai/cli and the posteverywhere/cli repository licence, read 13 November 2026.

6. ContentStudio

Best for: teams whose posts pass through approvals across several workspaces.

ContentStudio's CLI installs with npm install -g contentstudio-cli and signs in with an API key generated in the dashboard. Add --json to any command for structured output. Beyond creating scheduled posts, it can approve or reject a post with a comment, add internal notes, switch workspace for a single command, and preview a write with --dry-run. The FAQ says it retries rate-limit and server errors twice with backoff. From the terminal you can connect ten platforms through OAuth links plus Bluesky with an app password. A skill teaches Claude Code, Cursor and Codex the commands, and ContentStudio runs a separate MCP server for chat assistants.

Where it falls short: settings specific to one network, such as TikTok privacy or YouTube categories, need a JSON body file rather than flags, and the CLI page gives no price.

Source: contentstudio.io/social-media-cli, read 13 November 2026.

7. PostNitro

Best for: turning a topic or an article into a designed carousel and booking it in one command.

PostNitro's CLI installs with npm install -g @postnitro/cli and runs on Node 18 or later. It generates carousels, single images and short videos from a topic, an article address or an X post, renders them with your templates and brand kit, and schedules them to LinkedIn, Instagram, TikTok, Threads, Facebook and Pinterest. generate-and-schedule does the writing, the render and the booking in one step. Output is JSON on stdout with JSON errors on stderr, and the CLI shares its key and credits with PostNitro's API and MCP server. The code lives in the postnitro/postnitro-agent repository on GitHub.

Where it falls short: it needs a paid plan, and the API add-on costs $10 a month on top for 250 credits; Creator+ at $30 and Team+ at $60 a month include 200 and 500 credits. AI generation costs 2 credits a slide. Six networks is the shortest list here after OpenTweet.

Source: postnitro.ai/cli, read 13 November 2026.

8. OpenTweet

Best for: people who post only to X and want no X developer account.

OpenTweet's CLI installs with npm install -g @opentweet/cli and signs in with one OpenTweet API key, so you skip X's developer app and OAuth set-up. opentweet tweet publishes with --now or books a time with --schedule, and other commands list, publish and delete posts, show analytics and run an evergreen queue. The docs include a GitHub Actions step and say the CLI exits non-zero on error, so a failed post fails the job. An MCP server with 43 tools covers the same account.

Plans start at $19.99 a month, with a 7-day trial.

Where it falls short: it reaches X only, and long-form X Articles are not a CLI command yet, so those go through the REST API or MCP. The CLI docs do not say whether output is JSON.

Sources: opentweet.io/docs/cli and opentweet.io/pricing, read 13 November 2026.

What to check before you script one

A CLI that posts well at a keyboard can still fail quietly in a pipeline. Four checks catch most of it:

  • Sign-in with no prompt. A cron job or CI runner has no browser, so the CLI must accept a key from the environment or a flag. Every CLI above does.
  • A failure the job can see. A non-zero exit code on a refused post turns a silent miss into a red build. PostWharf, bundle.social, PostNitro and OpenTweet say so on the pages we read.
  • Safe re-runs. A job that is retried halfway can post twice. Look for an idempotency key or a dry run before the real call.
  • The network's own rules. A CLI cannot lift a platform's limits. Instagram, for one, publishes only from professional accounts, which our guide to posting to Instagram from the command line covers.

Start from the terminal

If your posts go out from a script or an agent and you need a line per network saying what landed, start PostWharf free, copy the workspace key and run npm i -g postwharf. Starter is $15 a month after its free week, with the CLI, the MCP server and the REST API included, and unlimited channels.

Common questions

Can I schedule social media posts from cron or a CI pipeline?

Yes, with any of the eight, as long as the job holds an API key as a secret. For a pipeline, prefer a CLI that exits non-zero when a post is refused and lets you re-run a failed job without posting twice. PostWharf's wharf does both: --idempotency-key ties a post to, say, a release tag, and wharf status exits non-zero when a delivery failed.

Is there a free social media CLI?

Postiz's self-hosted edition is free under AGPL-3.0, but you pay for the servers and register a developer app with each network yourself. Among the hosted tools, bundle.social has a free plan (20 posts a month on 3 accounts), and Zernio covers two accounts with a monthly credit. The rest offer trials: 7 days on PostWharf, Postiz Cloud, PostEverywhere and OpenTweet.

Does a social media CLI work with Claude Code or Codex?

Yes. Any CLI works in a coding agent that can run shell commands, and most of these ship a skill file that teaches the agent the commands. PostWharf gives Claude Code two routes into the same queue, the wharf CLI and the MCP server, set out in our guide to scheduling posts from Claude Code in the terminal.

Is there a self-hosted option?

Postiz is the one on this list with a self-hosted edition. Its CLI can point at your own instance, and the AGPL-3.0 licence lets you change the code.

Should an agent use the CLI or the MCP server?

Use the CLI where the agent already runs shell commands and you want each step in a log or a script. Use an MCP server where the agent is a chat client such as Claude or ChatGPT. All eight have an MCP server; our list of social media MCP servers compares the servers, and our social media posting APIs list covers calling the REST API directly.

Is there a CLI just for X?

OpenTweet's CLI posts only to X and needs no X developer account. Of the other seven, all but PostNitro reach X alongside their other networks.

PostWharf is priced per workspace rather than per connected channel, and every plan carries unlimited channels. See per-brand pricing.