Works with all AI agents

Connect your AI agent

Choose your assistant and connect in seconds.

Add to Claude

Works on every Claude plan, including free. Full Claude guide

  1. 1

    Add to Claude

    One click from Claude’s connector directory.

  2. 2

    Sign up or sign in

    Takes seconds, then you’re sent straight back.

  3. 3

    Ask Claude

    “Plan and schedule my posts for next week.”

The PostEverywhere CLI

Open source, on npm. @posteverywhere/cli lets you log in, connect accounts and publish to all top platforms without leaving the terminal. Every command emits JSON, so an AI agent can drive it as easily as you can.

Get started from as little as $9 per month. $0 due today, cancel anytime.

ChatGPTClaudeGeminiMicrosoft CopilotGrokCursorWorks with any AI agent
Creator profileBusiness owner profileSocial media manager profileEntrepreneur profileContent creator profile

Used by 2,831 happy customers

Terminal
@posteverywhere/cli
$ npm install -g @posteverywhere/cli$ posteverywhere login  Opening your browser…  Waiting for you to approve…  (Ctrl-C to cancel)  ✓ Logged in as you@yourbrand.com$ posteverywhere connect instagram  Waiting for you to finish in the browser…  (Ctrl-C to cancel)  ✓ Connected instagram as yourbrand$ posteverywhere post -c "Launch day" -a 123,456 --queue✓ Queued (2026-10-06T09:00:00Z) to 2 account(s).

Quickstart

Publish your first post in 90 seconds

Prefer not to install anything? Every command works through npx @posteverywhere/cli. Full walkthrough in the CLI guide.

Log in once.
A device-flow login, the same pattern as the GitHub CLI: approve in your browser and a scoped key is saved locally.
Connect your accounts.
Instagram, TikTok, LinkedIn and the rest connect in the browser. Bluesky, Telegram, Discord and WordPress connect without leaving the terminal.
Post, schedule or queue.
Publish now, schedule with -s, or add --queue and the post takes the next opening in your posting queue.
Quickstart
bash
$ npm install -g @posteverywhere/cli
$ posteverywhere login                 # opens your browser, saves a scoped key$ posteverywhere connect instagram     # OAuth flow, auto-detects the account$ posteverywhere accounts              # list connected accounts with ids$ posteverywhere post -c "Hello" -a 123,456
Publishing to 2 account(s)or schedule with -s, or queue with --queue

Why this CLI

What the PostEverywhere CLI gives you

Seventeen commands cover the whole publishing workflow: scheduling, the queue, media upload, captions, analytics, account health and retries. Included on every plan, from $9/mo.
  • Seventeen commands, one binary. Login, connect, publish, schedule, queue, upload, caption, analytics, retry. The whole workflow, not just a post endpoint wrapped in curl.

  • Ships as an agent skill. npx skills add posteverywhere/cli auto-detects Claude Code, Cursor, Codex and 70+ other agents, teaching the full command surface in one install.

  • JSON on every command. Pass --json, or just pipe the output and it turns on automatically. Agents and scripts act on structured results instead of parsing text.

  • Device-flow login. The same pattern as the GitHub CLI: approve in the browser, get a scoped key saved locally. No tokens to copy and paste, revocable any time.

Command reference

Every command

The complete surface, grouped by what it touches. Flags and worked examples for each are in the CLI guide, and the underlying endpoints are in the API reference.

Auth and identity

  • loginDevice-flow login in your browser, saves a scoped key
  • logoutRemove saved credentials
  • whoamiShow the authed account, plan and quota

Accounts

  • accountsList connected accounts with ids and health
  • connect <platform>Connect a new account
  • reconnect <accountId>Re-authorize an account whose token expired
  • account:health <id>Detailed health for one account

Publishing

  • postPublish now, schedule, or drop into the next queue slot
  • postsList posts, filterable by status and platform
  • queueShow the next queue slots for your accounts
  • results <postId>Per-platform publish results
  • retry <postId>Retry failed destinations

Media, AI and reporting

  • upload <url>Import an image or MP4 by URL, returns a media_id
  • captionGenerate captions by topic, platform and tone
  • analyticsAnalytics summary by week, month or all time
  • campaignsList campaigns
  • platform-rules [platform]Character limits, media constraints and supported features

