

Script your next post to WordPress. Authenticate once, then validate and apply schedules from a terminal, a cron job, or CI.
$ socialclaw login --api-key sc_live_your_key
Connected to SocialClaw at https://getsocialclaw.com
Workspace: North Loop Cafe
$ socialclaw apply -f wordpress-post.yaml
Run run_8f2k1xz9 created (1 post(s), model=posts_v1)
timezone: America/New_York
posts:
- account: wordpress:northloopcafe.com
name: Launch announcement
description: We just shipped real-time delivery status for every scheduled post.
publish_at: 2026-07-21T09:00:00-04:00
media_link: https://getsocialclaw.com/media/asset_example/dlv_example/launch-graphic.jpg
Connect an account, upload media, apply a schedule, and check on it again, all without leaving your terminal.
$ socialclaw accounts connect --provider wordpress --open
$ socialclaw assets upload --file ./launch-graphic.jpg --json
$ socialclaw apply -f wordpress-post.yaml --json
$ socialclaw status --run-id run_8f2k1xz9
Every post lands in the same place a person scheduling by hand would use.
Upload an image or a video once and reuse it across every scheduled WordPress post. SocialClaw hosts it for you, so WordPress always has what it needs the moment your post goes out.
Same workspace, same connected account, on whichever surface fits what you are building.
Schedule and manage WordPress posts visually. No code required.
Use with APIPublish to WordPress from your own backend with a workspace key. Full reference for request payloads, media, and error handling.
Use with MCPConnect Claude, ChatGPT, or Codex to the hosted MCP server and let the agent schedule WordPress posts in conversation.
Real quotes from Reddit, G2, Trustpilot, and Instagram.
“I can prepare the content once and let SocialClaw handle the distribution.”
“If SocialClaw sees this just know you changed my entire workflow girl.”
“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”
“Most schedulers still feel like old calendar tools with an AI caption button added on top. SocialClaw feels more built around the newer AI era.”
“SocialClaw if you want to schedule posts to social media.”
“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”
“I used to use stuff like Buffer etc, but I use SocialClaw with my AI agent. I just tell it to schedule like 100 videos for the next month.”
“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”
“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”
Connect once, then schedule and publish everywhere from the same workspace.
Run socialclaw login with your workspace API key. It is saved locally and reused by every command after that, so you only enter it once per machine.
Yes. Run socialclaw validate on your schedule file first. It checks the file against WordPress's rules and reports back without publishing anything. Run socialclaw apply on the same file once you are happy with it.
Yes. Every command accepts a saved API key and a flag for output a script can parse, so socialclaw apply fits cleanly into a cron job, a GitHub Action, or any other unattended pipeline.
Run socialclaw accounts connect with the WordPress provider and the open flag, and it launches the same authorization flow as connecting from the dashboard.
Yes. socialclaw assets upload takes a local file and returns a link you can reuse as the media for as many scheduled posts as you like.
Run socialclaw status with the run id that apply printed out, or socialclaw runs inspect for the full breakdown of every post in that run.
Yes. socialclaw install with the claude flag wires the CLI straight into Claude Code, and socialclaw mcp starts the same server behind SocialClaw's MCP tools, so an agent can drive it without you typing the commands yourself.
Every command and flag is documented at /docs/cli, with install steps and a schedule file example.