Checked before it is queued
Over MCP, each post is checked against the platform's rules. One that breaks them, or misses something like a Pinterest board, is refused with the reason.
Connect Claude, ChatGPT, Dots, Muse, Grok, OpenClaw, Hermes or any agent that speaks MCP. It schedules and publishes posts on Instagram, TikTok, LinkedIn, X, YouTube and more, answers comments and reads analytics, all through one connection.
Remote MCP server · OAuth for Claude, ChatGPT and Cursor · CLI · REST API
Plus any agent or app that can call an MCP server, run a CLI or send an HTTP request. See every way to connect
We host the MCP server, so there is nothing for you to run. Connect your accounts and your agent, then ask for posts in plain words.
Sign in to each network from your dashboard. The access tokens stay with us and never reach your agent.
Add our MCP server and its 200+ tools to your agent. Claude, ChatGPT, and Cursor sign in with OAuth, and any other MCP client can use a full-access API key.
https://api.so-me.studio/mcpTell your agent what to post, where and when. It schedules the posts through our tools, which first check each post's media and required fields against the network's rules.
Connect over MCP, run the CLI, call the REST API or listen for webhooks. Each one reaches the same workspace, accounts and schedule.
Install the so-me-studio skill and OpenClaw drives the so-me CLI for you.
Add our server to the MCP config of Hermes Agent. There is nothing else to install.
A community node for self-hosted n8n. Publish from any workflow, or start one when a post goes live.
Call the REST API from an HTTP step and catch our signed webhooks. There is no separate app to install.
200+ MCP tools cover publishing, media, comments, analytics and more.
Create and schedule posts, move them to new times, write threads of up to 24 parts and add a first comment on the networks that support it.
create_postschedule_postget_calendar_postsUpload images and video, check each file against every platform's media rules before posting, and get the exact fix when a file breaks one.
presign_media_uploadvalidate_post_mediaRead new comments and messages and reply in the thread. Turn on reply approval and your agent's replies wait as drafts until a teammate sends them.
Creator plan and up
list_conversationsreply_to_conversationPull a workspace overview, an account's numbers for the period you choose and the results of any single post.
Creator plan and up
get_analytics_summaryget_instagram_analyticsget_post_analyticsWrite captions, get suggested posting times for each account, or write and schedule a post in a single call.
AI captions on the Creator plan and up
generate_captionget_best_time_recommendationsgenerate_and_scheduleBuild a link-in-bio page with buttons and a post gallery, give it a theme and publish it at its own web address.
Creator plan and up
create_biolinkcreate_biolink_buttonpublish_biolinkPosts sent over MCP are checked against each platform's rules before they are queued, inbox replies can wait for a person, and you can switch off AI features or disconnect an app at any time.
Over MCP, each post is checked against the platform's rules. One that breaks them, or misses something like a Pinterest board, is refused with the reason.
Turn on Approve MCP replies and your agent's inbox replies wait as drafts until a teammate sends them. It is off by default.
Ask your agent to save drafts, and they wait in your dashboard until you edit, schedule or publish them.
Disconnect any AI app or revoke any API key in Settings. Your social account passwords and tokens never reach the agent.
An owner can switch off AI features for the workspace, and they stay off in the app, the REST API and MCP.
Your plan sets rate limits and a monthly allowance of API calls and MCP credits. Settings show logs of API requests, MCP usage and webhook deliveries.
Posts your agent creates are not held for approval. Once they pass the checks, they are scheduled or published. If you want to read posts before they go out, ask your agent to save drafts.
Connect your accounts once, and your agent works with them through our MCP server, CLI or REST API. Here is what it can do on each network.
Post now or at a set time, with images or video where the network accepts them.
Read and answer comments and messages in one inbox, yourself or through your agent.
Comments on these networks need approval from the platform, so they may not be available on every account yet.
Account stats, plus post stats where the network shares them, in the app or for your agent to read.
WhatsApp is for conversations, not posts. Messages you start go out as approved templates.
Plans differ in posts, accounts, features and agent limits. How your agent connects stays the same on every one.
Prices are per workspace. Each plan covers one workspace, and every other workspace you create needs its own plan.
For large teams & enterprises
Billed monthly
For growing teams & agencies
Billed monthly
For individual creators & freelancers
Billed monthly
Post to every platform, by hand or through the API and MCP
Billed monthly
Start with a 7-day free trial. A credit card is required, but nothing is charged until the trial ends. Your selected plan renews automatically after 7 days unless you cancel in Billing. There is no free plan.
Limits belong to the workspace, so every agent and API key you connect shares them.
Each MCP tool call uses credits: reads use the fewest, and AI generation uses more. CLI commands count as REST API calls.
It gives your agent one connection to your social media. You connect your accounts once, and your agent drafts, schedules and publishes posts through our MCP server, our CLI or our REST API. On plans that include them, it can also answer comments and messages and read your analytics. We handle the publishing on each network, so your agent decides what to post and when.
Any agent that can call an MCP server, run a command or make an HTTP request. Claude, ChatGPT and Cursor sign in with OAuth: you approve the connection in your browser and never copy a key. Other MCP clients, Hermes among them, can connect with an API key, and OpenClaw can install our skill from ClawHub and work through the CLI. Dots, Muse and Grok have no integration of their own: they connect the same way as any other agent, as long as they can use one of those three.
No. You connect each social account in Social media studio yourself, and your agent only ever talks to our tools. The tokens that let us post to a network stay on our side and are removed from everything a tool returns. You can disconnect an AI app or revoke an API key in Settings at any time, and your social accounts stay connected.
Yes, if you ask your agent to save drafts instead of scheduling. Drafts wait in your dashboard until someone schedules them. This is an instruction your agent follows, not a lock: the agent can also schedule a draft. A post your agent creates directly is not held for approval; it is scheduled or published straight away. Replies work differently: an owner can turn on approval for agent replies in Settings, and every inbox reply your agent sends over MCP then waits as a draft until a teammate sends or discards it.
There is no separate charge for agents. Every plan includes the MCP server, the CLI and the REST API, the lowest-priced plan too. Plans differ in posts, accounts, agent limits and features: your agent can use the inbox, analytics and AI captions only on plans that include them. Every plan starts with a 7-day free trial. A credit card is required, but nothing is charged until the trial ends.
Your agent can post to Instagram, Facebook, X, LinkedIn, TikTok, YouTube, Threads, Pinterest, Bluesky, Mastodon, WordPress, Dev.to, Dribbble, Discord and Slack. On LinkedIn, it can post to personal profiles and Pages. Each post goes to one network, so your agent makes one call per network and can word each post differently. WhatsApp and Telegram are inbox channels: WhatsApp sends approved message templates, and Telegram does not publish posts.
Use MCP when your agent works in a chat app or another MCP client: it finds the tools it needs by itself. Use the CLI for coding agents and scripts: install @social-media-scheduler/cli, sign in once in your browser with so-me auth:login, and commands print JSON. Use the REST API from your own code and automations: self-hosted n8n has a community node, and Zapier or Make can call the API through their HTTP steps. All three work on the same workspace and posts, and CLI commands count toward your REST API calls.
Yes. Each workspace has a per-minute rate limit and a monthly allowance set by its plan: MCP credits for tool calls over MCP, and API calls for the REST API and the CLI. Every agent and API key you connect shares the workspace's limits. An agent that posts and replies all day fits a higher plan, and you can follow its usage in Settings, in the API request log and the MCP usage log.
Yes. Your agent and your team work in the same workspace. Posts your agent creates show up in the calendar and on the Posts page, where you can edit, reschedule or delete them by hand, and replies it sends show up in the inbox. To see what the dashboard does on its own, visit so-me.studio/social-media-scheduler.
Many problems are caught before a post is queued: a post missing something a network requires, such as a Pinterest board or a WordPress title, is refused, and over MCP, attached files are checked against the network's media rules. If a network still rejects a post, it is marked as failed with the reason, and you see it in the dashboard. Your agent can read the reason, fix the problem and call retry_post. On plans with webhooks, a post.failed event also tells your own systems.
Sign in from Claude, ChatGPT or Cursor, or give any other agent an API key. From then on it drafts, schedules and publishes for you, and every post shows up in your calendar.
Every plan includes the MCP server, the CLI and the REST API. Cancel anytime.