Agent skill

Driving the CLI from an AI agent

One command installs the bundled skill and the agent learns the whole surface, no prompt engineering required. Then just ask.

For headless pipelines, skip login entirely and set POSTEVERYWHERE_API_KEY, which takes precedence over any saved key. If you would rather work conversationally inside an assistant than in a shell, the MCP server covers the same API, and the agents guide compares the two.

If you would rather connect over MCP inside your editor, there are setup guides for Cursor, Codex, Windsurf and Cline. For ready-made workflows to run once it is connected, see the skills and prompts.

Your coding agent
$ npx skills add posteverywhere/cli

schedule a post to all my accounts for tomorrow at 9am

$ posteverywhere accounts --json$ posteverywhere post -c "Doors open at 9." -a 123,456,789 -s 2026-10-07T09:00:00Z✓ Scheduled to 3 account(s).

Connect your AI agent

Prefer chat to the terminal? Connect an AI agent

Connect any AI agent.
Add PostEverywhere to ChatGPT, Claude, Grok, Perplexity, Cursor or any other AI app that supports MCP with one address. It takes seconds.
Ask in plain English.
“Plan next week's posts for all my accounts.” Your agent writes every post for you.
It schedules and publishes.
Your agent can post now, schedule for later or save a draft for you to review. Every post lands in your calendar, and scheduled posts go out on time through each network's official API.

$0 due today, cancel anytime

Connect your AI agent

Choose your assistant and connect in seconds.

Add to Claude

Works on every Claude plan, including free. Full Claude guide

  1. 1

    Add to Claude

    One click from Claude’s connector directory.

  2. 2

    Sign up or sign in

    Takes seconds, then you’re sent straight back.

  3. 3

    Ask Claude

    “Plan and schedule my posts for next week.”

FAQ

PostEverywhere CLI FAQs

Straight answers about plans, platforms and how scheduling works.

What is the PostEverywhere CLI?

A command line tool (@posteverywhere/cli) that lets you log in, connect social accounts, and schedule or publish posts to all top platforms without leaving the terminal. Install it globally with npm install -g @posteverywhere/cli, or run it ad hoc with npx @posteverywhere/cli. It is open source, and it talks to the same REST API as the dashboard.

Can an AI agent use the CLI?

Yes, and it ships with a skill file that teaches an agent the whole command surface in one install: npx skills add posteverywhere/cli auto-detects Claude Code, Cursor, Codex and 70+ other agents. Every command also accepts --json (automatically on when output is piped) and emits structured JSON, so an agent can act on what actually happened rather than parsing prose.

How does CLI login work?

A device-grant flow, the same pattern the GitHub CLI uses. Running posteverywhere login prints a short code, opens the approval page in your browser, and polls until you approve. It then saves a scoped API key to ~/.posteverywhere/config.json with 600 permissions. The key appears on the Developers page alongside dashboard-generated keys and can be revoked there at any time.

Which platforms can the CLI connect?

All top platforms. Instagram, Facebook, Threads, X, LinkedIn, TikTok, YouTube and Pinterest connect through the browser OAuth flow, and the CLI watches for the account to appear so there is no token to copy and paste. Bluesky, Telegram, Discord and self-hosted WordPress connect headlessly, prompting for an app password, bot token, channel webhook URL or WordPress application password respectively.

Can I run the CLI headlessly in CI?

Yes. Skip login entirely and set POSTEVERYWHERE_API_KEY with a key from the Developers page. The environment variable takes precedence over any saved login key, so the same commands work unchanged in a pipeline.

Should I use the CLI or the MCP server?

The CLI is the better fit when publishing belongs in a script or a command, because it composes with everything else in your shell and pipes cleanly into other tools. The MCP server is the better fit for conversational use inside an assistant like Claude or ChatGPT. Both talk to the same API and both are included on every plan, so it is a workflow preference rather than a capability difference.

Still have questions?

Contact us or browse the full FAQ.

Start 7-day free trial

$0 due today, cancel anytime

Publish from your terminal today

One install, one login, all top platforms. Included on every plan, with a 7-day free trial.