How to Schedule Social Media Posts with Claude
You can schedule social media posts with Claude by connecting Claude or another AI agent through MCP or Claude Code Skills, then asking it to write, schedule, and publish content across your platforms. This guide covers both setup paths, the exact configuration fields to check, and the prompts that express immediate versus scheduled intent.
What this setup does
The task is to let an AI agent handle the posting workflow instead of switching between separate apps for drafting, scheduling, and publishing. You connect the agent once, then describe the work in natural language. The agent drafts the content, applies the timing you requested, and publishes or schedules it across the platforms you named. Before sending a large batch, review the resulting calendar so you can confirm the platforms, dates, and content scope match your intent.
Start at the agent connection page
Start at the agent connection page, which is where the two connection options are presented. Choose MCP if your client uses a server configuration file, or choose Claude Code Skills if you work from a terminal. Keeping the choice explicit matters because the setup steps, configuration files, and failure checks differ between the two paths.
Option A: MCP for Claude Desktop, Cursor, and similar clients
MCP is the first option and works with Claude Desktop, Cursor, and similar clients that read an MCP server configuration. Copy the configuration snippet shown in the MCP configuration example, then add it to claude_desktop_config.json or mcp.json, depending on which file your client reads. Replace YOUR_API_KEY with your own API key, save the file, and reload the client if your client requires it. Then paste the configuration into Claude and tell it to connect. Claude will confirm the connection, after which you can issue scheduling prompts. If the client does not confirm a connection, do not proceed to scheduling prompts; first check the file name, the JSON structure, and the Authorization header.
MCP configuration field map
The MCP configuration has four parts to verify. The top-level mcpServers object groups the server entries. Inside it, the server entry contains a url field pointing to the MCP endpoint path and a headers object. Inside headers, the Authorization field carries the bearer token in the form Bearer followed by your API key. The field map table below lists each part and the check to perform. A common failure is leaving YOUR_API_KEY unchanged, using the wrong configuration file for the client, or editing the JSON so that a comma or brace is misplaced.
Worked scheduling prompts
Once connected, describe the platforms, the amount of content, and the timing in a single prompt. The example scheduling prompts show three distinct intents: a week of LinkedIn content to be scheduled, a Twitter post to be published immediately, and 30 posts spread across the next month. Separate immediate and scheduled requests in your own prompts as well, because the timing instruction changes the expected result. After the agent responds, check that the scheduled items appear with the platforms and dates you asked for before treating the batch as complete.
Option B: Claude Code Skills in the terminal
If you use Claude Code in the terminal, the second option is Claude Code Skills. Run the installation command shown in the Claude Code Skills installation example, substituting the skills repository you are using for the placeholder. This gives Claude Code direct access to the posting actions as terminal skills. After installation, confirm that the skills are available in the terminal before asking Claude Code to schedule content.
Failure matrix: configuration, authentication, and connection checks
Use the failure matrix below when setup does not work. Work through the checks in order: confirm the client supports the connection method you chose, confirm the configuration file matches the client, confirm the API key is present and not a placeholder, and confirm the client reports a successful connection. Each failure has a specific check derived from the setup steps, so fixing the earliest failing check first avoids masking later problems.
Result: an AI-agent-created scheduled content calendar
The expected result is a calendar of scheduled content created through the AI agent, with the agent handling drafting and timing decisions and the connected service handling the platform publishing. Review the calendar entries for platform, date, and content before relying on them. If entries are missing or mistimed, reissue a narrower prompt that names one platform and one time window, then review the calendar again.
| Field | Location | Purpose | Check |
|---|---|---|---|
| mcpServers | Top level of claude_desktop_config.json or mcp.json | Groups the MCP server entries for the client | Confirm the object is present and correctly nested |
| url | Inside the server entry under mcpServers | Identifies the MCP endpoint path | Confirm the path is /mcp and the origin matches your deployment |
| headers | Inside the server entry under mcpServers | Carries request headers for the connection | Confirm the object is present inside the server entry |
| Authorization | Inside headers | Carries the bearer API key | Confirm the value is Bearer followed by a real API key, not YOUR_API_KEY |
Field names and structure are preserved from the source MCP configuration snippet; the endpoint origin is modularized as {{API_BASE_URL}} and the owned endpoint must be matched and verified at implementation stage.
| Failure | Likely cause | Check | Fix |
|---|---|---|---|
| Client does not list the server | Wrong configuration file for the client | Confirm whether the client reads claude_desktop_config.json or mcp.json | Add the configuration to the file the client actually reads |
| Connection rejected or not confirmed | Missing or placeholder API key | Confirm Authorization is Bearer followed by a real API key | Replace YOUR_API_KEY and reload the client |
| Configuration file fails to parse | Malformed JSON structure | Confirm mcpServers, url, and headers are nested with correct braces and commas | Correct the JSON and save the file again |
| Client does not support MCP | Unsupported client | Confirm the client supports MCP server configuration, as Claude Desktop and Cursor do | Use a supported client or switch to the Claude Code Skills path |
| Skills not available in terminal | Skills installation not run or not completed | Confirm the installation command completed without errors | Run the installation command again and confirm the skills appear |
Checks are derived only from the source setup steps; no runtime test evidence was supplied.
Frequently asked questions
Should I use MCP or Claude Code Skills?
Use MCP when your client supports an MCP server configuration, such as Claude Desktop or Cursor. Use Claude Code Skills when you work in a terminal with Claude Code and want the actions available as terminal skills. The two paths are distinct setup options for the same scheduling task.
What should I check if Claude does not connect?
Check that the configuration file matches your client, that the Authorization header contains a real API key instead of the placeholder, and that the client reports the server as connected before asking it to schedule or publish.
What details should a scheduling prompt include?
State the platforms, the amount or scope of content, and whether you want immediate publishing or scheduled delivery. The example prompts in this guide separate a week of LinkedIn content, an immediate Twitter post, and 30 posts spread across a month.
{
"mcpServers": {
"social-media-posting": {
"url": "{{MCP_BASE_URL}}/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}npx skills add <SKILLS_REPOSITORY> --all