Claude Code for Social Media: Schedule Posts from Your Terminal

Why Manage Social Media from the Terminal?

If you're a developer, your terminal is home. You write code, commit changes, deploy services, and debug production issues — all without touching a mouse. But the moment you need to post a product update to LinkedIn or schedule an Instagram carousel, you're yanked out of your flow and into a browser-based dashboard.

That context switch is expensive. Studies estimate it takes 23 minutes to regain deep focus after switching tasks. For developers who ship code and then need to announce it on social media, the traditional workflow looks like this: finish the feature, open a new tab, navigate to your scheduling tool, write the post, pick the time, upload the image, click publish, close the tab, try to remember what you were doing.

What if you could do all of that without leaving the terminal?

What you'll learn in this guide:

• How to connect Publora's MCP server to Claude Code in one command
• 6 real-world use cases with terminal conversation examples
• How to cross-post, check analytics, and bulk-schedule from your shell
• Power user tips: aliases, git hooks, and combining MCP servers
• Full platform support table for all 10 supported networks

With Claude Code — Anthropic's official CLI for Claude — and Publora's MCP server, you get a terminal-native social media workflow that is scriptable, version-controllable, and fits into the same environment where you already spend your day. No dashboards. No browser tabs. Just your terminal and natural language.

One-Command Setup

Connecting Claude Code to Publora takes one command and a browser sign-in — no API key to copy. The only prerequisite is at least one social media account connected in the Publora dashboard. Add the server, then run /mcp in Claude Code, select publora, choose Authenticate and approve access in the browser window that opens.

claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp

For CI or a machine that can't open a browser, use a Publora API key instead (from API in the sidebar at app.publora.com) and add --header "Authorization: Bearer sk_YOUR_API_KEY" to the same command. Once you've signed in, verify the connection:

// .mcp.json — drop this in your project root
{
  "mcpServers": {
    "publora": {
      "type": "http",
      "url": "https://mcp.publora.com/mcp"
    }
  }
}

Use Case 1: Schedule a LinkedIn Post for Tomorrow Morning

You just finished a feature and want to announce it on LinkedIn. In a browser workflow, that's: open Buffer/Hootsuite, write the copy, pick the time, click schedule. In Claude Code, it's a conversation:

Notice what happened: Claude Code automatically called list_connections to find your LinkedIn platform ID, converted "9am EST" to ISO 8601 UTC, and called create_post. You didn't need to know any API details.

Use Case 2: Create an Instagram Carousel from Local Images

You have a set of product screenshots in your ./marketing/ folder and want to turn them into an Instagram carousel. Claude Code can read your filesystem, find the images, upload them, and create the post.

Use Case 3: Cross-Post to 5 Platforms Simultaneously

One of Publora's most powerful features is cross-platform posting. A single API call can schedule the same post to multiple platforms. Claude Code makes this conversational:

Publora handles the platform-specific differences automatically. Your 280-character limit on X? If the content is too long, it auto-splits into a thread. Threads' 500-character cap? Same treatment. Bluesky and Mastodon don't thread, so Publora flags a post that's too long for them before it's scheduled.

Use Case 4: Check Your Analytics — "How Did My Last LinkedIn Post Perform?"

You posted a thought leadership piece on LinkedIn last Tuesday. You want to know how it did — but you don't want to open the LinkedIn app or a dashboard. Just ask Claude Code:

The key insight here: Claude Code doesn't just fetch data — it analyzes it. It noticed the pattern in your engagement and called it out, something a regular analytics dashboard wouldn't do. This is where AI-powered workflows genuinely outperform traditional tools.

Use Case 5: Bulk Schedule a Week's Content from a CSV

This is where the terminal workflow gets really powerful. You have a content plan in a CSV file — maybe your marketing team created it in Google Sheets and exported it. Instead of manually creating 7 posts, you hand the file to Claude Code:

day,time,platform,content
Monday,09:00,linkedin,"Starting the week with a deep dive into our new caching layer..."
Tuesday,14:00,twitter,"Hot take: Most API rate limiting is done wrong. Here's why..."
Wednesday,10:00,linkedin,"3 things I wish I knew before building a multi-tenant SaaS..."
Thursday,11:00,twitter+linkedin,"We just hit 10K users. Here's the growth chart and what we learned..."
Friday,09:00,linkedin,"Weekend reading: The best engineering blog posts I read this week..."
Saturday,11:00,instagram,"Behind the scenes of our engineering team offsite..."
Sunday,16:00,twitter,"Week in review: shipped 12 PRs, fixed 3 bugs, broke prod once..."

This is something you simply cannot do quickly in a web dashboard. Reading a local file, parsing it, and creating 7 API calls — Claude Code handles all of it in one conversation turn. For the full API reference on bulk operations, see the bulk scheduling guide.

Use Case 6: Auto-Post When You Ship Code (Git Hook)

This is the developer dream: you push a release to production, and your social media automatically announces it. There are two approaches — a git hook with Claude Code, or a simpler curl-based approach using the REST API directly.

Option A: Git hook with Claude Code

Create a .git/hooks/post-commit (or use Husky) that invokes Claude Code in non-interactive mode:

#!/bin/bash
# .git/hooks/post-commit (make executable: chmod +x)

# Only trigger on main branch
BRANCH=$(git rev-parse --abbrev-ref HEAD)
if [ "$BRANCH" != "main" ]; then
  exit 0
fi

# Get the commit message
COMMIT_MSG=$(git log -1 --pretty=%B)

