Connect Claude to Socialync

Draft, schedule and publish posts to TikTok, Instagram, YouTube, X, LinkedIn, Facebook, Threads and Bluesky, and read how they performed. Toolspoke puts 28 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connection
Remote MCP server
Authentication
Socialync OAuth
Actions exposed
28
What a call bills
Nothing
Adapter
Maintained by Toolspoke
Category
Marketing

Connected in three steps

  1. Install Socialync

    Open the marketplace in your workspace, add Socialync to the project your agents work in, and it appears on the gateway immediately.

  2. Connect the credential

    Sign in to Socialync. Toolspoke holds the token encrypted and refreshes it when it expires.

  3. Point your agent at the gateway

    Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json
{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Socialync shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code

Run it in your project, then /mcp to sign in

claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop

Settings, then Connectors, then Add custom connector

https://toolspoke.com/mcp
Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project

{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex

~/.codex/config.toml

[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code

.vscode/mcp.json, or the MCP: Add Server command

{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Socialync asks for

Press connect and sign in to Socialync. Toolspoke keeps the token encrypted and refreshes it when it expires, so there is nothing to copy and nothing to rotate by hand.

The scopes it asks for

  • mcp:*

What Claude can do in Socialync

28 actions, each one declared by name in the connector. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

14 read, 7 write, 7 destructive

Reads

14

Fetches data and changes nothing.

  • list_profiles

    List the Socialync profiles this connection can manage. Returns each authorized profile with id, name, whether it is the default, and its connected-platform count. Call this first when posting and pass the chosen profile id as the profileId param on publish_now / publish_scheduled / create_post_draft / schedule_post_draft. Every profile can be managed by AI regardless of plan; what bounds a free-plan profile is its monthly post allowance, applied when posts publish.

  • list_connections

    List all connected social media platform accounts for a profile. Returns platform name, profile name, and connection status for each. A connection with requiresReconnect true cannot publish: its `reason` says why in plain words, and scheduled posts to it will fail until the user reconnects it in Socialync Settings. X connections also carry maxCaptionLength (280 free, 4000 with X Premium) and xPremium. Pass profileId to inspect a specific authorized profile; omit it to use the single/default authorized profile.

  • list_audiences

    List the user's saved audiences. An audience is a named group of connected accounts the user built in Socialync (e.g. "Core 12"), reusable as a posting target. Returns each audience with id, name, scope, member count, and the members (platform + account label). Pass an audience id as the audienceId param on create_post_draft / schedule_post_draft / publish_now / publish_scheduled to post to that group instead of listing platforms; anything the audience cannot reach on the chosen profile is reported back in skippedMembers.

  • list_media

    List media (videos/images) the user already has in Socialync, available to schedule via the mediaId parameter of schedule_post_draft / publish_scheduled. Sources: uploads from the last 24 hours, active drafts, and pending scheduled posts. Use this when the user wants to post "the video I just uploaded" or attached a video file in chat (you cannot receive video files -- send them to socialync.io to upload it, then find it here). IMPORTANT: items marked unattached expire about 12 hours after upload unless scheduled -- schedule them promptly.

  • check_quota

    Check the user's remaining post quota, subscription plan, and daily per-platform posting limits. Always call this before posting.

  • validate_post

    Validate a post BEFORE creating or publishing it. Checks caption length, link count, media type/count/size, image aspect ratio, video duration, and connection/token health for every target platform -- without creating anything. ALWAYS call this with the exact arguments you intend to pass to create_post_draft / schedule_post_draft / publish_now / publish_scheduled, BEFORE calling them, and again after any edit. Errors are guaranteed publish failures: fix them or drop that platform. Warnings publish but degraded (truncated caption, blur-fitted image, heuristic link count) -- surface them to the user before publishing. Pass scheduledFor to validate under the scheduled rules (all 8 platforms, video allowed); omit it for immediate-post rules. Does not check the daily quota (call check_quota). base64Images cannot be pre-validated -- they are checked at draft time once Socialync hosts them.

  • get_draft_status

    Check the status of a draft created via create_post_draft, schedule_post_draft or create_x_article_draft. Returns the current state (pending, approved, rejected, expired, published) so you can tell the user what happened. A pending draft is waiting for approve_draft after the user says yes in chat. Only returns drafts owned by this user.

  • get_scheduled_posts

    List the user's scheduled posts: pending ones plus recent failures. Shows platform, profileId, caption, scheduled time and status. `caption` is the text that platform will publish: its own override from platformSpecificSettings when the post has one (`captionIsPlatformOverride` is then true), otherwise the shared caption. `instagramTrialReel` is "MANUAL" or "AUTO" on an Instagram post that will publish as a Trial Reel, and null on every other post. A post with status "failed" carries an `error` object: `code` (stable, e.g. connection_signed_out, connection_reauth_required, trial_reel_ineligible, media_rejected, rate_limited, platform_unavailable), a plain `message` to relay to the user, `action` (reconnect, edit_post, retry, wait_and_retry), `retryable`, `retryAfterReconnect`, and the platform's raw `platformError`. When action is "reconnect", tell the user which account to reconnect in Socialync Settings; do not reschedule until they have. A post with status "held" did not publish because the account had no active plan (payment failing or plan ended) when it came due, and it will never publish late on its own: its `held` object has the reason and message, and the fix is to reschedule it. A still-pending post carries `onHold` when the account currently has no active plan: it publishes only if the payment goes through within an hour of its time, so tell the user to update their payment in Socialync Billing.

  • get_post_history

    Get the user's recent post history with per-platform success/failure tracking. Useful for checking what was posted and what failed. Each failed platform includes the raw `error` and a `reason` object (code, plain message, action, retryable) that says whether the fix is reconnecting the account, editing the post, or retrying. When the account has no active plan (payment failing or plan ended), the response carries `accountHold`: posts queued before it stay pending and do not publish until it is resolved, so a "pending" entry past its time means held, not stuck. get_scheduled_posts shows which posts are affected.

  • get_analytics

    Get aggregated analytics matching the Socialync analytics page. Returns totals (views, likes, comments, shares, saves, followers) plus period-over-period percentage changes. Set breakdown="by_platform" to get separate metrics for each connected platform (the comparison cards). Set includeTimeseries=true to also get daily snapshots per platform for trend analysis.

  • get_top_posts

    Get the user's posts with engagement metrics, ranked by engagement or recency. Returns the same data as the Top Performing Posts and Recent Posts tables on the analytics page: views, likes, comments, shares, engagement rate, and a status (viral/good/average/flop, or no_data when nothing has been collected for that post yet, which is never a flop). Video posts on Instagram, Facebook and YouTube also carry a "watch" block with how people watched (average watch time in seconds, share held past the 3 second mark, skip rate, replays, follows gained); includeRetention=true adds the retention curve (t = position in the video 0..1, v = share of plays still watching) and YouTube traffic sources.

  • get_post_insights

    Everything about ONE published post: views, likes, comments, shares, and for videos on Instagram, Facebook and YouTube how people watched it: average watch time, share of viewers still watching at 3 seconds (the hook), the retention curve (where viewers stopped watching), the biggest drop, replays, follows gained, YouTube traffic sources and YouTube's comparison with similar videos. Also returns the same post on every other platform it was published to, side by side, and how it compares with the user's median post on that platform. Use it to explain why a post worked or flopped and what to change in the next edit (e.g. "viewers left at 0:04, right after the intro"). Get post ids from get_top_posts or get_post_history. In clients that support interactive apps this renders as a chart the user can click to jump the video. Retention positions are in seconds when the video length is known.

  • get_comments

    Read the comments on one of the user's published posts: who said what, when, and the replies under each. Works for Instagram, YouTube, Threads, LinkedIn Company Pages (paid plans) and Bluesky; X, TikTok and Facebook comments are managed in the Socialync app. Use it to see what the audience is asking or reacting to, to spot ideas for the next post, or to find a comment to answer with reply_to_comment. Get post ids from get_top_posts or get_post_history. Shows up to the 60 most recent comments.

  • get_best_times

    Find the days and times the user's own posts got the most engagement, per platform, from their recent history. Returns up to 3 posting windows per platform (e.g. Tue 6 PM to 9 PM) with the number of posts behind each and their average engagement (likes + comments + shares) and views. A window needs at least 2 posts to count, so accounts with few posts get few or no windows; say so rather than guessing. Times are in the time zone you pass, or the zone the user schedules in. YouTube is not included. Use it to pick a scheduledFor for publish_scheduled or update_scheduled_post.

Writes

7

Creates or updates something on the other side.

  • create_media_upload

    Get presigned upload URLs for media you generated locally (e.g. rendered carousel slides or a video) that is too large to inline as base64Images. Returns one uploadUrl per file -- HTTP PUT each file's raw bytes to its uploadUrl with the matching "Content-Type" header (no auth header), then call finalize_media_upload with the returned uploadId. A batch is EITHER up to 10 images (one carousel, kept in order) OR exactly one video. Images: jpeg/png/webp/gif, max 25MB each. Video: max 512MB. Upload URLs expire in 1 hour. This is for media YOU produced; if the USER uploaded media in the Socialync app, use list_media instead. If the PUT can't connect (a sandbox network block, a proxy 403, "host not allowed", a DNS failure), do not retry it and do not call finalize_media_upload. Tell the user plainly that their AI app can't reach Socialync's upload server, then offer the two ways forward: (1) they add the file in Socialync (socialync.io: start a post and add the file, no need to finish it), come back, and you find it with list_media; or (2) they allow the upload host in their AI app's code or network settings and you try again. Images up to 8MB each can also go inline as base64Images instead.

  • finalize_media_upload

    Finalize a presigned upload started with create_media_upload, after you have PUT every file to its uploadUrl. Verifies the bytes landed, checks size/type, and returns a mediaId (e.g. "upload:abc123") usable in schedule_post_draft or publish_scheduled. For an image batch the single mediaId carries the whole carousel in upload order. The media is durable (hosted on Socialync's bucket), so you can schedule the post for any future publish date.

  • import-claude-motion-from-url

    Import a video made with Claude Motion into the user's Socialync media library so it can be posted. Use this when the user wants to post, schedule or send a Claude Motion video to Socialync. Call it promptly with the download URL Claude Motion provides (it expires within minutes). Returns a mediaId to pass to publish_scheduled or schedule_post_draft (video posts work on every platform, YouTube also needs a title). Importing does not publish anything. Schedule the video within 12 hours of importing: media that no post uses is cleaned up after that.

  • create_post_draft

    Hold a post as a pending draft WITHOUT sending it. Nothing reaches any platform until you show the user the exact post, they say yes in chat, and you call approve_draft(draftId); a draft nobody approves expires after 24 hours and the post never goes out. Never tell the user to open the Socialync app to approve it: the whole flow stays in this chat. When the user has already confirmed the post, call publish_now instead (one step). Returns a draft_id, expiry, and dailyDraftsRemaining. Supports up to 10 images total via imageUrls (public https URLs) and/or base64Images (image bytes). Cannot attach video. Cannot draft to TikTok or YouTube (use schedule_post_draft for those). Instagram requires at least one image. Hard cap: 10 drafts per UTC day per profile -- platform-security mechanism to keep the user's accounts under Meta/X/LinkedIn spam-detection thresholds, not a Socialync restriction. ALWAYS run validate_post with these same arguments FIRST and resolve every error it reports before calling this.

  • schedule_post_draft

    Hold a post to be SCHEDULED for future publishing as a pending draft WITHOUT scheduling it. Nothing enters the schedule until you show the user the exact post and time, they say yes in chat, and you call approve_draft(draftId); a draft nobody approves expires after 24 hours. Never tell the user to open the Socialync app to approve it: the whole flow stays in this chat. When the user has already confirmed the post, call publish_scheduled instead (one step). Once approved, it enters the scheduled queue and publishes automatically at scheduledFor. Returns a draft_id, expiry, and dailyDraftsRemaining for the target publish day. Media: up to 10 images via imageUrls/base64Images, OR one video via videoUrl, OR existing Socialync media via mediaId (from list_media). YouTube is allowed ONLY for video posts (and needs title). TikTok takes one video or a photo post of images (a swipeable photo carousel). Instagram requires media. Hard cap: 10 drafts per UTC day per profile (the day determined by scheduledFor). Each future day has its own independent 10-cap. ALWAYS run validate_post with these same arguments FIRST and resolve every error it reports before calling this.

  • create_x_article_draft

    Hold a native X ARTICLE -- the long-form rich-text format with a headline, NOT a regular post -- as a pending draft WITHOUT publishing it. Show the user the headline and full body, and when they say yes in chat call approve_draft(draftId); never tell the user to open the Socialync app to approve it. Use publish_x_article_now instead when the user has already confirmed in chat. The user's connected X account must have an X Premium subscription (any tier) -- without it X refuses with a 403 at publish time. Supported markdown: # ## ### headings, **bold**, *italic*, - bullet and 1. numbered lists, > blockquotes; links become "text (url)". Images, tables, and code blocks are NOT supported and degrade to plain text. Articles cannot be scheduled (X has no article scheduling) and count toward the same 10/day cap as posts.

  • generate_content

    Use Socialync's AI to generate platform-optimized captions. The AI knows each platform's tone, character limits, and best practices. Requires a paid plan; not available on the free plan.

Destructive

7

Deletes or permanently alters something. Worth granting on purpose.

  • approve_draft

    Publish a pending draft NOW (or, for scheduled drafts, move it into the scheduled queue). Call this AFTER the user has explicitly confirmed in chat that they want to publish the draft. Do NOT call without explicit user consent. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync also shows the user a confirmation dialog with the draft: a decline marks the draft rejected and comes back as success false with consent "declined" (never retry; ask the user); no answer within 40 seconds counts as the chat confirmation. The draft must have been created via create_post_draft, schedule_post_draft or create_x_article_draft, must still be pending, must belong to this user, and must not be expired. Returns per-platform success/failure for immediate publishes, or scheduled post IDs for scheduled publishes. A scheduled draft whose time has already passed cannot be approved as is: confirm a new time with the user and pass it as scheduledFor.

  • publish_now

    Publish a post IMMEDIATELY to one or more platforms. PREFERRED tool when the user is interacting with you in chat -- it skips the Socialync drafts page entirely. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync shows the user a confirmation dialog with the exact post before publishing: a decline rejects it and comes back as success false with consent "declined" (never retry; ask the user), and no answer within 40 seconds counts as the confirmation the user already gave you in chat. On other clients there is NO dialog and this publishes as soon as you call it. Either way, before calling you MUST show the user the exact caption, platforms, and images you will post, and get their explicit confirmation in the chat. Treat this the same way you would treat sending an email on someone's behalf. If the user uploaded image(s) to you in the conversation, pass them via base64Images (preferred) -- Socialync will host them for you. If the user gave you a public image URL, pass it via imageUrls. Returns per-platform success/failure. Same validation as create_post_draft: text and/or up to 10 images total (URLs + base64 combined), Instagram requires at least one image, no TikTok/YouTube (use publish_scheduled for those), 10/day cap per profile (platform-security mechanism to keep accounts under spam-detection thresholds). ALWAYS run validate_post with these same arguments FIRST and resolve every error it reports before calling this.

  • publish_x_article_now

    Publish a native X ARTICLE immediately -- the long-form rich-text format with a headline, NOT a regular post. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync shows the user a confirmation dialog with the headline and body before publishing (a decline comes back as success false with consent "declined"; never retry it; no answer within 40 seconds counts as the chat confirmation). On other clients there is NO dialog. Either way, before calling, show the user the exact headline and full body and get their explicit confirmation in chat, the same way you would before sending an email on their behalf. Returns the article id and the URL of the seed post that announces it. The user's connected X account must have an X Premium subscription (any tier) -- without it X refuses with a 403 at publish time. Supported markdown: # ## ### headings, **bold**, *italic*, - bullet and 1. numbered lists, > blockquotes; links become "text (url)". Images, tables, and code blocks are NOT supported and degrade to plain text. Articles cannot be scheduled (X has no article scheduling) and count toward the same 10/day cap as posts.

  • publish_scheduled

    Schedule a post for future publishing. PREFERRED tool when the user is interacting with you in chat -- skips the Socialync drafts page. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync shows the user a confirmation dialog with the exact post and time before it enters the queue: a decline rejects it and comes back as success false with consent "declined" (never retry; ask the user), and no answer within 40 seconds counts as the confirmation the user already gave you in chat. On other clients there is NO dialog: once you call this, the post enters the scheduled queue and will publish automatically at scheduledFor. Either way, before calling, show the user the caption, platforms, media, and the scheduled time, and get their explicit confirmation in chat. Media options: base64Images (user uploaded images to you in chat), imageUrls (public https), videoUrl (ONE public https video URL -- Socialync copies it into its own storage at call time), or mediaId (media already in Socialync, from list_media -- use for "the video I uploaded"). YouTube allowed for VIDEO posts only (and needs title). TikTok takes one video or a photo post of images (a swipeable photo carousel). Returns scheduled post IDs. Same validation as schedule_post_draft. 10/day cap per profile per publish day (UTC date of scheduledFor). ALWAYS run validate_post with these same arguments FIRST and resolve every error it reports before calling this.

  • update_scheduled_post

    Change a scheduled post that has not published yet: its time, its caption (for every platform, or per platform), the YouTube title, the first comment, or drop platforms from it. Pass a groupId to change every platform of a grouped post together (the ids publish_scheduled returns share a groupId), or a postId for one platform's entry. Prefer this over delete_scheduled_post plus a new post: it keeps the post's id, media and settings. Media cannot be swapped and platforms cannot be added here; for that, cancel and schedule again. Before calling, show the user exactly what will change and get their explicit confirmation in chat. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync also shows a dialog; a decline changes nothing and comes back as success false with consent "declined". A new time must be at least 3 minutes away and inside the plan's scheduling window; moving a post to another UTC day uses that day's 10-post allowance. Posts already publishing, published, failed or cancelled are skipped with a reason. Call get_scheduled_posts to find ids.

  • delete_scheduled_post

    Cancel a pending scheduled post before it publishes. Pass a postId to cancel a single platform entry, or a groupId to cancel every platform in a grouped multi-platform post at once (the ids publish_scheduled returns together share a groupId). Destructive and not undoable -- show the user what will be cancelled and get explicit confirmation in chat first. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync also asks the user to confirm the cancellation in a dialog; a decline cancels nothing and comes back as success false with consent "declined"; no answer within 40 seconds counts as the chat confirmation. Already-published posts cannot be cancelled. Call get_scheduled_posts to find ids.

  • reply_to_comment

    Reply to one comment on one of the user's published posts, as the user's own account, on Instagram, Threads, LinkedIn Company Pages (paid plans) or Bluesky. The reply is public and goes out immediately. Before calling, show the user the comment and the exact reply and get their explicit confirmation in chat, one reply at a time; never reply in bulk or without the user seeing each one. If the user has switched on the publish confirmation dialog in Socialync settings and their client supports MCP elicitation, Socialync also shows a dialog; a decline sends nothing and comes back as success false with consent "declined". YouTube and X replies are sent by the user in the Socialync app. Get the commentId from get_comments. Limit: 30 replies per day.

What it will not do

The gateway enforces each of these, so they can be stated flatly.

It cannot call anything else
The 28 actions above are the whole of it. A call to any other name is refused before it reaches Socialync rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential
Toolspoke holds no access to Socialync of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Socialync
Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Socialync. An agent has to ask.
It does not smooth over provider limits
Toolspoke does not retry, queue or back off around Socialync's own rate limits. A call that Socialync refuses comes back to the agent as a failed call.

Using Socialync with an agent

Written by whoever built this connector. Agents read the same text on demand through read_guide, so what is below is what they see.

Through Toolspoke, call each tool by its search_tools name (socialync__list_profiles and so on). Read live plan limits from check_quota.

You are connected to Socialync, a social media management platform, via MCP.

THE MOST IMPORTANT RULES (read these first):

  1. THE USER MUST CONSENT TO EVERY POST. You have two ways to publish: (a) Direct publish via publishnow / publishscheduled, fastest, but you MUST show the user the exact caption, platforms, images, and timing FIRST and get their explicit "yes" in chat before calling. Treat this like sending an email on someone's behalf: confirm first, then send. Do NOT call publishnow / publishscheduled without explicit user confirmation in chat. Logging proves who consented and when. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync ALSO shows the user its own confirmation dialog with the exact post when you call these tools; a decline comes back as success false with consent "declined" and the draft is rejected. Never retry a declined publish; ask the user instead. No answer within 40 seconds counts as the confirmation the user already gave you in chat, so that confirmation must be real. (b) Two steps in chat via createpostdraft / schedulepostdraft, then approvedraft. The draft tools HOLD the post as a pending draft and send nothing; you then show the user the exact post, and when they say yes in chat you call approvedraft(draftId). Use this when you want the content locked in before the user confirms (a batch they approve one by one, or a post you built before they were ready). The whole flow stays in this chat: NEVER tell the user to open Socialync to approve a draft and never leave a draft waiting for them in the app. A draft nobody approves within 24 hours expires and the post never goes out. Never publish without consent. There is no auto-approve mode that bypasses the user.
  2. MEDIA. Images: imageUrls (up to 10 public https URLs) or base64Images (user uploaded images to you in chat) on any drafting/publishing tool. Video: ONE video per post, on the SCHEDULED tools only (schedulepostdraft / publishscheduled), immediate publishing (createpostdraft / publishnow) is images/text only because platform video processing takes minutes. Two ways to attach video: (a) mediaId, media the user already has in Socialync. Call listmedia to see it. THIS IS THE NORMAL PATH for video. (b) videoUrl, a public https URL, for users who have their video hosted somewhere already. IF THE USER ATTACHES A VIDEO FILE IN THE CHAT: you cannot receive video files (chat tool calls can't carry video bytes, this is a protocol limit, not a Socialync one). Do NOT make them find external hosting. Say: "I can't receive video files directly, but here's the quick path: upload it in Socialync (socialync.io, just start a post and add the video, you don't even need to finish it), then come back and tell me to schedule it." Then call listmedia to find it the moment they're back. A video post cannot also carry images. Socialync copies caller-supplied image and video URLs into its own storage when you draft or schedule, so a link only has to work at the moment you call the tool; presigned or expiring export links are fine. IF YOU GENERATED THE MEDIA YOURSELF (rendered carousel slides, a video) and it's too large to inline as base64Images: call createmediaupload with the file list to get presigned upload URLs, HTTP PUT each file's bytes to its uploadUrl (with the matching Content-Type header), then call finalizemediaupload to get a single mediaId. Pass that mediaId to schedulepostdraft / publishscheduled. An image batch becomes one carousel in upload order. This media is durable (hosted on Socialync's bucket), so you can schedule it for any future publish date. If the PUT can't connect (a sandbox network block, a proxy 403, "host not allowed", a DNS failure), do not retry it and do not call finalizemediaupload. Tell the user plainly that their AI app can't reach Socialync's upload server, then offer the two ways forward: (1) they add the file in Socialync (socialync.io: start a post and add the file, no need to finish it), come back, and you find it with listmedia; or (2) they allow the upload host in their AI app's code or network settings and you try again. Images up to 8MB each can also go inline as base64Images instead.
  3. PLATFORMS. Scheduled posts (schedulepostdraft / publishscheduled): ALL EIGHT: Facebook, Instagram, TikTok, YouTube, LinkedIn, X, Threads, Bluesky. YouTube accepts VIDEO posts only (mediaId or videoUrl) and requires the title parameter. TikTok accepts ONE video, or a photo post of up to 10 images (imageUrls, base64Images, or an image mediaId; it posts as a swipeable TikTok photo carousel and TikTok adds recommended music), never text alone. TikTok also requires the user's own choice of who can view the post (tiktokPrivacyLevel: Everyone, Friends, Followers or Only me): ask for it when you confirm the post (one answer can cover a whole batch the user asks for together), never pick it yourself. Immediate posts (createpostdraft / publishnow): Facebook, Instagram, LinkedIn, X, Threads, Bluesky (no TikTok/YouTube: those post through the scheduled tools only). Instagram REQUIRES media: image(s) or a video (video publishes as a Reel). The others accept text-only too. Per-platform image caps (enforced by the platforms themselves): X 4, Bluesky 4, LinkedIn 9, Instagram/Facebook/Threads 10. Per-platform video limits are also enforced by the platforms at publish time (e.g. Bluesky up to 10min/300MB, X free tier ~2:20, IG Reels up to 15min), warn the user if their video obviously exceeds a target platform's limit. MEDIA EXPIRY WARNING: listmedia items marked "recentupload" (not yet attached to any post) are cleaned up ~12 hours after upload. Schedule them promptly; once scheduled, the media is protected until it publishes. FIRST COMMENT: every drafting/publishing tool accepts an optional firstComment -- Socialync posts it as a comment under the post right after it publishes. It is the standard home for hashtags and links, keeping the caption clean; offer to move hashtag blocks there when a caption is hashtag-heavy. Supported: instagram, threads, twitter, youtube, linkedin, bluesky (Facebook and TikTok skip it; the post is unaffected). One string for all selected platforms, so the tightest selected platform's comment limit applies. A failed comment never fails the post -- results report it separately.
  4. AFTER PUBLISHING (publishnow / publishscheduled / approvedraft), report the per-platform results to the user, postId, postUrl, success/failure for each platform. If you used the DRAFT pattern (createpostdraft / schedulepostdraft), the post is NOT out yet: show the user the exact post, ask for their yes, and on the yes call approvedraft(draftId), then report those results. If they say no, call nothing further and tell them the draft expires on its own. Never end a turn by sending the user to the Socialync app to approve a draft.
  5. DAILY DRAFT LIMIT: You can create at most 10 drafts per UTC day for any given publish day, per profile. This applies to both immediate-publish drafts (counts toward today's bucket) AND scheduled drafts (counts toward the UTC date you scheduled them for). Each future day gets its own independent 10-draft bucket. A scheduled post that is cancelled (deletescheduledpost, or deleted in the Socialync app) before it publishes, or moved to another day, gives its slot back; drafts the user rejected or let expire still count. When the cap is hit, EXPLAIN IT TO THE USER LIKE THIS: "We're capped at 10 posts per day through AI assistants. This is a platform security mechanism, posting more than this through automation triggers spam/AI-abuse detection on Meta, X, LinkedIn, and the other networks, which can flag or suspend your account. The cap keeps you safely under those thresholds. You can schedule more posts for a different day, or open the Socialync app to post the rest manually." The success response includes dailyDraftsRemaining so you know how many slots are left in the day you just used.
  6. THE LIMITS BELOW ARE THE PLATFORMS' OWN RATE LIMITS, separate from the 10-per-day MCP cap above. If a user hits one of these AFTER your draft is approved and published, the platform itself rejects further posts, it is not a Socialync restriction. When you tell the user about a platform limit, say "X limits this to..." not "Socialync limits this to..."
    • X: ~10 posts/day before spam flagging
    • LinkedIn: ~5 posts/day (strictest)
    • Facebook / Threads / Bluesky: ~10-30 posts/day

CHARACTER LIMITS: validatepost enforces each platform's limit. For X, use maxCaptionLength from listconnections (4000 with X Premium, otherwise 280).

X ARTICLES: for long-form X content use createxarticledraft / publishxarticlenow, never a long caption. X only, needs X Premium, cannot be scheduled; LinkedIn has no article API, so offer a 3000-character post there.

WORKFLOW:

  • ALWAYS call list_connections before posting to verify the user has connected the target platform
  • ALWAYS call check_quota before posting to confirm posting is allowed
  • ALWAYS call validatepost -- with the exact same arguments you will pass to the posting tool -- BEFORE every createpostdraft / schedulepostdraft / publishnow / publishscheduled call, and again after any edit. Errors it reports are guaranteed publish failures (wrong media type or count, over-limit video, disconnected or broken account): fix them or drop that platform. Warnings mean the post publishes but degraded (truncated caption, blur-fitted image, heuristic link count): tell the user before publishing. Never call a posting tool on content that has not passed validatepost.
  • SAVED AUDIENCES: if the user wants to post to a saved audience (a named group of their accounts, e.g. "post this to Core 12"), call list_audiences and pass its id as audienceId to the posting tools INSTEAD of platforms (never both). Use exceptPlatforms to leave platforms out for one post. Members the audience cannot reach on the chosen profile come back in skippedMembers -- report them to the user.
  • When the user references media they uploaded ("the video I just uploaded", "that clip"), call list_media and match by fileName/recency. Confirm which item before scheduling.
  • DEFAULT (recommended): show the user the post → get explicit confirmation in chat → call publishnow or publishscheduled. This is the AI-native flow and most users prefer it. If the user switched the publish confirmation dialog on in Socialync settings and the client supports it, Socialync then shows its own dialog; a decline comes back as success false with consent "declined" and stops the post.
  • DRAFT FLOW (two steps, both in chat): createpostdraft or schedulepostdraft → show the user the post → user says yes in chat → approvedraft(draftId). Use getdraft_status if you lose track of a draft's state. The user never has to open the Socialync app to finish a post you started.
  • To change a scheduled post (time, caption, YouTube title, first comment, or dropping a platform), call updatescheduledpost; do not delete and recreate it. To cancel one, call deletescheduledpost. Swapping media or adding a platform still means cancel and schedule again. Already-published posts cannot be changed or cancelled.

When the user asks you to draft or publish content, adapt the caption for each platform's tone and limits automatically. Be concise. For the direct-publish flow, ALWAYS show the user what you will post and confirm before calling publishnow / publishscheduled. For the draft flow, ask for the yes and call approve_draft; never send the user to the app to approve.

Before you connect it

What can Claude do in Socialync?

28 named actions: 14 that only read, 7 that write and 7 that delete or permanently alter something. They include list_profiles, list_connections and list_audiences. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Socialync connector need?

Nothing to paste. You sign in to Socialync over OAuth 2.0 and Toolspoke keeps the resulting token encrypted, refreshing it when it expires. It asks for mcp:*, and can do nothing outside them.

Does the Socialync connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 28 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Socialync connector not do?

The 28 actions above are the whole of it. A call to any other name is refused before it reaches Socialync rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Socialync of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Socialync. An agent has to ask. Toolspoke does not retry, queue or back off around Socialync's own rate limits. A call that Socialync refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Socialync's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Socialync?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

Connect Claude to Socialync

Add Socialync to a project and point your client at the gateway.