Posting to LinkedIn from Claude CLI Using WoopSocial MCP

What WoopSocial Is

WoopSocial is a social media management tool that also exposes an MCP (Model Context Protocol) server. That means it slots into Claude Code CLI the same way any other MCP server does — Supabase, GitHub, filesystem. You register it, restart Claude, and a set of tools appear in context.

The core value here isn't the social media scheduling features themselves — it's the MCP surface. Being able to tell Claude "draft a LinkedIn post about the WoopSocial setup I just wrote about and publish it to both my personal profile and Webfluentia" and have it actually execute that is what I'm after.

The Setup

Setup was about as frictionless as it gets. WoopSocial generates a personal MCP URL with your API key embedded. You paste that URL into your Claude MCP config as an HTTP-type server, and that's it.

1. Create a WoopSocial account and connect your LinkedIn accounts (personal and/or business pages)
2. Go to your WoopSocial settings and copy your MCP server URL
3. Add it to your ~/.claude.json MCP config as an HTTP server entry
4. Restart Claude Code CLI
5. WoopSocial tools appear in context — done

The config entry looks roughly like this:

One note on security: the MCP URL contains your API key inline, which is the same pattern as some other HTTP-type MCP servers. Make sure that config file has restricted permissions and is not checked into version control.

What It Recognized Immediately

Once connected, WoopSocial instantly surfaced all the LinkedIn accounts I had already linked in my WoopSocial dashboard — my personal profile and the Webfluentia business page. No additional auth steps, no re-linking. It just knew.

The MCP tools it exposes cover what you'd expect: listing connected social accounts, creating and scheduling posts, managing uploads. For my use case — writing a post and publishing it — the relevant tools are listSocialAccounts to confirm which accounts are available, and createPost to publish. There's also post validation, upload sessions for media, and webhook endpoints if you want to build something more automated.

What This Actually Looks Like in Practice

Here's a realistic example of how I'd use this. Say I just merged a feature or published a blog post. Instead of opening LinkedIn, writing something, picking the right account, and posting — I stay in my Claude session and say something like:

Write a short LinkedIn post announcing my new blog post about WoopSocial MCP. Keep it conversational, under 200 words, no hashtag spam. Post it to my personal profile.

— My prompt to Claude

Claude drafts the post, I review it in the terminal, confirm, and it publishes. The whole thing happens without me switching context. That's the point — not that Claude can post to LinkedIn, but that posting to LinkedIn no longer requires breaking my flow.

The Free Plan Is Genuinely Usable

WoopSocial offers a free plan that's generous enough to actually test the workflow before committing. I started on the free tier and it covers connecting multiple accounts and using the MCP integration. If you're already paying for social scheduling tools, this could replace one of them. If you're not, the free tier is a reasonable starting point.

I'm not affiliated with WoopSocial — I just tried it, it worked well, and I'm sharing that. The MCP integration is what made it interesting to me specifically. As a tool for developers who already live in Claude Code CLI, it's a good fit.

Where This Fits in an Agentic Workflow

I've been progressively wiring more things into my Claude setup: filesystem access, Supabase, GitHub, Google Ads via AdLoop, and now social posting via WoopSocial. The goal isn't to make Claude do everything autonomously — it's to reduce the number of context switches in a given work session.

Every time I leave the terminal to do something in a browser, I lose a small amount of flow. Some of those interruptions are unavoidable. But posting to LinkedIn after shipping something? That one I can now keep inside the same session. That's a worthwhile quality-of-life improvement.

If you're already using Claude Code and you want to experiment with this, WoopSocial is worth a look. The free plan is enough to validate whether it fits your workflow before spending anything.