# Only announce releases (commits starting with "release:")
if [[ "$COMMIT_MSG" == release:* ]]; then
  echo "Announcing release on social media..."
  # Print mode can't stop to ask for permission, so allow the two Publora tools it needs
  claude --print "Based on this release commit message, create a professional LinkedIn post announcing the release. Schedule it for 30 minutes from now. Commit message: $COMMIT_MSG" \
    --allowedTools "mcp__publora__list_connections" "mcp__publora__create_post" 2>/dev/null &
fi

Option B: Direct API call (no Claude Code)

For CI/CD pipelines (GitHub Actions, GitLab CI), a direct curl call to Publora's REST API is simpler and faster:

#!/bin/bash
# In your CI/CD pipeline after deploy step

RELEASE_VERSION=$(git describe --tags --abbrev=0)

curl -s -X POST https://api.publora.com/api/v1/create-post \
  -H "Content-Type: application/json" \
  -H "x-publora-key: $PUBLORA_API_KEY" \
  -d "{
    \"content\": \"v${RELEASE_VERSION} is live! Check out the changelog: github.com/acme/app/releases/tag/${RELEASE_VERSION}\",
    \"platforms\": [\"linkedin-ABC123\", \"twitter-DEF456\"],
    \"scheduledTime\": \"$(date -u -d '+30 minutes' +%Y-%m-%dT%H:%M:%SZ)\"
  }"

Power User Tips

Once you have the basic workflow down, here are some techniques to make it even faster.

Shell aliases for common tasks

# Add to ~/.bashrc or ~/.zshrc
# Print mode can't stop to ask for permission, so allow Publora's tools up front
social() { claude --print "$*" --allowedTools "mcp__publora"; }

# Usage:
social "Schedule a LinkedIn post for tomorrow at 9am: Just shipped our new API docs"
social "What are my scheduled posts for this week?"
social "Delete the post I scheduled for Friday"

Combine with other MCP servers

Claude Code supports multiple MCP servers simultaneously. You can connect Publora alongside other tools for powerful combined workflows:

{
  "mcpServers": {
    "publora": {
      "type": "http",
      "url": "https://mcp.publora.com",
      "headers": { "Authorization": "Bearer sk_PUBLORA_KEY" }
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"]
    },
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./content"]
    }
  }
}

This is the killer feature of the MCP ecosystem — tools compose naturally. Claude Code reads from GitHub, processes the data, and writes to Publora in a single conversational flow.

Content templates as local files

Store your recurring post formats as text files and reference them from Claude Code:

# ~/templates/release-announce.txt
We just shipped {version}!

Key highlights:
{highlights}

Full changelog: {url}

#opensource #devtools #release

Supported Platforms

Publora supports 10 social media platforms through its API and MCP server. Here's what you can do from Claude Code on each one:

Platform	Post Types	Character Limit	Media	Analytics
LinkedIn	Text, image, video, documents (PDF)	3,000	Images, video	Impressions, reach, reactions, comments, reshares (REST API)
X (Twitter)	Text, image, video, auto-threads	280 (auto-threads if longer)	Images, video, GIF	Not available
Instagram	Photo, carousel (2-10), Reels, Stories	2,200	JPEG, PNG, WebP (WebP auto-converted), 8 MB; video MP4, MOV	Not available
Threads	Text, image, video	500	Images, video	Not available
Telegram	Text, image, video	4,096 (text) / 1,024 (captions)	Images, video, documents	Not available
Facebook	Text, image, video	63,206	Images, video	Not available
TikTok	Video	2,200	Video (MP4)	Not available
YouTube	Video	5,000 (description)	Video	Not available
Mastodon	Text, image, video	500	Images, video	Engagement counts, followers (post_stats, profile_stats)
Bluesky	Text, image, video	300	Images, video	Engagement counts, followers (post_stats, profile_stats)
Pinterest	Connect only (Publora can't publish to Pinterest)	—	—	—

The Complete MCP Tools Reference

When you connect Publora to Claude Code, you get access to 20 active MCP tools, plus 12 company_* tools for Agency client work that this guide doesn't cover. Here's a quick-reference of the most commonly used ones:

For the full reference with parameters and response examples, see the MCP tools reference.

Why Claude Code + MCP Is Different from Other Integrations

You might be wondering: "Can't I already do this with Zapier or n8n?" Yes — and Publora supports Zapier, n8n, and Make. But the Claude Code + MCP approach is fundamentally different:

The MCP approach shines for interactive, ad-hoc tasks — the kind of social media work that developers do alongside coding. It's not a replacement for automation pipelines; it's a complement that fills the gap where automation is too rigid and manual dashboards are too slow.

Getting Started in 60 Seconds

Here's the fastest path from zero to your first terminal-scheduled post:

1. Create a Publora account and connect at least one social media account
2. Add to Claude Code:

claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp

3. In Claude Code, run /mcp, select publora, choose Authenticate and sign in to Publora in the browser window that opens — no API key needed. For CI or a headless machine, create a key under API in the sidebar and add --header "Authorization: Bearer sk_YOUR_API_KEY" to the command instead.
4. Try your first command:

That's it. You're managing social media from your terminal. No dashboards, no browser tabs, no context switching.

Frequently Asked Questions

Further Reading

• MCP Client Setup Guide — Full setup instructions for Claude Code, Claude Desktop, Cursor, and more
• MCP Tools Reference — Every tool with parameters and response examples
• Cross-Platform Posting — How content adaptation works across platforms
• Bulk Scheduling Guide — CSV imports and batch operations
• LinkedIn Analytics Guide — Post-level metrics and account insights
• MCP Examples — More conversation examples and use cases
• Rate Limits — Platform and API rate limits