Run your social media from Claude
Connect FeedSquad once and Claude can draft, schedule, and publish to LinkedIn, X, and Threads without leaving the chat. No API keys. No LinkedIn developer app. You approve every post before it goes live.
Claude proposes, you approve. Every post lands as a draft first — nothing publishes until you say so.
Using Claude Code? Add it in one line:
claude mcp add --transport http feedsquad https://feedsquad.com/api/mcpWhat you can do from a Claude chat
Type it the way you would say it. Claude maps the request to a FeedSquad tool and shows you the result before anything ships.
“Draft a LinkedIn post about our new pricing and show me the slot you would give it.”
create_postLands as a draft on a proposed slot. Nothing publishes yet.“Adapt that draft for X and Threads.”
adapt_for_platformOne idea, three platform-native versions. You keep the ones you want.“Plan a six-week launch campaign, three posts a week.”
create_campaignA full sequence of drafts you approve in one pass.“Find three LinkedIn slots next Tuesday afternoon.”
find_next_slotPlanning only. Respects daily caps and spacing — no write.“What is my posting gap this week?”
get_calendar_healthRead-only. Flags clusters, gaps, and stale drafts.“Publish the approved one now.”
publish_postImmediate publish — only after you have approved the draft.Six of 29 tools the connector exposes.
Connect FeedSquad to Claude
One remote MCP endpoint, one browser authorization. The endpoint is the same in the app and in Claude Code:
https://feedsquad.com/api/mcpClaude app (web and desktop)
Add it once in your connector settings:
- 1Open Settings → Connectors.
- 2Click Add custom connector.
- 3Paste the endpoint above and click Add.
- 4Authorize FeedSquad in the browser when prompted — once.
- 5Enable FeedSquad for a chat with the + (connectors) control in the message bar.
On the free plan you can add one custom connector. On Team or Enterprise, an org owner adds FeedSquad before members can connect it.
FeedSquad shows up in the + (connectors) menu for the current chat.
Claude Code
One command, then authorize on first use:
claude mcp add --transport http feedsquad https://feedsquad.com/api/mcp- 1Run the command above.
- 2On your first FeedSquad request, Claude Code opens the browser for OAuth.
- 3Authorize once.
Confirm it with /mcp inside a session.
FeedSquad manages the LinkedIn, X, and Threads OAuth for you. Your social credentials never reach Anthropic — the connector authenticates with OAuth 2.1 and PKCE, and you connect each account with connect_platform from inside the chat. No API keys, no developer app.
Connector steps reflect Claude’s settings as of July 2026.
Try your first command
Start with the read-only one. Nothing to undo.
Run an account health review on FeedSquad.Read-only. Shows the calendar intelligence, nothing to undo.
What is my posting gap this week?Draft a LinkedIn post about [topic] and lint it before scheduling.Claude writes it; FeedSquad flags AI-slop patterns before you schedule it.
What Claude cannot do without you
The connector is built so an over-confident agent cannot publish on your behalf. The gate is the product, not a switch you can forget to turn on.
Drafts, not posts
create_post makes a draft. It never goes live on its own — even when it carries a scheduled date.
Approval is a separate step
You approve with confirm_post before anything publishes. The two-step draft → confirm lifecycle is intentional.
Scoped permissions
Each tool asks for the narrow scope it needs — posting, publishing, connections. Revoke access anytime from Settings.
No training on your content
Your posts and data are never used to train AI models. Every response carries an x-mcp-request-id you can trace.
Same rule for campaigns: create_campaign drafts the whole sequence, confirm_campaign approves it. Approve, edit, or cancel per post.
How this differs from the other Claude MCPs
There are real LinkedIn MCP servers for Claude already, and some are good. The honest split is about scope.
Taplio LinkedIn MCP
Taplio ships a working LinkedIn MCP — research, draft, edit, schedule, publish, and analytics, all from Claude. If LinkedIn is the only place you post and you already pay for Taplio, it does the job.
It is LinkedIn-only and text-only — no media or PDF upload, per Taplio’s own page.
Open-source LinkedIn MCPs
The servers on GitHub are free and hackable. If you like registering a LinkedIn developer app and managing your own tokens, they are a fair weekend project.
One platform, manual OAuth, text-only responses, and no calendar or campaign layer.
FeedSquad
- LinkedIn, X, and Threads from one connector
- Campaigns and a shared content calendar, not post-by-post
- Managed OAuth — no developer app, no token juggling
- Interactive post, calendar, and campaign cards inside Claude
- Image upload with set_post_image and upload_asset
- A slop check (lint_post) that flags the worst AI tells before you schedule
Post to one platform in plain text and an open-source server or Taplio may be all you need. Run more than one channel and think in campaigns, and that is the gap FeedSquad fills.
Keep going
Posting to LinkedIn from Claude: how the MCP integration actually works
The Claude-to-LinkedIn flow under the hood, minus the marketing layer.
Read moreLinkedIn MCP
8-week campaigns and official-API publishing to LinkedIn.
Read moreX / Twitter MCP
Native posts and threads on X, no reposts.
Read moreThreads MCP
On-brand Threads posts adapted from your campaigns.
Read moreMCP documentation
Tools reference, scopes, rate limits, and troubleshooting.
Read moreFrequently asked questions
Handler · Campaign Manager
Run your social media from Claude.
Free plan. No credit card.
Start with one real job. FeedSquad shows you the finished work before anything publishes, and you keep the final say.
Start free →