Use SuprPost from your AI assistant

Connect Claude, ChatGPT, Cursor or any app that speaks the Model Context Protocol (MCP), then plan, draft, schedule and fix posts by just asking. Everything it does goes through the same rules as the SuprPost app — your workspaces, accounts, team roles and plan.

Connect

Connect a new app

Point any MCP-compatible AI app at this server URL, then sign in and choose what it may do.

https://app.suprpo.st/api/mcp

1In Claude, go to Settings → Connectors.
2Select Add custom connector.
3Paste the server URL above and confirm.
4Click Connect, then sign in to SuprPost and approve the access you want to give.

You stay in control

Assistants save drafts by default, so you review what they wrote in SuprPost before anything goes out. When you connect an app you choose exactly what it may do, and you can disconnect it at any time from AI Agents & APIin SuprPost — access stops immediately. Posts an assistant creates are marked with the app's name.

View your workspaces and connected accounts
View your scheduled, draft, and published posts
Create, reschedule, and delete posts on your behalfIncludes scheduling — a scheduled post publishes on its own at the chosen time.
Publish posts immediately to your connected accountsLeave this off to keep the final say: the app can still draft and schedule, but can't publish anything right away.

Things to ask

“Draft next week's posts for our LinkedIn and Instagram around any holidays — save them as drafts.”
“Turn this blog post into a post for each of my accounts, shorter for X and Bluesky.”
“What's scheduled this week? Move Tuesday's post to Thursday at 10am.”
“Why did yesterday's LinkedIn post fail? Retry it if it's safe.”
“Which days in the last month did we not post anything?”

Some assistants also offer SuprPost's ready-made prompts: Plan a week of posts, Repurpose content per platform and Recover failed posts.

Tools

What your assistant can call. You don't need these names — just ask in plain words — but they help when you're building your own agent.

Know the workspace

Workspaces, connected accounts, and the options some platforms need.

list_workspacesRead-only: List the workspaces (brands or clients) this user can access, with each one's timezone and the user's role. Scheduled times are interpreted in the workspace's timezone. `isDefault` marks the workspace tools use when no workspaceId is passed.
list_social_accountsRead-only: List the connected social accounts in a workspace — the ids create_post targets. An account whose status isn't `connected` can't publish until the user reconnects it in SuprPost; tell them.
list_pinterest_boardsRead-only: List a connected Pinterest account's boards. Every Pinterest account a post targets needs a board — pass it in create_post's pinterest.boardIds.
search_threads_locationsRead-only: Search for a place to tag on a Threads post. Only works for Threads accounts with canTagLocation. Pass the chosen id as create_post's threads.locationId, and its name as threads.locationName so SuprPost can show the user which place was picked.

Create posts

Draft, check, schedule or publish — one post or a whole batch.

create_post: Create a post for one or more connected accounts: save it as a draft (recommended — the user reviews it in SuprPost), schedule it, or publish it now. The post type is worked out from the media: none = text, one image, a carousel, a video, or mixed media. Use perPlatform to tailor the caption or add a first comment per platform. Run check_post first to catch platform limits (caption length, media count) before saving. Confirm with the user before using mode "now".
check_postRead-only: Dry run: validate a post exactly as create_post would, then check each destination against its own platform's rules (caption length, media count, type and size). Nothing is saved. Returns each destination's readiness, the caption it would publish, and any issues.
create_bulk_posts: Create a batch of posts in one call — the fastest way to fill a content calendar. Each post has its own caption, media and (for mode "schedule") its own scheduledAt; all share the batch's accountIds unless a post sets its own. All-or-nothing: if any post is invalid, nothing is saved and every problem is listed. Prefer mode "draft" so the user can review the batch in SuprPost.
schedule_post: Schedule a new single-media post for a future time. Older, simpler form of create_post with mode "schedule" — prefer create_post.
publish_post: Create a single-media post and publish it immediately. Older, simpler form of create_post with mode "now" — prefer create_post. Confirm with the user first.

Manage posts

Find, edit, reschedule, publish, retry and clean up.

list_postsRead-only: List a workspace's posts, filtered by status (draft, scheduled, queued, recurring, published, failed), platform, account, or date range, newest first by default. Queued posts wait in a queue and recurring posts repeat on a rule; each of their publications is separate. Paged: pass nextOffset to continue.
list_scheduled_postsRead-only: Older name for list_posts — same inputs and results. Prefer list_posts.
get_postRead-only: Get one post in full: its content, per-platform settings, and each destination's outcome — published (with its URL), failed (with the reason), or still pending. Use it to check a publish, or to explain a failure before offering retry_failed_destination.
update_post: Change a draft or scheduled post. Send only what should change — everything omitted keeps its current value (get_post shows the current values). mode defaults to the post's current state; pass mode "schedule" with scheduledAt to schedule a draft, "draft" to unschedule, or "now" to publish it (confirm with the user first).
reschedule_post: Move a scheduled post to a new time. Only works on scheduled posts; to schedule a draft use update_post or bulk_schedule_posts.
cancel_schedule: Turn a scheduled post back into a draft, so it won't publish. Nothing is deleted.
duplicate_post: Copy any post — even a published or failed one — into a new draft with the same content, accounts and media. Handy for reposting or reusing a format.
delete_postDeletes data: Permanently delete a post from SuprPost. For a published post this removes SuprPost's record only — the post stays live on the platforms (except Threads, where the published Thread is deleted too). Confirm with the user before deleting.
publish_now: Publish a draft or scheduled post immediately. Publishing runs in the background — check get_post for each destination's result. Confirm with the user first.
retry_failed_destination: Retry publishing one failed destination of a post (by its accountId from get_post). Destinations that already published are never re-posted. If get_post marked it mayHavePublished, check the platform with the user first — it might be live already.
bulk_schedule_posts: Schedule several existing drafts at once, each at its own time — e.g. after the user approves a batch from create_bulk_posts. All-or-nothing: every post must be a draft in the same workspace, and every time must be in the future.

Media

Bring images and videos into the library.

attach_media_from_url: Download an image or video from a direct, public URL into the workspace's media library and return its mediaId for create_post. JPG, PNG, WebP and GIF up to 10 MB; MP4 and MOV up to 250 MB. The URL must serve the file itself — no sign-in, no HTML page, no redirect.
upload_media: Upload an image or video by its base64-encoded content and return its mediaId for create_post — for files with no public URL, like one the user attached to this chat. JPG, PNG, WebP and GIF up to 10 MB; MP4 and MOV up to 250 MB; base64 adds about a third to the size.
list_mediaRead-only: List the workspace's media library, newest first, so an existing image or video can be reused by its mediaId instead of uploading it again.

Plan

The calendar, holidays, posting cadence and past captions.

get_calendarRead-only: The workspace's calendar for a date range (max 92 days): every post on each day with its local time and status, plus holidays and observances (global, regional to the workspace's timezone, and the team's own custom days). Use it to plan around key dates and spot empty days before proposing posts.
get_posting_activityRead-only: How much the workspace has been posting: posts per day over a range (max 92 days, default the last 30), totals by status, the days with nothing posted, and how many posts are queued per account. Use it to find gaps and keep a steady cadence.
search_past_captionsRead-only: Search the workspace's previously used captions (or first comments), plus the ones the team saved to reuse — newest first, one entry per distinct text. Use it to match the brand's voice, reuse hashtags and sign-offs, and avoid repeating a recent caption.

Building a plain integration instead? The same actions are available over the REST API — create an API key in SuprPost under AI Agents & API. Sign in to get started.