Plan and schedule posts
Tell the Agent what to publish, where, and when. Save posts as drafts, add them to the queue, or schedule them as feed posts, Reels, Stories, carousels, videos, or Shorts.
Connect ContentStudio to Cursor with one MCP link or the ContentStudio CLI. Ask the Agent to draft, schedule, and approve posts across all major social networks, turn your changelog into launch posts, and check analytics without leaving your editor.

{ "mcpServers": { "contentstudio": { "url": "https://mcp.contentstudio.io/mcp?api_key=YOUR_API_KEY" } }}Publishes to:
Quick Reference
Core Capabilities
The same social media management features your team uses in ContentStudio, available from the Agent panel.
Tell the Agent what to publish, where, and when. Save posts as drafts, add them to the queue, or schedule them as feed posts, Reels, Stories, carousels, videos, or Shorts.
Ask the Agent to create images and videos with ContentStudio's AI Studio, and attach them to your posts.
Point the Agent at a changelog, release notes, a README, or blog drafts in your repo. It writes a version for each network and schedules them.
Images and videos in your project go straight to your ContentStudio media library through the CLI, then get attached to the posts that need them.
Ask how a launch or last week's posts performed and get the numbers back in the chat.
Read comments and messages across networks and draft replies without switching tabs.
List posts waiting on you, approve or reject them, and leave a comment explaining why.
Filter posts by draft, scheduled, or published status, update unpublished posts, or delete ones you no longer need.
Move between client workspaces and check their campaigns, categories, labels, and team members before you post.
Setup
Two quick steps are all it takes to connect Cursor with ContentStudio and start scheduling your social media from the Agent panel.
Open (or create) .cursor/mcp.json in your project, or ~/.cursor/mcp.json for a global setup, and add the entry below. Grab your API key from ContentStudio’s Settings → API Keys, swap it in for YOUR_API_KEY, and save the file. Restart Cursor, or reload MCP servers from Cursor’s settings panel, to pick up the new entry. Where OAuth is not supported, use api_key in the query parameter or x-api-key in the header.
{
"mcpServers": {
"contentstudio": {
"url": "https://mcp.contentstudio.io/mcp?api_key=YOUR_API_KEY"
}
}
}Once it’s connected, just ask Cursor to do the work: “Schedule this post for tomorrow at 9am” or “Show me what’s queued this week on ContentStudio.” Cursor calls ContentStudio through the MCP server, no separate login step needed. Details on the ContentStudio MCP server page.
Using the integration
Anything you'd do in the ContentStudio dashboard, plus work that starts from files in your project.
> Read the v2.4 section of CHANGELOG.md and schedule a LinkedIn post and an X thread for tomorrow at 9 AM.
✓ Posts drafted from your notes, previewed, and scheduled once you approve.
> Turn the Getting Started section of README.md into a 5-post thread on X and Threads for Thursday at 10 AM.
✓ A thread for each network, ready in your calendar.
> Upload the images in /assets/launch and create one Instagram post per image, one hour apart, starting Friday at 10 AM.
✓ Each image uploaded to your media library and scheduled as its own post.
> Schedule the five posts in content/social/next-week.md on LinkedIn and Facebook, one per weekday at 9 AM.
✓ Five posts spread across the week, each on both networks.
> How did yesterday's launch posts perform on LinkedIn and X?
✓ Engagement for each post, with the strongest one called out.
> Show posts waiting for approval in the Bloom Bakery workspace and approve the two about the new menu.
✓ Pending posts listed, the two you named approved, the rest left alone.
Security & Trust
By default, Cursor asks before it runs MCP tools or terminal commands, and ContentStudio keeps every connection scoped and reviewable.
Approval by default: Cursor asks before it runs MCP tools and terminal commands, and any approval workflow on your ContentStudio workspace still applies.
Scoped API key: The MCP link uses a single api_key that talks only to the ContentStudio public API. Revoke or replace it anytime.
No password sharing: The MCP route connects with your ContentStudio API key; your social media passwords never pass through Cursor.
Dry-run previews: With the CLI, add --dry-run to preview any request first, before it reaches the API.
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 |
Cursor Agent or Automations
Both use the same ContentStudio connection. The difference is whether you're at the keyboard.
| Cursor Agent | Cursor Automations | |
|---|---|---|
| Where it runs | In your editor, on your machine | As a cloud agent on Cursor's servers |
| How it starts | You type a prompt in the Agent panel | A schedule, webhook, Slack message, or other trigger |
| Connects via | mcp.json or the CLI and skill | The ContentStudio MCP server, added as a tool |
| You | Review and approve each step | Write the prompt once, then review the results in ContentStudio |
| Best for | Posting while you code, one-off and batch scheduling | Recurring drafts, weekly plans, and reports |
Troubleshooting
Most issues come down to the MCP connection, the API key, or the wrong workspace.
Check that the URL in mcp.json was entered correctly, including ?api_key=. A bare https://mcp.contentstudio.io/mcp with no key gets saved but may not connect. Confirm the file is saved, and Cursor was restarted (or MCP servers reloaded from settings) after adding it. 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 entry was added. Generate a fresh key from Settings → API Keys, update the URL in mcp.json, and restart Cursor.
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 update the entry 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 or the CLI, and let the Agent draft, schedule, and approve posts across every network, without leaving your editor.
7-day free trial · No credit card · Cancel anytime
