What is the Socialync remote MCP server?
The Socialync remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.socialync.io/mcp, so AI assistants can connect to it without installing or running anything locally.

@Jack Vitick
Basic information
Transport
Streamable HTTP
Authentication
OAuth
Category
Communication
Author
Jack Vitick
Submitted by
Jack Vitick
Draft, schedule, and publish social media posts to 8 platforms from any AI agent: Facebook, Instagram, X, TikTok, YouTube, LinkedIn, Threads, and Bluesky. 19 tools covering drafting, scheduling, publishing, media upload, and analytics readback. Every integration runs on the official platform API, with no scraping and no browser automation. Human-in-the-loop approval is built into the workflow.
https://mcp.socialync.io/mcpclaude mcp add socialync --transport http https://mcp.socialync.io/mcpTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
This server requires authentication. Tool discovery may require signing in or credentials from the provider.
Fetch the live tool list directly from this server's endpoint using the button above.
Socialync is a cross-platform social media scheduler. This remote MCP server lets Claude, ChatGPT, Cursor, OpenClaw, or any MCP-compatible agent draft, schedule, and publish posts to eight platforms through your own OAuth-authorized accounts.
Most social media agent tooling stops at drafting. It writes a content calendar and hands you a CSV to upload somewhere else. This server completes the job: the agent drafts the post, checks the account is connected and within quota, schedules it, publishes it, and reads the analytics back.
Facebook Pages, Instagram, X, TikTok, YouTube, LinkedIn, Threads, and Bluesky.
Every integration runs on the official platform API. No browser automation, no scraping, no unofficial endpoints. That matters when an agent is posting unattended, because scraping-based tooling puts the account itself at risk.
{
"mcpServers": {
"socialync": {
"type": "http",
"url": "https://mcp.socialync.io/mcp"
}
}
}
Claude Code:
claude mcp add --transport http socialync https://mcp.socialync.io/mcp
Authentication is OAuth 2.0 with dynamic client registration. You sign in with your Socialync account in the browser. No API keys are pasted into your client, and access can be revoked from account settings at any time.
Nineteen tools across five groups.
Discovery: list_profiles, list_connections, check_quota, list_audiences
Drafting: create_post_draft, get_draft_status, approve_draft, generate_content
Publishing: schedule_post_draft, publish_now, publish_scheduled, get_scheduled_posts, delete_scheduled_post
Media: create_media_upload, finalize_media_upload, list_media
Analytics: get_analytics, get_top_posts, get_post_history
Agents that follow this order fail less.
list_profiles to pick the right brand. A user may manage several, so never assume the default.check_quota for plan, remaining posts, per-platform daily caps, and how far ahead you can schedule.list_connections to confirm the target platform is connected and healthy before drafting against it.create_post_draft, then approve_draft, then schedule_post_draft or publish_now.get_scheduled_posts to read back what you created and show the user.Publishing to a real audience is not meaningfully reversible. A deleted post has already been seen.
Never blind-retry a publish. A network timeout does not mean the post failed, because the response may have been lost after the post succeeded. Call get_post_history first and confirm the post is absent before trying again.
Read quota before a batch rather than during one. Per-platform daily caps differ and LinkedIn's is lower than the rest, so plan the whole batch against check_quota instead of stranding a half-published week.
Nothing reaches a social network until a draft is approved and explicitly published or scheduled. Agents cannot operate accounts the user has not connected and authorized.
An OpenClaw skill wrapping this server is published on ClawHub:
openclaw skills install @jackvitick/social-media-scheduler
MCP access is included on the Socialync Premium and Business plans.
The Socialync remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.socialync.io/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://mcp.socialync.io/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. Socialync uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Socialync exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Pay-per-use data and tools for AI agents: crypto token safety and rug checks, web search with cited answers, page-to-Markdown, up-to-date library docs, package safety, company research and UK/EU open data. 160 tools, 20
Football club Power Ratings for AI assistants: weekly 442ball ratings, league strength, the 442 League Index, unbeaten and winning runs, and the greatest sides in a league's history. Every answer links to its 442ball.com
Marketing campaign and audience insights from Adobe
Manage your Adobe Experience Manager content
Check one exact Gold Coast or Brisbane City property address. Free address/coverage check and short summary; paid structured Agent JSON adds available building, street and surrounding context, with Brisbane routed journe
Comments