A MCP server for agencies is one hosted endpoint that an AI app connects to once, then switches between client workspaces. In Creator OS, each workspace holds one client’s set of socials (11 platforms plus Skool), and each workspace gets its own scoped API key, so an agent working for client A can never publish to client B.
One login (you)
|
+-- Agency 10 plan
|
+-- Workspace: Client A ----> cos_live_A (scoped key)
| Instagram, LinkedIn, YouTube, Threads, Facebook
|
+-- Workspace: Client B ----> cos_live_B (scoped key)
| Instagram, LinkedIn, TikTok, X
|
+-- Workspace: Client C ----> cos_live_C (read only)
Facebook, YouTube, Threads
AI app (Claude, ChatGPT, Cursor, Codex)
connects to https://mcp.creatoros.ca/mcp
one connection per client workspaceWhat is an MCP server for agencies and why do clients need separate setups?
An MCP server for agencies is a hosted connection point that lets an AI app read and write on your client accounts through tools, and it only works cleanly if each client sits in its own workspace with its own key.
Clients need separation for three reasons that show up in real agency work:
- Blast radius. If an agent holds one key for everything, a wrong platform name or a mixed up post id reaches the wrong brand. A workspace key stops that at the API boundary.
- Handover. When a client leaves, you revoke one key and one workspace. Nothing else moves.
- Permissions. Some clients want you to post. Others only want reporting. Read-only keys cover the second case, and the API refuses writes from them.
Creator OS runs this from one login. Agency 10 gives you 10 client workspaces, each with 11 platforms plus Skool, for $99/month or $599/year (about $50/month). Agency 5 covers 5 workspaces at $49.99/month or $399/year (about $33/month). Both include unlimited posts, comments and messages, unlimited team members, and a scoped API key per client workspace.
How does one login run 8 client networks without mixing accounts?
You keep one Creator OS account and treat each client as a workspace, then connect that workspace to your AI app as its own MCP connection.
In Claude, the flow is: Settings > Connectors > Add custom connector, paste https://mcp.creatoros.ca/mcp, sign in to Creator OS, then pick the workspace. On agency plans you pick one client per connection. Each connection gets its own key, listed under Settings > Connected apps, so you can see eight client connections side by side and revoke any one of them.
A worked example, eight clients, Monday morning:
- Open the Claude project for Client A. The connector for Client A’s workspace is already named in the project.
- Ask: “Pull last week’s post analytics, flag any post where the Instagram Reels skip rate is above 60%, and draft three new hooks.”
- Move to the Client B project. Same question, different workspace key, different accounts.
Nothing about that workflow requires you to log out. The switching happens at the connection level, not at the human level. For the wider agency picture, see 8 client networks, one login and social media management for agencies.
What are scoped API keys and how do they protect each client?
A scoped API key is a creatoros key starting with cos_live_ that is pinned to exactly one workspace, so the holder can only act on that client’s accounts.
That pinning is the whole safety story. If an agent holding Client A’s key tries to publish to an account that belongs to Client B, the API has no account to resolve and the call fails. You can also create read-only keys in Settings > API keys, which is the right default for a reporting-only agent or a contractor who just needs numbers.
Three habits that keep keys tidy:
- One key per client per tool. Do not reuse a single key across Claude, Cursor and a script.
- Read-only first. Give write access only after a client approves the posting workflow.
- Revoke on offboarding the same day. The key list under Connected apps is your audit trail.
For the deeper version of this argument, read MCP server API key safety for social media and the security update notes. Authentication details live at the authentication docs.
Can one MCP server handle LinkedIn, Instagram, Threads, Facebook and YouTube per client?
Yes, when each client has its own workspace, the same hosted MCP endpoint covers LinkedIn, Instagram, Threads, Facebook, YouTube and the rest of the 11 platforms plus Skool, scoped per workspace.
The MCP server exposes about 160 tools. The names you will use most for a client with mixed networks are create_post, upload_media_from_url, get_post_analytics, get_best_time_to_post, list_comments, reply_to_comment and send_message.
One practical detail worth knowing before you promise a client anything: a post can name several platforms, and any network that is not connected in that workspace comes back in missing_platforms while the rest still go out. That means a half-configured client workspace fails loudly but partially, not silently. Check accounts:health before a launch week.
creatoros accounts:health
creatoros posts:create --text "New drop Friday" \
--platforms instagram,linkedin,threads,facebook,youtube \
--media https://cdn.example.com/hero.jpg
Per-platform rules are applied for you: Reels and Shorts handling, TikTok consent flags, YouTube visibility and thumbnails on long form only. The full option map is at post options.
LinkedIn MCP server and LinkedIn ads MCP server for agencies: what is scoped to each client?
LinkedIn posting and LinkedIn ads run through the same client workspace, so the workspace key scopes both the organic page and the ad account work.
On the organic side, a LinkedIn post in Creator OS supports text, images, video, polls, reposts, a first comment, disabling the link preview, and company pages through organizationUrn. Page posts can carry audience targeting once the page has 300 or more members. Comment replies are supported. LinkedIn DMs are not.
On the ads side, the Ads add-on ($19.99/month on any plan, no percentage of ad spend) covers LinkedIn sponsored posts from a Company Page, image or video, with objectives for traffic, lead generation, engagement, awareness, video views and job applicants. The minimum is 10 per day. LinkedIn reviews every ad, and there is no native dry run on that network, so build the pause-and-review step into your client’s approval flow.
What that looks like scoped per client:
| Layer | Scoped by | Effect for the client |
|---|---|---|
| Company page posts | Client workspace key | Only that client’s page can be posted to |
| LinkedIn ads | Same workspace, ad account | Budgets come from that client’s ad account |
| Read-only key | Workspace setting | Reporting agent cannot post or spend |
The linkedin-campaign-builder skill walks an agent through campaign structure inside the client workspace. Skills arrive as MCP prompts too, so they show in the AI app’s prompt menu. Ads setup details are at the ads docs.
How to set up per-client MCP workspaces in Creator OS step by step
Setting up per-client MCP workspaces takes about ten minutes per client: create the workspace, connect the networks, then add one MCP connection for that workspace in each AI app you use.
- Sign up and pick a plan. Agency 10 if you run 8 clients today and want headroom. Start here.
- Create one workspace per client and connect that client’s platforms. Use
creatoros accounts:connect <platform>per network, then confirm withcreatoros accounts:health. - Generate a key per workspace in Settings > API keys. Read-only unless the client approved posting.
- Add the MCP connection at
https://mcp.creatoros.ca/mcp, one per client workspace, in Claude or ChatGPT (developer mode) or your editor. - For Claude Code, use the header form:
claude mcp add --transport http creatoros-clientA \
https://mcp.creatoros.ca/mcp \
--header "Authorization: Bearer cos_live_..."
Cursor, Windsurf and VS Code use the same idea with an mcpServers entry: type http, the URL, and the Authorization header. Name each entry after the client so the tool list is self-explanatory.
Two extras that save time once you are past client three:
- Destructive tools ask first. Deletes for posts, comments, automations, webhooks, Skool posts and ads are marked so the AI app confirms before acting.
- The Claude Code plugin adds a publish guard. Install with
/plugin marketplace add kevinbadi/creatoros-claude-plugin, then/plugin install creatoros@creatorosand/plugin configure creatoros@creatoros. It asks Proceed or Cancel before anything is published, spent or deleted. It also adds/cos-statsand/cos-health.
Full connector instructions are at the MCP docs. If you want to watch it happen, the walkthroughs are on the KevBuildsApps YouTube channel.
MCP server vs one API for agency client work: which scales better?
For agency client work a hosted MCP server scales better than hand-rolling one REST integration per client, because the connection, the permissions and the workspace boundary are configuration rather than code.
Compare the two paths honestly:
| Job | Hosted MCP server | Direct REST integration |
|---|---|---|
| Connect a new client | New workspace, new connector, new key | New code path and new secrets per client |
| Agent tooling | About 160 named tools in the AI app | You write and maintain every call |
| Guardrails | Workspace-pinned keys, read-only option | Whatever you build |
| Who it suits | Strategists using Claude, ChatGPT, Cursor | Backend engineers with a fixed pipeline |
The REST API is not a lesser option. It is the same workspace and key model, with typed ids (acc_, post_, cmt_, conv_) and one error shape, { error: { code, message, status } }. When your team wants scripted reports, use it. When a strategist wants to ask a question in plain English and get a draft, use MCP. The tradeoffs are covered in MCP server vs REST API.
For agencies running eight client accounts, the deciding factor is usually not speed of the first integration. It is how cheap client nine is to add. On MCP it is a connector and a key.
FAQ
What is an MCP server for agencies?
It is a hosted endpoint, https://mcp.creatoros.ca/mcp in Creator OS, that an AI app connects to once so an agent can publish, reply and read analytics through named tools. For an agency, each client workspace is connected separately so the agent acts only inside that client’s accounts.
Can one MCP server manage multiple client social accounts?
Yes. One URL serves every client. What varies is the connection: on agency plans you pick one client workspace per connection, and each connection carries its own key. Your login stays the same while the workspace changes.
How do scoped API keys keep client accounts separate?
A cos_live_ key is pinned to a single workspace, so an agent holding Client A’s key has no path to Client B’s accounts. Read-only keys can be created in Settings > API keys, and the API refuses writes from them.
Does Creator OS support a LinkedIn MCP server and Facebook MCP per client?
Yes. LinkedIn and Facebook are part of the same 11 platforms plus Skool inside each client workspace, so the LinkedIn posting, Facebook page posts and Messenger work all sit behind that client’s key. Comment replies, hiding, DMs and comment-to-DM funnels work where each network supports them.
Is an MCP server safe for agency client accounts?
It is as safe as your key and workspace discipline. Creator OS gives you a key per client, a read-only option, and a list of connected apps you can revoke from. Destructive actions are marked so the AI app asks before deleting anything, and the Claude Code plugin adds a publish guard that asks Proceed or Cancel.
Get started with Creator OS: 8 client networks, one login
Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Agency plans add the workspaces and scoped keys an agency needs: Agency 5 at $49.99/month or $399/year, Agency 10 at $99/month or $599/year. New subscribers start for $0 with a free trial and can cancel anytime.
Create your account, add one client workspace, connect it at https://mcp.creatoros.ca/mcp, and test a single post before you load the other seven. When you want the agent itself, the open-source Social Agents harness runs your socials on Creator OS, and the build is shown in the launch video. More agent recipes are at the AI agent for agencies guide.
Get started for $0
Free trial for new subscribers. Cancel anytime.