One queue · seven networks

A social media scheduler that tells you the truth about every post

Queue a post once and PostMCP AI delivers it to LinkedIn, X, Facebook, Instagram, Threads, Bluesky and YouTube Shorts — each as its own delivery, with its own status, permalink and error. No silent failures, no guessing which network dropped it.

Free forever plan · 5 profiles · no card

Queue · Tue 14 OctEngine live
  • 09:00
    LinkedIn · Company page
    Asia/Kolkata
    Published
  • 09:00
    X · @founder
    Asia/Kolkata
    Published
  • 11:30
    Instagram · Reel
    Europe/Berlin
    Scheduled
  • 11:30
    Threads · @studio
    Europe/Berlin
    Scheduled
  • 17:45
    Bluesky · @team.bsky
    America/New_York
    Retry queued
What is a social media scheduler?

A social media scheduler stores a post together with a future publish time and sends it to the network for you at that moment. PostMCP AI goes one level deeper: a scheduled post is not one item but one delivery per connected profile, so five targets produce five independently tracked publishes — five statuses, five permalinks, five retry paths — instead of a single row that either “worked” or didn’t.

The life of a scheduled post

Most schedulers show you two states: queued and sent. Here every stage is visible, and every stage is reversible until the moment of broadcast.

  1. 01

    Draft

    A post exists as copy plus a target list. Nothing is committed yet, so you can rewrite, re-target or throw it away with no cost.

  2. 02

    Pre-flight

    Before anything queues, the scheduler dry-runs the post: character limits per network, profiles that are not connected, missing media where a network demands it, and the exact credit cost.

  3. 03

    Scheduled

    The slot is stored as a wall-clock date and time plus an IANA timezone. 09:00 in Asia/Kolkata stays 09:00 in Asia/Kolkata across daylight-saving boundaries.

  4. 04

    Publishing

    At the slot the engine walks the target list and calls each network directly. One post per profile, so a LinkedIn failure never blocks the X delivery.

  5. 05

    Published or failed

    Every profile records its own status, the live permalink, and the upstream error if there was one. Retrying re-sends only the profiles that failed.

What each network will actually accept

Cross-posting fails on the network with the tightest rule. These are checked before a post ever enters the queue.

How cross-posting works
NetworkText limitMediaWorth knowing
LinkedIn3,000Image or videoPersonal profiles and company pages
X (Twitter)280Image or videoCosts 5 credits per delivery
Facebook63,206Image or videoPublishes to Pages you administer
Instagram2,200RequiredBusiness/Creator accounts, Reels for video
Threads500Image or videoPosts as the linked Instagram identity
Bluesky300Image or videoGraphemes, not bytes. Works with self-hosted PDS
YouTube Shorts5,000Video requiredTitle taken from the first line, 100 chars
Timezones, done properly

9:00 AM means 9:00 AM in March and in November

Schedulers that store a UTC instant quietly drift an hour twice a year. PostMCP stores the wall-clock date, the wall-clock time and the IANA zone the hour was meant in — Europe/Berlin, Asia/Kolkata, America/Sao_Paulo — and resolves it to UTC at publish time.

That matters most for the accounts you schedule furthest ahead: an evergreen queue built in summer still lands at the right local hour in winter.

Scheduling over the API without a timezone falls back to UTC. Pass it explicitly whenever the exact local hour is the point.

# schedule 9am local, next Tuesday
POST /api/tools/create_post
x-api-key: pmcp_sec_•••

{
  "content": "Changelog 4.2 is live.",
  "targetAccounts": [
    { "platform": "linkedin", "profileId": "lin_774…" },
    { "platform": "twitter",  "profileId": "tw_129…" }
  ],
  "scheduleDate": "2026-10-14",
  "scheduleTime": "09:00",
  "timezone": "Asia/Kolkata"
}
→ 2 deliveries queued · 6 credits

When a network says no, you find out — and you fix it in one click

Retry only what failed

Publishing again walks the delivery list and skips every profile that already succeeded. Nobody gets a duplicate post because one page rejected the image.

The upstream error, verbatim

A 403 from LinkedIn about a missing posting scope reads as exactly that, not as “something went wrong”. The fix is usually one reconnect away.

Nothing stays stuck

A post caught mid-publish can be released and re-armed. Delivered profiles keep their state, so the retry is genuinely partial.

Social media scheduling questions

What is a social media scheduler?+

A social media scheduler stores a post with a future publish time and sends it to the network on your behalf at that moment. PostMCP AI schedules to seven networks from one queue, records a separate delivery for every connected profile, and lets you edit, move, force-publish or cancel a post right up until it goes out.

How does timezone scheduling actually work?+

A slot is stored as a date, a time and an IANA timezone such as Europe/Berlin, not as a fixed UTC instant. The engine converts to UTC at publish time, so a 9:00 AM post stays at 9:00 AM local even when clocks change. If no timezone is passed through the API, the backend defaults to UTC — worth setting explicitly when the exact hour matters.

What happens if one network rejects the post?+

Nothing else stops. Each targeted profile is its own delivery row with its own status, post ID, permalink and error message. Publishing again retries only the profiles that failed and skips the ones already delivered, so nobody gets a duplicate.

Can I schedule different copy for each network?+

Yes. A 280-character X post and a 3,000-character LinkedIn essay can be scheduled from the same action — pass per-profile copy in targetAccounts, or use the variants map. The built-in AI agent can also rewrite one idea into per-network variants for you.

Is there a free social media scheduler plan?+

Yes. The Free Forever plan connects up to 5 social profiles, includes 20 publishing credits and 100k AI tokens per month, and gives you the full drag-and-drop calendar. No card required to start.

Can an AI assistant schedule posts for me?+

That is the point of PostMCP. The same scheduler is exposed as a Model Context Protocol server, so Claude, ChatGPT or Cursor can create, reschedule and retry posts through the same queue you see in the dashboard — with the same pre-flight checks.

Put a week of posts on the calendar in the next ten minutes

Connect five profiles free, queue your first post, and watch each delivery land with its own permalink.

Start free