You can set up a Claude Desktop custom connector for social media in about five minutes, and after that Claude can publish posts, answer comments, and pull analytics from your real accounts instead of drafting text you have to copy and paste. This guide walks through the exact steps, what to check when something breaks, and the prompt patterns that make the connector actually useful.
One thing to get straight before you start: the connector does not live inside Claude. It lives on Creator OS, and Claude connects out to it. That distinction explains most of the confusing parts of the setup.
Claude Desktop Creator OS
+----------------+ +------------------+
| Connectors | HTTPS | Hosted MCP |
| custom URL ---+----------->| mcp.creatoros.ca|
| | | | |
| Tool calls | | v |
| create_post --+----------->| Instagram |
| list_comments | | TikTok |
+----------------+ | YouTube, X, ... |
+------------------+
Auth: Creator OS account, read only or read & write
What a Claude Desktop Custom Connector Actually Is
A connector is a saved MCP server entry inside Claude Desktop. MCP stands for Model Context Protocol. It is the standard that lets an AI app call external tools. When you add a connector, Claude learns a list of tool names it can invoke, plus the arguments each one takes.
Creator OS runs a hosted MCP server at https://mcp.creatoros.ca/mcp. Nothing to install. You add that URL as a custom connector, sign in to Creator OS, pick a workspace, and choose read only or read & write access. Claude then has tools like create_post, upload_media_from_url, list_comments, reply_to_comment, get_daily_metrics and get_best_time_to_post available in the conversation.
The tool list is not fixed forever. Creator OS also ships skills_list and skills_get, so Claude can look up packaged playbooks at runtime instead of you explaining your whole workflow every session.
Custom Connector vs Social Media MCP Server: Which One Do You Need
People search for both phrases and often mean the same thing. The distinction is where the connection is configured.
- Custom connector in Claude Desktop. You add the URL through the app’s own settings screen. Best when you live in the desktop app all day and want one click to reconnect.
- Social media MCP server entry in a config file. You add a JSON block to a client like Cursor, Windsurf or VS Code. Best when you switch between several AI apps and want the same server defined in each.
- Claude Code command. One terminal line:
claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp --header "Authorization: Bearer cos_live_...". Best for terminal-first workflows.
All three point at the same server and give you the same tools. You are not picking a different product, just a different door into it. If you want the deeper background on how the server behaves, read what a social media MCP server does before you start adding entries.
Prerequisites Before You Start
Four things, and only the first one takes real effort.
- A Creator OS account with at least one social account connected. Sign up at creatoros.ca/sign-up if you have not yet. Instagram, TikTok, YouTube, X, LinkedIn, Facebook and Threads are all supported, plus Skool communities, a WordPress blog and paid ads as an add-on.
- Claude Desktop installed and signed in.
- Knowledge of which workspace you want Claude to touch. A workspace is one set of socials. API keys are pinned to one workspace, so an agent holding one key cannot post to another.
- A decision on access level. Read only connections only see read tools, and the API refuses writes from them. If you want Claude to publish, pick read & write.
If you are using ChatGPT instead, the same URL works as a connector in developer mode. That path is covered in setting up ChatGPT as a social media manager.
Step 1: Install Creator OS and Generate Your Connector URL
If you prefer a terminal, install the CLI and check your auth in one go:
npm i -g @creatoros/cli@latest
creatoros auth:check
creatoros profiles:list
creatoros accounts:listcreatoros auth:check confirms your key works. creatoros profiles:list shows the workspaces you can reach. creatoros accounts:list shows the social accounts inside them, each with an acc_ id you will see again later in prompts.
Now check account health before you trust anything Claude does:
creatoros accounts:healthA token that expired three weeks ago is the single most common reason a connector looks broken when it is not. Fix that first, then move on. If any account is disconnected, creatoros accounts:connect instagram (or the platform you need) starts the flow again.
The connector URL itself is always https://mcp.creatoros.ca/mcp. For a REST route instead, the base URL and full request shapes are in the docs. Do not guess at a base URL.
Step 2: Add the Custom Connector in Claude Desktop Settings
In Claude Desktop: Settings > Connectors > Add custom connector. Paste https://mcp.creatoros.ca/mcp. Claude will open a sign-in window for Creator OS. Sign in, pick the workspace you want this connection scoped to, then choose read only or read & write.
That last choice matters more than it looks. Read only connections only see read tools. Write tools are not “available but blocked,” they are simply absent, which means a read only connector is a genuinely safe thing to leave open in a chat window.
Destructive tools like delete post, delete comment, disconnect account and delete ad are marked as destructive, so the AI app asks you before running them. You stay in the loop on anything irreversible.
Once added, the connector persists. You are not re-adding it each session, though you may need to re-authorize if you revoke access or rotate your key.
Step 3: Authorize Your Social Accounts
Authorizing inside Claude is only half the story. Creator OS needs live tokens for each network, and those tokens expire on each platform’s own schedule.
creatoros accounts:health
creatoros accounts:follower-stats --granularity weeklyThe health command tells you which accounts are usable right now. The follower stats command is a quick proof that the connection is not just present but actually returning data. If follower stats come back empty for a platform you know has an audience, that account needs reconnecting.
If your plan covers several sets of socials, remember the scoping rule: a key belongs to one workspace, and an agent holding one workspace’s key cannot post to another. Agency plans cover 5 sets for $49/month or $399/year, and 10 sets for $99/month or $599/year. That scoping is a feature. You can hand a client’s key to an agent without exposing your other clients.
Step 4: Verify the Tools Claude Can Now Call
Ask Claude a question that requires a real lookup, not a guess. Something like: “List my five most recent published posts and the comment count on each.” If the connector is live, Claude calls list_posts and get_post_analytics and returns real numbers.
You can also verify from the terminal side, which is often faster than reading a tool panel:
creatoros posts:list --status published --limit 5
creatoros analytics:best-time --platform instagramIf both agree, the connector is working. Tool names you should expect to see in Claude include create_post, update_post, get_post, get_daily_metrics, get_follower_stats, list_comments, hide_comment, list_conversations, send_message, create_automation, check_caption_length, links_create, links_stats, plus the Skool, blog and ads families.
Prompt Patterns That Turn Connectors Into a Social Media Manager
A live connector and a useful assistant are two different things. These patterns close the gap.
Pattern 1: Length check before creation
Ask Claude to run check_caption_length against your draft before publishing. Each network has its own ceiling: Threads caps a post at 500 characters and allows 250 posts per 24 hours, TikTok descriptions run to 4,000 characters, and YouTube titles stop at 100. Claude will adjust the copy before it ever hits the API.
Pattern 2: One asset, several networks
Upload once with upload_media_from_url, then reuse the returned med_ id everywhere. Claude will apply each platform’s own rules for you: vertical video becomes a Short on YouTube automatically, Reels and Stories are handled on Instagram, and TikTok’s consent flags get filled by the simple post path.
Pattern 3: Reply queue triage
Have Claude call list_comments across platforms, group them by sentiment, and draft replies. You approve, then it calls reply_to_comment. Replies are supported on Instagram, Facebook, X, Threads, YouTube and LinkedIn. TikTok replies are not supported, so tell Claude to route those to hide or delete instead, which does work on TikTok for Business accounts.
Pattern 4: Comment to DM funnel
create_automation sets up a keyword funnel that DMs a link when someone comments a trigger word. Funnels run on Instagram and Facebook. Pair it with links_create so every DM carries a go.creatoros.ca short link you can measure with links_stats.
Pattern 5: Weekly report
Ask for get_daily_metrics plus get_best_time_to_post each Monday and have Claude write the summary. That is the difference between a chat window and a dashboard you actually read.
If you want these patterns prebuilt, npx @creatoros/cli@latest init installs 14 Claude Code skills including post-everywhere, respond-to-comments, analytics and ads. creatoros sync updates them later without overwriting files you edited, so your tweaks survive. More on that in Claude skills for social media marketing, and there is a walkthrough of the whole MCP path in adding Creator OS to Claude.
Troubleshooting: Connector Not Showing, Auth Errors, Missing Tools
The connector does not appear in the list
Check the URL character by character. It must be https://mcp.creatoros.ca/mcp. A trailing space or a missing path segment silently fails. Then restart Claude Desktop. The app reads connector definitions at launch.
Auth fails or loops
Run creatoros auth:check. If that fails too, the problem is on the Creator OS side, not in Claude. Re-sign-in and pick the workspace again. Remember that keys begin with cos_live_, and that a key is pinned to one workspace. If you picked the wrong workspace during sign-in, everything downstream will look empty rather than broken.
Tools are missing after connecting
Most likely a read only connection. Read only connections only see read tools, so you will find list_posts but not create_post. Reconnect with read & write if you need publishing.
Some platforms post, some do not
Post to several networks and one is not connected, and the API reports it back in missing_platforms while the rest still go out. That is deliberate. One dead account does not sink the whole post. Handle the missing one and retry that platform. If a post failed for another reason, creatoros posts:retry <postId> gives it another attempt.
Errors look the same every time
That is by design. Errors use one shape: { error: { code, message, status } }. Read the code, not the message.
For client-specific config, the MCP docs cover Cursor, Windsurf and VS Code entries. If you are building automations further out, Creator OS vs Zapier for social media explains where a connector approach diverges from a no-code workflow builder.
Two more things worth knowing. Webhooks exist for post.published, comment.received and more, signed with X-CreatorOS-Signature, so you can trigger your own systems when something ships. And if you want an agent that runs the whole loop without you driving each step, Social Agents runs your socials from Claude Code, with the code open at github.com/kevinbadi/social-agents and the launch walkthrough on the Creator OS launch video.
Get Started With Creator OS
The Creator plan is $19.99/month or $59.99/year and covers up to 8 connected accounts: 7 socials plus Skool. API keys, the MCP server, the CLI and the agent skills are included in every plan, so nothing in this guide is gated behind an upgrade.
Sign up at creatoros.ca/sign-up, connect one account, add the connector URL, and ask Claude for your last five posts. That single round trip tells you whether the whole thing is wired correctly. Then read the rest at creatoros.ca/docs, and watch the walkthroughs on the KevBuildsApps YouTube channel when you would rather see it done than read it.