Mixpost CLI
Mixpost CLI is the mixpost command. It lets you draft, schedule and review posts, manage media, tags
and mentions, and read analytics from your terminal. It works with Mixpost Cloud and with your own
self-hosted Pro or Enterprise instance.
It is made for three kinds of work:
- You, at a terminal. A quick way to schedule a post or check what's going out this week, without opening a browser tab.
- Scripts, cron jobs and CI. Output is JSON whenever it goes to a pipe, failures have their own exit codes, and destructive commands never run without confirmation.
- AI agents that work in a shell, such as Claude Code, Codex or Cursor. Ask for three posts about
your new feature scheduled for next week, and the agent can do it from start to finish with
mixpostcommands.
The CLI talks to the Mixpost API, which is available in Mixpost Cloud, Mixpost Pro v7 and Mixpost Enterprise v8. Mixpost Lite has no API. The CLI depends on endpoints that were added in those releases (such as listing your workspaces), so earlier versions are not supported.
Install
- Homebrew
- Install script
- Scoop (Windows)
- Go
- Docker
- Binary
On macOS and Linux:
brew install inovector/tap/mixpost
On macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/inovector/mixpost-cli/main/install.sh | sh
The script picks the build for your system, verifies its checksum, and installs it to /usr/local/bin.
If that directory is not writable, it installs to ~/.local/bin instead.
| Variable | Meaning |
|---|---|
MIXPOST_VERSION | install a specific release |
MIXPOST_INSTALL_DIR | install to a directory of your choice |
scoop bucket add inovector https://github.com/inovector/scoop-bucket
scoop install mixpost
go install github.com/inovector/mixpost-cli/cmd/mixpost@latest
docker run --rm -e MIXPOST_PERSONAL_KEY \
ghcr.io/inovector/mixpost-cli:latest post list -w acme
A container keeps no configuration between runs, so pass the key with MIXPOST_PERSONAL_KEY (and
MIXPOST_URL for a self-hosted instance) and pass the workspace with -w on each command.
Download the archive for your platform from the
releases page, extract it, and put mixpost on your
PATH.
On macOS, use Homebrew or the install script instead. Gatekeeper blocks unsigned binaries downloaded through a browser.
To check that it installed:
mixpost version
Quick start
1. Create a personal key. In your Mixpost dashboard, open the user menu, click API, then Create a personal key. The key is shown only once, so copy it right away. See Create a personal key for details.
2. Log in.
- Mixpost Cloud
- Self-hosted
mixpost auth login
mixpost auth login --url https://example.com/mixpost
Use the address you open Mixpost at, including its core path. See Self-hosted instances.
On a terminal, the CLI shows a link to the page where you create keys, then asks for the key. The key is not shown as you type. The CLI makes one test request to check the key before it saves anything.
3. Pick a workspace. Commands work on one workspace at a time. List the workspaces your key can access, then save one as the default:
mixpost workspace list
mixpost config set workspace 3bbd0951-5b04-432b-b2a0-688588b0720e
4. Start working.
mixpost account list # your connected social accounts
mixpost post create --text "Hello from the CLI" --account twitter --now
mixpost post list --status scheduled # what's going out next
What you can do
| Command | Purpose |
|---|---|
mixpost post | create, edit, schedule, queue, approve and delete posts |
mixpost media | upload files and URLs, organise them into folders |
mixpost tag | create, rename, recolour and delete tags |
mixpost mention | save the handles a person or brand uses on each network |
mixpost account | list the social accounts connected to a workspace |
mixpost analytics | followers, reach, post performance, best times to post |
mixpost workspace | list the workspaces your key can access |
mixpost raw | call any API endpoint the CLI doesn't have a command for |
mixpost auth, mixpost config | log in, manage profiles and settings |
Every command has built-in help with examples:
mixpost --help
mixpost post create --help
CLI or MCP?
Mixpost also includes an MCP server. Both let an AI agent run your social media workflow, but each one fits a different setup:
- Use the MCP server for chat apps that support MCP, such as Claude or ChatGPT on the web and desktop. You sign in with OAuth and there is nothing to install.
- Use the CLI for agents that already work in a shell, and for cron jobs and CI pipelines. Running one command costs less than keeping a protocol connection open, and the output is easy to pipe into other tools.
Shell completion
# zsh
mixpost completion zsh > "${fpath[1]}/_mixpost"
# bash
mixpost completion bash > /etc/bash_completion.d/mixpost
# fish
mixpost completion fish > ~/.config/fish/completions/mixpost.fish
Run mixpost completion <shell> --help for PowerShell and for how to load completions in your current
session.
Next steps
- Authentication and configuration: profiles, self-hosted instances, environment variables
- Commands: what each command can do, with examples
- Scripting and automation: output formats, exit codes, CI, and AI agents