Post across channels
Tell your Bot what to post and where. It drafts a version for each network, schedules it in ContentStudio, and checks with you before anything goes live.
Connect ContentStudio to Grok Bot, xAI's always-on AI teammate. Ask your Bot to connect the ContentStudio MCP server, or install the ContentStudio CLI on its cloud computer. Then it drafts, schedules, and reports on your posts, even while you're offline.

https://mcp.contentstudio.io/mcp npm install -g contentstudio-clinpx skills add contentstudioio/contentstudio-agentcontentstudio auth:login --api-key <key>Publishes to:
Quick Reference
Core Capabilities
Your Bot can list your connected accounts, create and schedule posts with media, pull analytics, and work the inbox, all through ContentStudio and from its own cloud computer.
Tell your Bot what to post and where. It drafts a version for each network, schedules it in ContentStudio, and checks with you before anything goes live.
Create images and videos for your posts from a prompt, or edit images with the CLI tools.
Ask how last week went, and your Bot pulls performance data or generates a full report.
Save any posting task as a routine. Your Bot runs it on a schedule from its cloud computer while you are offline.
Read comments, messages, and reviews, and draft replies for you to approve.
Review pending posts, approve or reject them, and leave feedback for your team.
Upload files from the cloud computer to your ContentStudio media library and attach them to posts.
Add comments or internal notes to any post, and mention teammates.
Move between client workspaces, so each Bot posts to the right brand.
Setup
Three quick steps are all it takes to connect Grok Bot with ContentStudio and start scheduling your social media from chat.
Ask your Bot to install the CLI on its cloud computer. This is what Grok Bot uses to talk to the ContentStudio public API.
npm install -g contentstudio-cliAsk your Bot to install the skill so it knows every ContentStudio command without extra prompting.
npx skills add contentstudioio/contentstudio-agentGenerate an API key from Dashboard → Settings → API Keys, then give it to your Bot to authenticate the ContentStudio CLI.
contentstudio auth:login --api-key <key>Prefer the fastest setup with no key to manage? Ask your Bot to connect the ContentStudio MCP server instead.
MCP (Model Context Protocol) is the open standard Grok Bot uses to call outside tools. Give your Bot the ContentStudio MCP link, then sign in to ContentStudio when it hands you the browser.
https://mcp.contentstudio.io/mcpUsing the integration
A few things you can say to your Bot. It handles the ContentStudio calls behind the scenes.
> Which social accounts do I have connected in ContentStudio?
✓ Your Bot lists every connected account in the active workspace.
> Post this to X and LinkedIn tomorrow at 9 AM with the cover image, then ask me to approve.
✓ Both posts are prepared, shown to you, and scheduled once you approve.
> What's scheduled for this week? Move tomorrow's LinkedIn post to Friday and keep the rest.
✓ The week laid out, and the one change made.
> How did my X account do last month, and how is yesterday's launch post performing?
✓ Performance pulled from ContentStudio, with the strongest posts called out.
> Every weekday at 8 AM, turn new files in ~/content/drafts into ContentStudio drafts and send me a summary.
✓ A routine that saves drafts every weekday and reports back in your chat.
> Check unanswered Instagram comments and draft replies for my review.
✓ Replies drafted in ContentStudio, sent only after you approve.
Security & Trust
Your Bot checks with you before it publishes, and ContentStudio keeps your social account passwords out of reach.
OAuth 2.1 sign-in: The MCP server signs in with your ContentStudio account. No API key is stored, and your social media passwords stay inside ContentStudio.
Approvals before publishing: Your Bot asks before it changes anything outside its computer. ContentStudio approval workflows still apply on top.
One computer, shared sign-ins: All your Bots share one cloud computer and its sign-ins, so any Bot can use ContentStudio once it is connected. Keep routines on drafts if that matters.
Scoped API key: The CLI uses a single cs_ key that talks only to the ContentStudio public API. Revoke or replace it anytime.
Platforms
Every network connected in ContentStudio, with the post types and options each one needs.
| Platform | Post types |
|---|---|
| Feed, Reel, Story, carousel, video, poll | |
| Feed, carousel, Reel, Story | |
| X (Twitter) | Feed and threads |
| Feed, document carousel, video, poll | |
| TikTok | Video and photo posts |
| Image, video, carousel pins | |
| YouTube | Videos and Shorts |
| Threads | Posts and multi-post threads |
| Bluesky | Feed posts |
| Telegram | Channel posts |
| Tumblr | Feed posts |
| Google Business Profile | Updates, events, offers, CTAs |
Grok Bot or Grok
No. Grok is the chat assistant on X and grok.com. Grok Bot is the always-on AI teammate from xAI, with its own cloud computer. Both can work with ContentStudio, in different ways. Using Grok chat instead? See the ContentStudio MCP server page for the setup.
| Grok Bot (always-on teammate) | Grok (chat assistant) | |
|---|---|---|
| What it's for | Named Bots that work around the clock on their own cloud computer. | xAI's chat assistant on X and grok.com. |
| You say | “Every weekday at 8 AM, turn new drafts into ContentStudio posts and send me a summary.” | “Draft a LinkedIn post about our new feature.” |
| Connects | MCP from chat, or the CLI on its cloud computer | A connector with the MCP link and your key in the URL |
| Runs | 24/7, on routines | In a chat window, while you type |
| Best for | Recurring social media work | One-off posts and questions |
Troubleshooting
Most issues come down to the MCP connection, the API key, or the wrong workspace.
Ask your Bot to connect the ContentStudio MCP server again and sign in when it hands you the browser.
The CLI isn't installed on the cloud computer yet. Ask your Bot to run npm install -g contentstudio-cli.
Ask your Bot to run contentstudio auth:status, then contentstudio auth:login --api-key cs_... with a key from Settings → API Keys.
The key is missing or revoked. Generate a fresh one in the dashboard and have your Bot log in again.
The post, account, or file belongs to a different workspace. Ask your Bot which workspace is active, or name the one to use.
The CLI retries automatically, but AI image and video generation never auto-retry, because they are billable. Space out bulk routines.
One account, one set of tools. Pick the agent you already work in, or browse all of them below.
Building something custom? Browse every ContentStudio integration.
Connect the MCP server or the CLI, and let your Bots draft, schedule, and report on posts across every network, even while you’re offline.
7-day free trial · No credit card · Cancel anytime
