To bulk schedule a month of social posts from a CSV, you write one row per post, drop the file into a tool that reads it, and let the scheduler queue every row at once. Creator OS takes that file through its API, its CLI or its MCP server, so an AI agent can read the calendar and create the posts for you.
CSV (30 rows)
|
v
Agent or CLI reads the file
|
v
POST /v1/posts (one call per row)
|
+--> scheduled queue (schedule_at + timezone)
|
+--> missing_platforms reported back
|
v
Published on each network at its timeWhat Is Bulk Scheduling From a CSV (And Why It Beats Scheduling One Post at a Time)
Bulk scheduling from a CSV means your content calendar lives in a spreadsheet and the tool turns each row into a timed post, so you stop opening a composer thirty times.
The advantage is not speed alone. A CSV is a file you can review, diff and keep. When you schedule one post at a time in a dashboard you lose the shape of the month: the gaps, the repeats, the day where three platforms get the same caption. A single file shows all of it. You edit a cell, re-run the import for the rows you changed, and the calendar is fixed.
It also makes the work reviewable by someone else. A client or a teammate can read a spreadsheet. They will not click through your scheduler.
How to Format Your CSV So Every Row Becomes a Scheduled Post
Keep the file flat: one row per post, one column per field, and platforms as a comma separated list inside a quoted cell.
These are the fields the Creator OS post endpoint accepts, mapped to columns you can plan around. Full field details are in the posts API reference.
| Column | What goes in it | Example |
|---|---|---|
| content | The caption, under each platform’s limit | “Three ways to price a retainer” |
| platforms | Comma separated, quoted | “instagram,tiktok,threads” |
| media | A med_ id or a URL |
https://cdn.example.com/clip.mp4 |
| schedule_at | ISO date and time | 2026-03-04T14:00:00 |
| timezone | The zone that timestamp is in | America/Toronto |
| post_type | Post shape where the platform has one | reel |
| draft | true to hold it back for review | true |
Upload media once with POST /v1/media. It returns a med_ id you can reuse in every row that needs the same file. Putting URLs in the media column also works, but a med_ id is stable if the source file moves.
Two rules save you an hour of debugging. Quote any cell containing a comma, which is every platform list and most captions. Keep the timestamp column in one format from the first row to the last, because a mixed column will schedule your Monday post on a Thursday.
How to Schedule a Month of Social Posts From a CSV in Creator OS
The fastest path is to hand the CSV to an AI app connected to the Creator OS MCP server, or to loop the rows through the CLI, both of which send the same requests to the posts endpoint.
Here is the manual version, which is the one to use when you want to see the request once before an agent runs it thirty times:
POST /v1/posts
{
"content": "Three ways to price a retainer",
"platforms": ["instagram", "tiktok", "threads"],
"media": ["med_01HX..."],
"schedule_at": "2026-03-04T14:00:00",
"timezone": "America/Toronto"
}The endpoint is authenticated with a Creator OS API key (cos_live_...) that is pinned to one workspace. Find the base URL and the auth details in the Creator OS docs.
That is it. One row, one call, and the post sits in the queue until its time. Thirty rows is thirty calls. The advanced form of the same endpoint takes platforms as objects when you need per platform options, and account_ids when one row should go out on specific accounts rather than every account on that network.
If you would rather hand the file to Claude or ChatGPT, connect the hosted MCP server and say: “Read this CSV and create a scheduled post for each row using create_post. If a row lists a platform I have not connected, skip it and tell me.” The agent calls create_post per row and reports back. Setup steps are in the MCP docs.
How to Schedule Instagram Posts and Threads Posts From the Same File
You can schedule Instagram posts and Threads posts from one CSV because the platforms column is a list, not a single choice, and Creator OS applies each network’s own rules on the way out.
A row with "platforms": ["instagram", "threads"] becomes two posts. Instagram gets its Reels or feed format, and if the account is Business or Creator the Reel cover, collaborators and first comment options apply. Threads gets its own constraints: 500 characters per post and 250 posts per 24 hours. When one caption has to fit both, run creatoros validate:post-length --text "..." before you import, or call the check_caption_length tool if an agent is doing the work.
Threads also supports multi-post threads and a first reply, so a row that needs a sequence is better split across several rows in order. If you are still working out the Threads side, the Threads scheduler post covers how a thread is assembled, and the Instagram scheduling walkthrough covers Reels and Stories. For the whole month planning view, read how to schedule a month of content.
One habit worth adopting: put the platform list in the same order every time, Instagram then Threads then TikTok. When your file is sorted the same way as your accounts, mistakes stand out.
How to Automate Social Posting With an MCP Server or CLI
The MCP server is how you automate social posting from a spreadsheet without writing code: the AI app reads the file and calls the tools, and every call lands in the same queue as a manual post.
For Claude, open Settings, then Connectors, then Add custom connector, and paste https://mcp.creatoros.ca/mcp. Sign in, pick the workspace, and choose read only or read & write. On an agency plan you make one connection per client workspace, which is exactly what you want when each client has their own CSV. ChatGPT takes the same URL as a connector in developer mode. The server exposes about 160 tools, including create_post, list_posts, upload_media_from_url and get_best_time_to_post.
If you prefer the terminal, the CLI is a thin wrapper over the same API:
creatoros posts:create \
--text "Three ways to price a retainer" \
--platforms instagram,threads \
--media https://cdn.example.com/reel.mp4 \
--scheduledAt 2026-03-04T14:00:00 \
--timezone America/TorontoWrap that in a loop over your rows and the month is queued. The CLI docs list every flag. There is also a bulk path that reads a calendar file directly: creatoros posts:bulk-upload --file calendar.json --dryRun. Run it with --dryRun first. It tells you what would be created without creating it, which is the cheapest way to catch a broken date column.
To watch an agent run a calendar end to end, the walkthroughs are on the KevBuildsApps YouTube channel. If you use Cursor rather than Claude, the Cursor MCP setup post covers that path, and the CLI client posting walkthrough is the agency version of this workflow.
What to Check Before You Import (Timezones, Duplicates, Failed Rows)
Run these four checks before an agent touches thirty rows, because fixing a queue after it publishes is not the same job as fixing a spreadsheet.
- Timezones. Every row needs
schedule_atandtimezonetogether. If your team writes in local time and the file mixes zones, the timestamps are wrong even though each one looks fine on its own. - Duplicates. A re-run creates new posts. Use
creatoros posts:list --status scheduled --from 2026-03-01 --to 2026-03-31and read it before the second import, or have the agent calllist_postsfirst. - Missing platforms. A row that names a network you have not connected comes back with that network in
missing_platforms, and the rest of the platforms still publish. Read that field. It is the difference between “Instagram and Threads posted” and “only Threads posted”. - Media. Run
creatoros validate:media --url ...on new files. A dead URL turns into a failed post at the scheduled time, not at import time.
Failed rows land with a status you can query, and creatoros posts:retry <postId> retries one after you fix the cause. Nothing about a CSV import bypasses a platform’s rules, so an over length caption or an unsupported format still fails at the network.
Can You Schedule Social Media Posts With MCP Agents?
Yes. Any MCP capable AI app can schedule social media posts when it is connected to the Creator OS MCP server, and the agent works from the same tools you would call by hand.
Connect the server once and the agent can read list_posts, check get_best_time_to_post before assigning a slot, upload a file with upload_media_from_url, and create each post with create_post. Destructive tools such as deleting a post or disconnecting an account are marked, so the AI app asks you first. A read only connection only sees read tools, and the API refuses writes from it, which is a sensible setting while you are still testing a prompt.
The Claude Code plugin adds another layer: it ships the MCP server, campaign builder skills and 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. Details are in the Claude Code plugin docs.
For a different approach, Social Agents is an open source agent harness that runs your socials on Creator OS. It interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports on what it did. Bring your own model. It is covered in the launch video.
FAQ
How do you bulk schedule social media posts from a CSV?
Put one post per row with a caption, a platform list, any media and a scheduled time, then send each row to a scheduler that accepts scheduled posts. In Creator OS that means one POST /v1/posts per row, or one creatoros posts:create command per row, or an AI agent calling create_post for each line. The posts land in the same queue a manual post would.
What columns should a social media scheduling CSV have?
At minimum: content, platforms, schedule_at and timezone. Add media for a med_ id or a file URL, post_type where the network has shapes like Reels or Stories, and draft if you want a human to approve before publishing. Quote any cell with a comma in it, which includes every platform list.
Can you schedule Instagram posts and Threads posts from a CSV at the same time?
Yes. List both networks in the platforms cell of one row and Creator OS creates a post for each, applying Instagram’s rules and Threads’ 500 character limit and daily post cap separately. If a caption fits one but not the other, run the length check first and split the row.
How do you schedule social media posts with MCP?
Add https://mcp.creatoros.ca/mcp as a custom connector in your AI app, sign in to Creator OS, choose a workspace and grant read and write. Then ask the agent to schedule the posts, or hand it the file. Step by step setup is at creatoros.ca/docs/mcp.
Can AI agents automate social media posting from a spreadsheet?
Yes, when the spreadsheet is readable and the agent has a posting tool. Paste the rows into the chat or give the agent access to the file, and it calls create_post once per row, reads missing_platforms for any gap, and reports which rows were queued. Read only connections cannot publish, so grant write access only when you are ready.
Get started
Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. That covers Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Threads, Reddit, Discord, Slack and WhatsApp, plus Skool communities.
Build your CSV, run it once with a dry run, then queue the month. Sign up at https://www.creatoros.ca/sign-up and connect your accounts.
Get started for $0
Free trial for new subscribers. Cancel anytime.
