← All articles

Claude Code MCP for Social Media: Publish Release Posts From the Terminal

Claude Code already writes your changelog, your release notes and half of your commit messages. The last step of a release, telling people about it, usually means leaving the terminal, opening five social apps and rewriting the same update five times. With an MCP server, Claude Code can do that step too.

This guide shows how to add the 1Social MCP server to Claude Code so you can publish release posts to X, LinkedIn, Bluesky, Threads, Facebook Pages, Instagram, TikTok and YouTube Shorts without leaving your project. It covers the one-line setup, the scopes worth choosing, prompts that work, and what Claude Code is not good at here.

How MCP works in Claude Code

Claude Code connects to external tools through the Model Context Protocol. A remote MCP server is added with a single command and stored in your config. Once it is connected, its tools show up next to Claude's built-in ones, and Claude decides when to call them based on what you ask.

1Social is a remote MCP server over HTTP with OAuth sign-in. Its tools cover the whole publishing loop: list your connected accounts, preview a post against each network's rules, publish now or schedule, attach media, retry a single failed network, and read back a receipt per network.

Step 1: Create a 1Social account

  1. Sign up at 1social.dev/login. Every plan has a free trial.
  2. Connect the networks you want to post to. Each one signs in through its own page in your browser, so Claude Code never sees those passwords.
  3. Pick a plan on the pricing page: Solo at $29 a month for 600 deliveries, or Pro at $49 a month for 1,600 deliveries with scheduling up to 30 days ahead.

Step 2: Add the server

In your terminal:

claude mcp add --transport http 1social https://mcp.1social.dev/mcp

That is the whole install. Then, inside Claude Code, run:

/mcp

Pick 1social and follow the browser login. If you are on a machine without a browser, you can start the login from the shell with claude mcp login 1social --no-browser.

Which scope to use

Claude Code stores MCP servers in one of three scopes:

  • local (the default): only you, only this project.
  • user: only you, in every project. Add --scope user to the command. This is usually the right choice for a publishing tool you use across repos.
  • project: saved in .mcp.json at the project root and shared with your team through git. Each teammate still signs in with their own 1Social account, because the config holds only the server address.

To check that it is connected:

claude mcp list

Step 3: Publish a release post

Here is a prompt that works well at the end of a release:

Read CHANGELOG.md and write a short release post for v2.4.
Make an X version under 280 characters, a LinkedIn version,
and a Bluesky version under 300. Preview all three in 1Social
and show me what each network would reject. Don't publish yet.

Claude reads the changelog, drafts three versions, and runs them through 1Social's preview. The preview reports caption overflow, missing images and cost before anything is sent. When the drafts look right:

Publish the X and Bluesky versions now. Schedule LinkedIn for tomorrow 9:00 Berlin time.

You get a receipt per network: what landed, what failed and why, and what could not be confirmed.

More prompts for developers

Post a screenshot of a new feature:

Take screenshots/new-dashboard.png and post it to X and LinkedIn
with a one-line description of the feature from the last commit message.

A launch thread for Bluesky:

Turn the "What's new" section of the README into a Bluesky post.
If it's over 300 characters, preview it as a thread first.

Fix a failed delivery:

The LinkedIn post from this morning failed. Find out why in 1Social
and retry only LinkedIn.

Check the queue:

List everything scheduled in 1Social for this week.

A post you schedule from the terminal also shows up in the 1Social web app and in any other client connected to the same account, so you can review or edit it from your phone later.

What Claude Code is not the right tool for

Be honest with yourself about the job:

  • It is not a scripting interface. The 1Social tools answer to instructions, not flags. You cannot pipe a file into a publish from a shell script. For unattended, scripted posting from CI, use the 1Social HTTP API instead.
  • It does not watch your repo. Nothing posts automatically when you tag a release. You ask, Claude acts.
  • Some posts cannot be undone. On Threads, TikTok and YouTube, a published post cannot be deleted through the API. Keep "preview first, publish after I confirm" as your habit.
  • Media rules still apply. Instagram, TikTok and YouTube Shorts need an image or video, and YouTube Shorts takes exactly one vertical video.
  • Facebook means Pages. Personal profiles are not supported by Facebook's API.

Why this is worth two minutes

The value is not that posting is hard. It is that release posts get skipped when they need a context switch. When the agent that wrote the changelog can also publish it, the announcement goes out the same hour the code ships, in the right length for every network.

Get started

Create your account at 1social.dev/login, run claude mcp add, and ask Claude Code to announce your next release. For other clients, see the 1Social MCP page.

Frequently asked questions

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http followed by a name and the server URL. For 1Social that is claude mcp add --transport http 1social https://mcp.1social.dev/mcp. Then run /mcp inside Claude Code to sign in.

Which scope should I use for the 1Social server?

Use --scope user if you want 1Social in every project. Use project scope to share the server through .mcp.json with your team. Each teammate still signs in with their own account.

Can Claude Code post automatically when I tag a release?

No. 1Social in Claude Code acts when you ask, it does not watch your repository. For scripted posting from CI, use the 1Social HTTP API.

Can I schedule posts from Claude Code?

Yes, on the 1Social Pro plan, up to 30 days ahead. Scheduled posts also appear in the 1Social web app and other connected clients.

Does Claude Code see my social media passwords?

No. Networks are connected in 1Social through their own sign-in pages, and Claude Code signs in to 1Social with OAuth.