A hosted MCP server gateway gives your AI agent one URL that reaches every tool behind it. Creator OS runs a hosted MCP server at https://mcp.creatoros.ca/mcp with about 160 tools for posts, analytics, comments, DMs, automations, the blog, Skool, Shopify and ads. You paste one URL into Claude, Cursor or ChatGPT and sign in once.
Claude Cursor ChatGPT Claude Code
| | | |
+-------------+------+------+--------------+
|
https://mcp.creatoros.ca/mcp
|
(one sign in, one workspace key)
|
+---------+----------+----------+-----------+
| | | | |
posts analytics comments DMs ads
IG/TT/ per post, reply, one inbox, Meta,
YT/X/ daily, hide, send, Google,
LI/... best time like search TikTokWhat is an MCP server gateway and why teams need one
A gateway is the single endpoint you register in your AI app. Without one, you add a server per job, and every server needs its own install, its own credentials and its own update.
The sprawl is real for a social team. One person wants the agent to post. Another wants replies to comments. A third wants numbers. A fourth wants to boost a post as an ad. Each of those turns into a separate connection if every capability lives on its own server.
Creator OS answers that with a hosted MCP server and a CLI so an agent can run your accounts. There is nothing to install for the MCP path. The account layer does the rest: one sign in, one workspace, one key, and the tools underneath share the accounts you have already connected.
The setup is deliberately small. In Claude you go to Settings, then Connectors, then Add custom connector, paste the URL, sign in to Creator OS and pick the workspace. In ChatGPT you add the same URL as a connector in developer mode. Both are one time jobs per app.
MCP gateway registry vs one URL: how routing works across Claude, Cursor and ChatGPT
A registry stores server definitions so many people can discover them. A single gateway URL puts the routing inside the server, so the client never has to know what sits behind it.
Those are two different jobs. A registry is a catalogue and a distribution problem. A gateway is a runtime and a permissions problem. Small teams mostly feel the second one.
Here is what actually happens when you point a client at the Creator OS gateway.
| Layer | What it is | Who manages it |
|---|---|---|
| Client | Claude, ChatGPT, Claude Code, Cursor, Windsurf or VS Code | You, once |
| URL | https://mcp.creatoros.ca/mcp | Creator OS |
| Credential | A connection key listed under Settings > Connected apps | You, per connection |
| Workspace | One set of socials per connection (agency plans: one client per connection) | You |
| Mode | Read only or read and write | You, per connection |
| Tools | About 160, exposed through the one URL | Creator OS |
Two details matter for a team. Read-only connections only see read tools, and the API refuses writes from them, so you can hand an analyst’s agent a safe view of the account. Destructive tools such as delete post or delete ad are marked so the AI app asks first.
For Cursor, Windsurf and VS Code the shape is an mcpServers entry with type http, the URL and an Authorization header. Claude Code takes one command:
claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp --header "Authorization: Bearer cos_live_..."
That is the whole multi client story. One URL, copied into whichever app the person already uses.
How to connect your tools with one URL: Instagram, Threads, YouTube, Facebook and LinkedIn
The gateway is only as useful as the accounts behind it, and those are connected in Creator OS first, not in the AI app.
The quickest path is the CLI, which is included in every plan:
npx @creatoros/cli@latest init
creatoros auth:check
creatoros accounts:connect instagram
creatoros accounts:connect threads
creatoros accounts:list
Run creatoros accounts:list to check what is connected. It tells you which platforms are live before an agent ever touches them.
Here is a worked example. You want one announcement on Instagram, Threads, YouTube and LinkedIn, with a first comment on the networks that allow it, and you want it scheduled for the morning.
creatoros posts:create \
--text "New tutorial is live. Link in the first comment." \
--platforms instagram,threads,youtube,linkedin \
--media https://cdn.example.com/thumb.jpg \
--scheduledAt 2026-03-04T09:00:00Z --timezone America/Toronto
Creator OS applies each platform’s own rules. Threads caps posts at 500 characters and 250 posts per 24 hours. YouTube takes a title up to 100 characters and a visibility setting. Instagram takes a first comment for links because captions have no clickable links. LinkedIn takes a first comment too.
If a platform in the list is not connected, it comes back in missing_platforms and the rest still go out. That one behaviour removes most of the pain of a multi network post.
Instagram MCP server URL and LinkedIn MCP server URL for Claude: setup walkthrough
There is no separate Instagram MCP server URL and no separate LinkedIn MCP server URL to collect. Both sit behind the same gateway, and the tool you call decides which network is touched.
So the walkthrough is short. Open your AI app’s connector settings, paste https://mcp.creatoros.ca/mcp, sign in, choose the workspace, pick read and write. Then ask a question that maps to a tool.
A realistic prompt, after Instagram and LinkedIn are connected:
Upload the cover at https://cdn.example.com/cover.jpg, then draft an
Instagram Reel and a LinkedIn post for the launch. Use
check_caption_length on both before you save them. Do not publish.
That path touches upload_media_from_url to get a reusable media id, check_caption_length to catch a caption that will fail, and create_post with draft set. Nothing goes out until a human says so.
Instagram specifics an agent can honor: a custom cover (instagramThumbnail) or a cover frame (thumbOffset), up to 3 collaborators, user tags, location, an AI generated label, and commentsEnabled false to turn comments off after publishing. Trial Reels are available on accounts with 1,000 or more followers; below that Creator OS refuses the post up front with trial_reel_needs_followers and suggests a regular Reel instead.
LinkedIn specifics: text, images, video, polls, reposts, first comment, disableLinkPreview, and company pages via organizationUrn. Document posts are not supported through the API, so plan a different format if that was the idea.
MCP server for Instagram vs LinkedIn ads MCP server: what each gateway tool actually does
Posting tools and ad tools behave differently on purpose, and knowing the difference keeps an agent from spending money by surprise.
On the posting side the tools are content operations. create_post, update_post, list_posts, get_post, get_post_analytics, get_best_time_to_post, list_comments, reply_to_comment, send_message, create_automation, links_create, blog_create_article, skool_create_post. Most of them change state you can see and undo.
On the ads side the tools are money. Ads is an add-on at $19.99/month on any plan, and ad spend is billed by each network to your own ad account. Spend is separate from the subscription.
ads_create_adbuilds an ad. Every create can be dry-run with validate_only, budgets are confirmed, and ads are created paused for review.ads_boost_postputs spend behind something you already published, on Meta, Google, TikTok Spark Ads or X.ads_best_postslooks at what performed before you pick a boost candidate.
A useful habit for an agent workflow: make the agent call ads_best_posts and propose three candidates, then have it call ads_boost_post with validate_only so you see the budget and audience before anything is live. Budgets are whole units of the ad account currency. Meta allows about 30 creates per ad account per 5 minutes, and Google allows about 15 live calls a minute, so a looping agent should pace itself.
The campaign builder skills, meta-campaign-builder, google-campaign-builder, tiktok-campaign-builder and linkedin-campaign-builder, come in as MCP prompts, so they appear in the AI app’s prompt or slash menu next to the tools.
Can one API replace five MCP servers in your content stack
For Creator OS, the gateway and the REST API sit in front of the same workspace, so the answer is about how you want to work, not about coverage.
The MCP path is for an AI app doing the work. The API path is for your own code, a scheduler, or a script. Both are authenticated with a Creator OS API key (cos_live_…), and a key is pinned to one workspace, so an agent holding one workspace’s key cannot post to another. That is the property that makes one URL safe to hand to five people.
A worked split:
- Your designer works in Claude with a read and write connection and drafts posts.
- Your analyst uses a read only connection for
get_daily_metricsandget_follower_stats. - Your developer uses the CLI for bulk calendar uploads with
creatoros posts:bulk-upload --file calendar.json --dryRunbefore the real run. - Your automation posts webhook events to your own endpoint: post.published, post.failed, comment.received, signed with X-CreatorOS-Signature.
One stack, three doors, one set of accounts. If you build in Claude Code, the plugin adds a publish guard that asks Proceed or Cancel before anything is published, spent or deleted. Install it with /plugin marketplace add kevinbadi/creatoros-claude-plugin, then /plugin install creatoros@creatoros and /plugin configure creatoros@creatoros. It needs Claude Code 2.1.287 or later.
FAQ
What is an MCP server URL and where do I find it?
An MCP server URL is the HTTPS endpoint your AI app connects to so it can list and call tools. For Creator OS it is https://mcp.creatoros.ca/mcp, and you paste it into your app’s connector settings rather than searching for it. Each connection gets its own key, listed under Settings > Connected apps.
How do I add a LinkedIn MCP server URL for Claude?
You do not need a LinkedIn specific URL: add the Creator OS gateway once and connect your LinkedIn account in Creator OS first. In Claude, open Settings > Connectors > Add custom connector, paste the URL, sign in and pick the workspace. LinkedIn then appears as one of the networks create_post can target.
Is there an official Instagram MCP server or Threads MCP server?
There is no separate Instagram or Threads endpoint in Creator OS; both are reached through the same hosted MCP server and its posting tools. Connect the accounts, then ask the agent to post with platforms set to instagram or threads. Platform rules such as the 500 character Threads limit are applied for you.
What is an MCP gateway registry and do I need one?
A registry is a catalogue of available servers that a client can browse or install from. If you already know the one URL your team uses, you do not need a registry to get work done. What you do need is a connection key per person or per client workspace, and the read only or read and write choice that goes with it.
Can one gateway handle posting, scheduling, analytics and LinkedIn ads MCP tools?
Yes. The Creator OS MCP server carries about 160 tools covering posts, analytics, comments, DMs, automations, webhooks, Skool, Shopify, the blog and the Ads add-on. Scheduling is part of create_post through the schedule fields. Ads tools need the $19.99/month add-on and an ad account you control.
Get started with Creator OS: one gateway URL for your whole stack
The point of the gateway is that the plumbing disappears and the work stays. One URL, one sign in, one workspace, and about 160 tools your agent can call in whichever app your team already likes.
Start at https://www.creatoros.ca/sign-up. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. The trial is free to start and you can cancel anytime.
Read the setup details at https://www.creatoros.ca/docs/mcp and the full API reference at https://www.creatoros.ca/docs. For posting patterns across networks, the walkthrough on publishing to two networks at once pairs well with this one, and agencies can follow the per client workspace setup. Ad workflows are covered in the ecommerce guide.
If you prefer to watch before you wire anything up, the walkthroughs are on the KevBuildsApps YouTube channel, and the launch video shows the server and the plugin in motion.
Get started for $0
Free trial for new subscribers. Cancel anytime.