Plan months of content
Tell Claude Code what you want to post, where, and when. It drafts and schedules a month of content across multiple platforms, including images, carousels, and videos.
Connect ContentStudio to Claude Code with one terminal command. Draft, preview, schedule, and publish across all major social networks from your terminal, without a second tab or a single copy and paste.

claude mcp add --transport http contentstudio https://mcp.contentstudio.io/mcp?api_key=YOUR_API_KEYPublishes to:
Quick Reference
Core Capabilities
Connecting ContentStudio gives Claude Code direct access to the core features you use every day, so it can manage workspaces, social accounts, content, media, and your publishing calendar from one session.
Tell Claude Code what you want to post, where, and when. It drafts and schedules a month of content across multiple platforms, including images, carousels, and videos.
Pull performance data for your posts and accounts without opening a dashboard.
Claude Code shows you the caption, network, media, and time, so you can make changes or approve it before anything is scheduled.
Review pending posts, approve or reject them, and add comments for your team before content moves forward.
Attach images, carousels, or videos to your posts, or save unfinished content as drafts for a teammate's review.
Read and reply to messages and comments across your connected networks, all from one session.
List posts by draft, scheduled, or published status, tweak unpublished copy, or remove posts you no longer need.
Add comments or internal notes to any post, no tab switching required.
Switch between client workspaces and the channels linked to them, and let Claude Code manage where your content gets published.
Setup
Connecting Claude Code to ContentStudio takes one command; no CLI to install.
One command adds ContentStudio as an MCP server in Claude Code. Where OAuth is not supported, use api_key in the query parameter or x-api-key in the header. Details on the ContentStudio MCP server page.
claude mcp add --transport http \
contentstudio https://mcp.contentstudio.io/mcp?api_key=YOUR_API_KEYUsing the integration
Run your social media by talking to Claude Code. It handles the everyday scheduling work, with ContentStudio doing the heavy lifting behind the scenes.
> Draft 30 LinkedIn posts from these five product updates and schedule them across the month. Mix product tips, customer use cases, team updates, and industry insights, using my best-performing time slots.
✓ Claude Code drafts all 30 posts, varies the content and formats, assigns publishing slots, and schedules the full batch after you approve it.
> Turn this engineering workflow into a technical LinkedIn post for developers. Explain the problem, show the key steps, and include a simple code example.
✓ Claude Code structures the technical details, writes the post, prepares the media direction, and schedules it after you approve the preview.
> Draft a LinkedIn post about our latest product update. Show me the final copy, target account, media, and scheduled time so I can review everything before it is queued.
✓ Claude Code prepares the complete post as a preview, so you can review the content and publishing details before anything is scheduled.
> Fetch the posts waiting for approval in this workspace, add my comments to the two that need changes, and send the approved ones to the publishing queue.
✓ Claude Code finds the pending posts, adds your feedback, and moves approved content forward without switching between tools.
> Show me everything scheduled this week across LinkedIn, X, and Facebook. Group the posts by platform and flag any overlapping publishing times.
✓ Claude Code checks your publishing calendar, organizes the scheduled posts, and highlights timing conflicts before they become a problem.
> Find this week's scheduled posts about our product tutorials, shorten their opening lines, and move all Tuesday posts to 9:00 AM without changing the rest of the copy.
✓ Claude Code finds the matching posts, applies the requested edits and time changes, then saves the updates across the batch.
Security & Trust
Secure authentication, workspace confirmation, and a preview-then-approve step keep every action safe, transparent, and under your control.
Standardized MCP connection: Claude Code reaches ContentStudio over the Model Context Protocol, an open standard that gives AI tools only the access they need.
Preview before every write: Claude Code drafts each post, then shows you a preview of the copy, network, and time. Nothing is scheduled until you approve it.
Human in the loop: Claude Code handles repetitive publishing at scale, but your team decides what gets approved, rejected, edited, or sent back.
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 |
Claude Code or Claude
Both connect to ContentStudio, but they run in different places. Using Claude in the browser or on desktop instead? See the ContentStudio Claude integration.
| Claude Code (in your terminal) | Claude (in the chat app) | |
|---|---|---|
| What it's for | For developers who work from the terminal. | For planning and posting by conversation. |
| You say | “Turn this engineering workflow into a technical LinkedIn post for developers.” | “Draft 30 LinkedIn posts from these five product updates and schedule them across the month.” |
| Connects | claude mcp add or the CLI and skill | Custom connector with the MCP link, then sign in |
| Runs | In your terminal | Claude on the web and Claude Desktop |
| Best for | Posting from where you already work, plus scripts and bulk jobs | Planning and approvals without a terminal |
Troubleshooting
Most issues come down to the MCP connection, the API key, or the wrong workspace.
Check that the URL was added correctly, including ?api_key=. A bare https://mcp.contentstudio.io/mcp with no key gets added but won't connect. Run claude mcp add --transport http contentstudio https://mcp.contentstudio.io/mcp?api_key=YOUR_API_KEY again to confirm it's registered. Where OAuth is not supported, use api_key in the query parameter or x-api-key in the header.
This usually means the API key in the URL is wrong, expired, or was regenerated in ContentStudio after the server was added. Generate a fresh key from Settings → API Keys, remove the existing entry with claude mcp remove contentstudio, and re-add it with the new URL.
The API key is tied to one ContentStudio workspace. If you manage multiple workspaces, check which key is in the URL. Generate a key from the correct workspace and re-add the server with that URL.
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.
Add the MCP server with one command, and let Claude Code draft, preview, schedule, and publish across every network from your terminal.
7-day free trial · No credit card · Cancel anytime
