How to Post to LinkedIn and Instagram from Claude
A practical guide to publishing social media posts directly from Claude Desktop using MCP — and why the brand voice layer is the part that actually matters.
If you use Claude every day to draft posts, there is a strange friction in what happens next. You write a good LinkedIn post in the conversation, copy it, open another tab, paste it, check the preview, maybe tweak the spacing, and finally hit publish. Claude never sees what went out, never knows what performed, and cannot follow up.
Model Context Protocol (MCP)
•An open protocol from Anthropic that lets AI assistants like Claude connect to external tools and data sources. An MCP server exposes a set of tools — functions the AI can call — so Claude can read, write, and act in systems outside the chat.MCP closes that loop. It lets Claude actually do the work, not just write the words. This piece walks through the three real options for posting to LinkedIn and Instagram from Claude, and where each one fits.
Option 1: A raw platform MCP server
The open-source world already has LinkedIn and Instagram MCP servers. You can install jlbadano/ig-mcp or stickerdaniel/linkedin-mcp-server into Claude Desktop, generate API tokens yourself, and get a working publish_post tool.
This route is fine if you are a developer, you only care about one platform, and you are happy managing OAuth tokens and refresh flows on your own machine. It breaks down fast once you want anything else — brand consistency, scheduling, images, analytics. Those servers do one thing: they post.
Option 2: An aggregator like Zapier MCP or Composio
Aggregators solve the platform sprawl problem. Zapier MCP, Composio, and Pipedream MCP each expose hundreds of services — including LinkedIn and Instagram — behind a single hosted endpoint. You paste one URL into Claude Desktop, OAuth through a browser popup, and Claude gains access to a library of post tools.
This is a good choice for developers building agent workflows across many apps. It is a poor choice for anyone who wants a brand to come out the other side. The tools are generic. Claude sees a function called linkedin_create_post(text, image_url) and nothing about who you are. Every conversation starts at zero.
Option 3: A brand-aware publishing MCP
The third option — and the one we built Rheos for — is a publishing MCP that ships your brand context alongside the tools.
Why brand context matters more than the publish tool
The publish call is the easy part. Every MCP server can post to LinkedIn. What changes the output is what Claude knows before it drafts: your tone, your pillars, your audience, what worked last month, what you never say. That context is what turns a generic LLM post into something your customers recognise as yours.
Rheos MCP exposes six tools to Claude:
get_brand_voice— returns your brand voice profile, content pillars, and audience context.draft_post— generates an on-brand post for a given platform and intent.generate_image— produces a brand-consistent image using your visual identity.schedule_post— queues a post for a specific publish time.publish_post— publishes immediately to LinkedIn or Instagram.get_post_analytics— pulls engagement, reach, and click metrics for published posts.
The practical effect: you say "draft me three LinkedIn posts for this week on the sustainability pillar, then schedule them" and Claude does it in your voice, queues them, and reports the publish times back in the chat. No copy-paste, no second tab.
How to set it up
Three steps, once:
- Install the Rheos MCP server by dropping the config snippet into Claude Desktop's
claude_desktop_config.json. - Generate an API key in the Rheos dashboard under Settings → Integrations → MCP.
- Connect your LinkedIn and Instagram accounts in the Rheos dashboard.
From that point on, every Claude conversation has access to your brand and your publishing pipe. You can treat Claude as a marketing collaborator who remembers — because the memory lives in Rheos, not in the chat window.
Which option should you pick?
If you are a developer building something custom, the raw servers or aggregators are the right shape — they are plumbing, and plumbing is what you want. If you run a business and you want Claude to help you actually post, not just draft, you want a layer that knows your brand. That is the category Rheos is in, and it is still largely empty.
Summary
Three paths exist for publishing social media from Claude: raw open-source MCP servers for developers, aggregators like Zapier and Composio for generic automation, and brand-aware platforms like Rheos for businesses that want the output to sound like them. The difference is not the publish call — every option can post. The difference is whether Claude knows who is posting.
Rheos Intelligence
AI-powered insights from the Rheos research team.
Related Articles
Best AI Social Media Tool for Small Business UK: Pricing, Free Plans, and Ease of Use Compared
An honest comparison of Rheos, Buffer, Later, and Metricool for UK small businesses. Pricing, free plans, AI features, and what actually matters if you're running the business yourself.
How to Maintain Brand Consistency Across Social Media Platforms
A practical guide for small businesses: what brand consistency actually means across Instagram, LinkedIn, Facebook, and X, why it matters, and the specific rules to follow so your brand looks like one brand on every platform.
Visual Content Calendar for Social Media: Drag-and-Drop Scheduling and Team Collaboration
How a drag-and-drop content calendar changes the way small teams plan, schedule, and publish social media. A practical guide to Rheos' visual calendar and team workflow.