Skip to content

Claude Code MCP social media posting

Claude Code MCP social media posting lets you install a hosted MCP server in Claude Code with one command, connect social accounts once, and then publish, schedule, cross-post, and analyze posts from natural-language prompts in your terminal.

Install the hosted MCP server in Claude Code
claude mcp add social-media --transport http --header "Authorization: Bearer YOUR_API_KEY" {{MCP_BASE_URL}}/mcp
Illustrative request
Example line 1

claude mcp add social-media --transport http --header "Authorization: Bearer YOUR_API_KEY" {{MCP_BASE_URL}}…

Supported workflow specifications include Twitter, LinkedIn, Instagram, TikTok, YouTube, and Bluesky as platforms in scope, subject to the accounts you actually connect and verify. You do not need to write tool definitions or SDK glue: describe the outcome, and Claude Code selects the appropriate tool for the platforms you have actually connected.

What you can build: publish, schedule, cross-post, and analyze

This integration is built around a hosted MCP server, where MCP stands for Model Context Protocol. With it installed in Claude Code, you can ask for a single update to go out across several connected networks at once, ask for a LinkedIn item to be queued for a specific morning time, turn a week of merged pull requests into a thread that is queued for later, or bring performance figures for recent posts into the current terminal session. Each of those jobs depends on which accounts you have connected, so check the connection list first with list_integrations before assuming a platform such as Twitter, LinkedIn, Instagram, TikTok, YouTube, or Bluesky is available.

Why use an MCP server with Claude Code

One command connects the hosted server, so there is nothing to install locally. Talk instead of coding: tell Claude Code to post a message on a connected account and it resolves the integration, calls the API through the MCP tool, and returns the live URL, without you copy-pasting account IDs or remembering endpoint shapes. Scheduling from the CLI turns a sentence such as schedule a LinkedIn post for tomorrow at 9am ET into a queued post you can review and cancel from the dashboard before it ships. Cross-posting in one sentence, such as posting a changelog summary to Twitter, LinkedIn, and Bluesky, relies on Claude Code handling the platform list while the MCP handles platform differences, qualified to the accounts actually connected. The typed tool surface means each MCP tool ships with a schema describing its parameters, so Claude Code introspects them and calls the right one without you loading documentation into the conversation. The source states 34 MCP tools; treat that count as a parity specification pending implementation matching. The server is also composable with other MCPs, so you can combine it with GitHub, Linear, or Notion MCPs in one session to build workflows such as reading yesterday's merged pull requests and drafting a thread about the highlights.

How to set it up

First, get your API key from the dashboard access-keys area and keep it secret; it is used as a Bearer token in the install command. Second, add the MCP server to Claude Code using the exact install command in the Install the hosted MCP server in Claude Code example, then restart Claude Code so the tools are available in the next session. Third, connect each platform once via OAuth, then describe what you want. Claude Code calls the right tool, such as create_post, list_integrations, or get_analytics, and shows you the result. Use the Worked prompt-to-tool examples example to see the expected flow for publishing, scheduling, cross-posting, and analytics.

Compatibility with Cursor, Zed, and other Streamable-HTTP MCP clients

Because the server follows the standard Model Context Protocol over Streamable-HTTP, it is not limited to Claude Code. Cursor, Zed, Continue, Claude Desktop, and ChatGPT can connect as Streamable-HTTP MCP clients using the same hosted URL pattern. The setup steps are the same in each client: supply your API key as the Authorization Bearer header, connect your social accounts once via OAuth, and verify with list_integrations before publishing.

Troubleshooting and verification checklist

If the tools do not appear, restart Claude Code after running the install command, because the source contract requires a restart before the next session. If calls fail with an authentication error, check that YOUR_API_KEY was replaced with a real key and that the Authorization Bearer header was included. If a post fails for a specific platform, run list_integrations to confirm that account is connected via OAuth; an unconnected account cannot be posted to. If a scheduled post has the wrong time, check that scheduledFor and timezone were both set, and review or cancel it from the dashboard posts view before delivery. If analytics return nothing, confirm you are querying a connected account and a period that includes published posts.

Scheduling field map for scheduled posts
FieldMeaningSource-stated behavior
scheduledForDate and time at which the post should be publishedSet from a natural-language request such as Friday at 9am
timezoneTime zone used to interpret scheduledForSet alongside scheduledFor, for example ET for a 9am ET request

Field map limited to source-stated scheduledFor and timezone; full create_post schema not supplied and not invented.

MCP tools used in the Claude Code workflow
ToolUse in this workflowWhen to use it
list_integrationsDiscover connected social accountsBefore publishing, cross-posting, or troubleshooting an unconnected account
create_postPublish or queue a postWhen you ask Claude Code to post immediately or schedule for later
get_analyticsRetrieve post analyticsWhen you ask Claude Code to pull analytics into your session

Tool names are exact source identifiers; parameter schemas beyond scheduledFor/timezone were not supplied.

Failure and verification checklist
CheckPass conditionFailure action
Restart Claude Code after installMCP tools are available in the next sessionRestart again and re-run the install command
API key presentAuthorization Bearer header uses a real key, not YOUR_API_KEYReplace the placeholder and re-run the install command
Accounts connectedlist_integrations shows each platform you plan to post toComplete one-time OAuth for the missing platform
Scheduling fields setscheduledFor and timezone match the requested time and zoneReview the scheduled post in the dashboard and cancel or edit before delivery

Checklist derived from source-stated restart, key, OAuth, and scheduling behavior.

Frequently asked questions

What is the MCP install command?

Run claude mcp add social-media --transport http --header "Authorization: Bearer YOUR_API_KEY" {{MCP_BASE_URL}}/mcp, replacing YOUR_API_KEY with your own key. Restart Claude Code afterwards so the tools are available in the next session. Nothing runs locally; the MCP server is hosted.

Do I need to write any code?

No. After connecting, describe what you want in natural language. Claude Code calls the right MCP tool, such as create_post, list_integrations, or get_analytics, and shows the result.

Can I use this in Cursor or Zed instead of Claude Code?

Yes. The server follows the standard Model Context Protocol and can be used by Streamable-HTTP MCP clients, including Cursor, Zed, Continue, Claude Desktop, and ChatGPT, using the same hosted URL pattern.

How do I connect my social accounts?

Connect each platform once using OAuth. After that one-time connection, the MCP can use those connections from any Claude Code session without reconnecting per session.

What if I want to schedule posts instead of publishing immediately?

Tell Claude Code when to publish. It should set scheduledFor to the requested date and time and timezone to the requested zone, for example America/New_York for ET. Review scheduled posts in the dashboard view before delivery so you can cancel or edit them.

Can I combine this with other MCPs?

Yes. Pair this MCP server with GitHub, Linear, or Notion MCPs in the same session. For example, read yesterday's merged pull requests and draft a thread about the highlights, then queue it for posting.

What plan details should I check before using the integration?

Check the plan limits and billing terms published for your deployment before relying on a specific allowance. Connecting an MCP client does not establish a pricing or free-tier entitlement.