FeedSquad for Claude

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.

Start free →Read the docs

Using Claude Code? Add it in one line:

claude mcp add --transport http feedsquad https://feedsquad.com/api/mcp

What 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_campaignPlans the dated sequence. Pass the copy in, or fill the placeholders afterwards. Campaigns need paid Handler.

“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 31 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/mcp

Claude app (web and desktop)

Add it once in your connector settings:

  1. 1Open Customize, then Connectors.
  2. 2Click + Add, then Add custom connector.
  3. 3Name it FeedSquad, paste the endpoint above and click Continue.
  4. 4Click Continue on the sign-in settings, choose Sign in now and click Add.
  5. 5Sign in to FeedSquad in the browser.
  6. 6In a chat, click +, choose Connectors and turn FeedSquad on.

On the free plan you can add one custom connector. On Team and Enterprise plans an owner adds FeedSquad first, under Organization settings, Connectors. Members then click Connect on it under Customize, Connectors.

FeedSquad shows up under Connectors in the + menu of the chat.

Claude Code

One command, then sign in from /mcp:

claude mcp add --transport http feedsquad https://feedsquad.com/api/mcp
  1. 1Run the command above.
  2. 2In Claude Code, type /mcp and select feedsquad.
  3. 3Sign in to FeedSquad in the browser it opens.

/mcp shows feedsquad as connected.

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.

Claude sometimes renames these settings. The endpoint stays the same.

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

Ask Claude to prepare the post, then read and approve it. Creating a draft or choosing a date does not publish it.

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

Read the draft, make any changes and approve it with confirm_post. Until then, it stays a draft.

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 plans the dated sequence. Pass the copy in its posts, or fill the placeholders afterwards with update_post. confirm_campaign approves the campaign. You can approve, edit or cancel each post.

How this differs from the other Claude MCPs

Already use a LinkedIn tool with Claude? Check which accounts it reaches, how it handles media and what you approve before a post goes out.

Taplio LinkedIn MCP

Taplio’s MCP covers LinkedIn research, drafts, schedules, analytics, comments and image or video attachments. Its page says publishing needs your confirmation. We reviewed taplio.com/taplio-linkedin-mcp on November 3, 2026; we did not test a connected account.

It focuses on LinkedIn. Check the media format you need and read the saved post before approving it.

Open-source LinkedIn MCPs

Start with the project’s own tool list. Some help with research, some publish through an API and some use a browser session. Check how it connects and what you will need to maintain.

Look for the features you need: supported accounts, media, a calendar and a clear approval step. They vary by project.

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

If you only need LinkedIn, Taplio or a suitable open-source project may be enough. FeedSquad brings LinkedIn, X and Threads into one calendar, with a separate step to approve the posts. Try the tasks you do each week before switching.

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 more

LinkedIn MCP

Campaigns of 1 to 12 weeks and official-API publishing to LinkedIn.

Read more

X / Twitter MCP

Native posts and threads on X, no reposts.

Read more

Threads MCP

On-brand Threads posts adapted from your campaigns.

Read more

MCP documentation

Tools reference, scopes, rate limits, and troubleshooting.

Read more

Frequently asked questions

Custom connectors work on Claude Free, Pro, Max, Team, and Enterprise. Free accounts can add one custom connector. On Team or Enterprise, an org owner adds FeedSquad before members can connect it. Claude sometimes renames these settings, so match what your version shows.
No. FeedSquad handles the platform APIs. You connect your LinkedIn, X, or Threads account with OAuth from inside the chat — no developer app, no API keys, no client secrets.
Yes. Run claude mcp add --transport http feedsquad https://feedsquad.com/api/mcp, then type /mcp in Claude Code, select feedsquad and sign in. Same account and same tools as the app.
No. create_post saves a draft, even if it has a date. Read it, make any changes and use confirm_post when you are ready to approve publication.
LinkedIn, X/Twitter, and Threads. One draft can be adapted for all three with adapt_for_platform.
Yes. Free Handler publishes up to 10 posts a month on LinkedIn and Threads and queues up to 10 active posts per channel. X publishing requires paid Handler, and so do campaign creation and MCP media attachments. Add Ghost (€39/mo) for dashboard AI campaign generation. Publishing cadence still applies.

Handler · Social Scheduler

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 →