For agents and automations
A social media scheduler built for AI agents
An AI social media scheduler is only useful if the agent can use it safely. SimplePost gives agents the accounts you connected, checks every post against each network's rules, stores scheduled posts until they are due, and reports what happened on every account. Agents connect through MCP, the SimplePost CLI or the HTTP API.
Free 7-day trial includes MCP, the CLI and the API.
Quick answers
What agents get from SimplePost
- Real accounts, not guesses
- Agents list connected accounts and use their IDs. They never handle social network passwords or tokens.
- Validation before publishing
- Text length, media count, file types and required fields are checked per network, and again when a scheduled post becomes due.
- Safe retries
- An idempotency key makes a retried write with the same payload return the original post instead of a duplicate.
- Honest results
- Results are returned per account and per thread segment, so partial failures are visible.
Interfaces
Choose the interface that fits your agent
| Interface | Best for | Scheduling | Auth | Hosted plan |
|---|---|---|---|---|
| MCP server | Chat assistants and coding agents | Now, schedule, draft, edit, discard | OAuth | Every plan |
| Agent Skill | Teaching an agent SimplePost's rules in Codex, Claude Code, Cursor, OpenClaw and other skill-aware clients | Uses MCP or the CLI | Inherited | Free to install |
| CLI | Terminal scripts, CI jobs, local agents | Publishes immediately | Browser login (simplepost connect) or token | Advanced and Pro |
| HTTP API | Backend services and custom agents | Now, schedule, draft, webhooks | Bearer API key | Pro |
The TypeScript SDK and the local CLI can also publish with your own platform credentials and no hosted plan; they do not include hosted scheduling. See the interface comparison.
Safety model
Rules that keep agent publishing predictable
- Accounts are connected by a person in the web app; agents cannot add, remove or reauthorize them.
- Agents must use account IDs returned by SimplePost. The Agent Skill forbids inventing account, board, chat or post IDs.
- Drafts are saved even when they do not pass validation yet, and are clearly different from posts that are ready to publish.
- Every create request carries a new idempotency key; retries after a timeout reuse it.
- Drafts and future scheduled posts can be edited or discarded; published posts cannot be undone through SimplePost.
- Trial and plan allowances are enforced server-side, and agents are told the reason when a post is refused.
Patterns
Three common agent setups
Assistant in chat
A person drafts with ChatGPT or Claude, reviews the preview widget, and schedules. Connect with the directory listing; no code needed. ChatGPT · Claude
Coding agent at release time
Claude Code or Cursor reads the changelog and schedules announcements through MCP, or a CI job posts with the CLI right after deployment. Claude Code · Cursor
Autonomous or recurring agent
OpenClaw or your own service prepares a weekly digest, saves a draft for approval, and schedules it. Use MCP for an assistant, or the API with webhooks for a backend. OpenClaw
curl -X POST "https://app.simplepost.social/api/v1/posts" \
-H "Authorization: Bearer $SIMPLEPOST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message": "Weekly digest: three things we shipped",
"accountIds": ["REPLACE_WITH_ACCOUNT_ID"],
"postingMode": "schedule",
"scheduledFor": "2026-10-05T09:00:00+02:00",
"idempotencyKey": "digest-2026-w41"
}'simplepost setup --backend keychain
simplepost connect --url https://app.simplepost.social
simplepost account
simplepost post --app-account-id REPLACE_WITH_ACCOUNT_ID --text "v2.4.0 is live: offline mode"https://app.simplepost.social/mcpPlatforms
Where agents can publish
X, LinkedIn, Instagram, Facebook, Threads, Bluesky, TikTok, YouTube, Pinterest and Telegram, with the same rules in every interface. Native threads work on X, Bluesky, Threads and Telegram.
FAQ
Agent scheduling questions
What is a social media scheduler for AI agents?
It is a publishing service an agent can call with structured requests instead of driving a web interface. SimplePost gives agents connected accounts, per-network validation, drafts, scheduling and per-account results through MCP, a CLI and an HTTP API.
Which interface should my agent use?
Use MCP for assistants such as ChatGPT, Claude, Claude Code, Cursor or OpenClaw. Use the CLI for terminal scripts and CI jobs that publish immediately. Use the hosted HTTP API for backend services that need drafts, scheduling and webhooks.
How do I stop an agent from posting twice?
Send an idempotency key with every create request and reuse the same key only when retrying the same write. Reusing the key with the same payload returns the original post instead of creating a second one.
Can an agent schedule without me approving each post?
Yes, if you instruct it to. A request with exact content, accounts and time is enough to schedule. If you want approval, ask the agent to save drafts and show previews, then schedule after you confirm.
Which plan do agents need?
MCP works on every plan and the free trial. The hosted CLI needs Advanced or Pro, and the hosted HTTP API needs Pro. The free trial includes all three.
Give your agent a scheduler
7 days free · No credit card