FeedSquad

npx add-mcp 'https://feedsquad.com/api/mcp'

Connect FeedSquad to Claude, ChatGPT, Cursor or any MCP client. Your AI drafts and schedules posts for LinkedIn, X and Threads. You approve every post before it goes out.

Support: support@feedsquad.com (how to reach us)

30

Public tools

3

Platforms

OAuth 2.1

PKCE auth

2026.10.23

Tool catalogue

Install in 60 seconds

1

Claude on the web, desktop and Cowork

Open Customize, then Connectors. Click + Add, then Add custom connector. Name it FeedSquad, paste https://feedsquad.com/api/mcp and click Continue. Click Continue again on the sign-in settings, choose Sign in now, click Add, and sign in to FeedSquad. In a chat, click +, choose Connectors and turn FeedSquad on.

On Team and Enterprise plans an owner adds FeedSquad first, under Organization settings, then Connectors. Members then find it under Customize, Connectors and click Connect.

Claude Code

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

Then type /mcp in Claude Code, select feedsquad and sign in from the browser it opens.

3

ChatGPT

ChatGPT connects to FeedSquad as an MCP connector, and you sign in once. Once FeedSquad is listed in ChatGPT’s plugin directory, add it from there. Until then, turn on Developer mode in ChatGPT’s settings and create a connector with https://feedsquad.com/api/mcp. Developer mode depends on your ChatGPT plan. On Business, only admins and owners can use it, so an admin adds FeedSquad and publishes it to the workspace. On Enterprise and Edu, an admin can turn it on for roles. OpenAI’s help center has the current rules. OpenAI renames these menus from time to time. The endpoint stays the same.

4

Cursor, Codex and other MCP clients

Add a remote MCP server that uses the HTTP transport, with the URL https://feedsquad.com/api/mcp. The client opens a browser for you to sign in. No API key is needed.

The FeedSquad plugin

The plugin bundles this MCP server with six skills that walk your AI through common jobs. It is one package for Claude and for ChatGPT.

Claude

Once FeedSquad is listed in Claude’s plugin directory, install it from there. In Claude Code you can also run /plugin install from a marketplace that lists it. Until then, connect the server as shown above.

ChatGPT

Once FeedSquad is listed in ChatGPT’s plugin directory, add it from there and sign in. Until then, add the custom connector as shown above.

• setup · Checks which social accounts are connected, then writes a first post with you.
• plan-week · Plans the coming week and fills the gaps in your calendar.
• write-campaign · Writes a campaign or launch series around one theme.
• repurpose · Turns one post, article or idea into versions for other platforms.
• clear-backlog · Archives stale drafts after a dry run and your yes.
• check-ai-tells · Checks a draft for patterns that read as machine-written.

Nothing is approved or published without your yes. The skills ask before every approval, and they publish only when you ask for a post to go out now.

What it can do

30 tools. Every error carries a recovery_hint that names the next tool to call, so agents can correct themselves.

Drafting and scheduling

• create_post · Create Post
• create_posts · Create Posts (Batch)
• update_post · Update Post
• reschedule_post · Reschedule Post
• find_next_slot · Find Next Available Slot
• confirm_post · Confirm Post
• publish_post · Publish Now
• delete_post · Delete Post
• adapt_for_platform · Adapt for Platform
• lint_post · Lint Post for Banned Patterns

Media

• set_post_image · Attach Image to Post
• upload_asset · Upload Image to Post
• set_post_carousel · Attach Image Carousel to Post
• set_post_video · Attach Video to Post

Calendar and campaigns

• get_calendar · Content Calendar
• get_calendar_health · Calendar Health
• archive_posts · Archive Posts
• create_campaign · Create Campaign
• confirm_campaign · Confirm Campaign

Search and analytics

• get_post · Get Post
• search_posts · Search Posts
• get_performance_insights · Performance Insights

Account and help

• capabilities · FeedSquad Capabilities
• connect_platform · Connect Platform
• list_accounts · List Posting Accounts
• get_usage · Usage Statistics
• get_plans · Plans
• get_help · Help Center

AI Tells Index

• list_ai_tells · List AI Tells
• get_ai_tell · Get AI Tell

Campaigns need paid Handler. create_campaign plans a dated sequence. Pass the copy in its posts, or fill the placeholders afterwards with update_post.

Built-in safeguards

The server handles three problems agents often run into, so your AI does not have to.

Cadence pre-flight

Scheduling a post on a day that already holds the platform’s daily cap is refused with cadence_conflict (LinkedIn 2, X 8, Threads 4). The day is your own calendar day, not UTC. Spacing and weekly volume never refuse.

Idempotent retries

Pass an idempotency_key on create_post or publish_post. A retry after a network drop replays the first result instead of creating a duplicate.

Recovery hints

Every error includes a recovery_hint that names the next tool to call, with arguments filled in where possible. Agents stop retrying blindly.

Rate limits

Daily caps (refused)

Posts a day per platform: LinkedIn 2, X 8, Threads 4. A schedule that would go over answers cadence_conflict, with the posts already on that day. Each LinkedIn company page has its own cap.

Spacing and weekly volume (warnings)

Recommended gap between posts: LinkedIn 4 hours, X 15 minutes, Threads 1 hour. Weekly guide: LinkedIn 10, X 50, Threads 25. These never refuse a post, and MCP clients do not receive them as warnings today. Only the daily cap reaches your AI, as cadence_conflict.

Free Handler

Up to 10 published posts a month on LinkedIn and Threads, and up to 10 active posts queued per channel. Your AI can create up to 10 drafts a day. X publishing, campaigns and media attachments need paid Handler.

Paid Handler

No monthly allowance on published posts and no queue cap. Your AI can create up to 30 drafts a day. The daily caps above still apply.

Automatic slotting is a separate ceiling. When your AI leaves out the date (create_post or create_posts) or asks find_next_slot, FeedSquad picks slots only while you have fewer than 300 dated posts that calendar month, on any plan. Ask your AI to call get_usage for your own headroom.

Troubleshooting

New tools are missing, or a tool acts on an old description

Your AI client keeps the tool list from when you connected. If a tool named in these docs or in get_help is missing, or behaves differently, refresh the client’s copy. In Claude and most clients, remove FeedSquad and add it again. In ChatGPT, open a connector you added yourself and choose Refresh. If a workspace admin published FeedSquad, ask the admin to refresh and publish it again. capabilities reports the catalogue the server runs, not the one your client cached. The current catalogue is 2026.10.23, and the MCP changelog lists what each one changed.

A tool answers scope_insufficient

The connection was approved before that permission existed. Reconnect and approve the sign-in again. Refreshing a token never adds a permission.

FeedSquad does not show up in the chat

Restart the client after adding the server. In Claude, turn FeedSquad on for the chat with the + (connectors) control.

A post was refused with cadence_conflict

That day already holds the platform’s daily cap. Ask your AI to call find_next_slot and pick another day.

Revoke a connection

In FeedSquad, open Settings, then MCP. Click Revoke next to the AI client you want to cut off.

Still stuck

Email support@feedsquad.com with the x-mcp-request-id of the call. More under Support.

Support

Email

support@feedsquad.com. A person reads every message. This covers the MCP server, the Claude and ChatGPT plugins, billing and your account.

Include the AI client you use (Claude, ChatGPT, Cursor or another), roughly when it happened, and the x-mcp-request-id from the response if you have it. With the request id we can find the exact call.

From inside FeedSquad

Signed in, open Support in the app. The assistant there answers common questions and forwards the conversation to support@feedsquad.com when a person is needed.

Who runs FeedSquad

Herman Foundry Oy, business ID 3636930-1, 99140 Kittilä, Finland.

Cookbook and reference

[

MCP Cookbook

Task-oriented recipes for agents and humans. You can load it as a system prompt.

Open cookbook

](https://feedsquad.com/mcp-cookbook.md)[

Tool reference

Every tool with its permission, plus response shapes and scopes.

Open reference

](https://feedsquad.com/mcp.md)[

MCP changelog

What changed in each tool catalogue, and when to reconnect.

Open changelog

](https://feedsquad.com/mcp-changelog.md)

Common recipes

First post (onboarding). Connect a platform, draft, schedule or publish.

Schedule a week of LinkedIn posts. Paid Handler: supply posts to create_campaign with cadence pre-flight. Omitted posts become placeholders to replace before approval.

Multi-platform adaptation. One brief becomes LinkedIn, X and Threads versions. Publishing to X needs paid Handler.

Recover from a publish failure. Inspect publishing_status, fix the cause, retry safely with idempotency.

Reschedule with cadence respect. Move a post without going over a daily cap.

Clear a draft backlog. get_calendar_health finds stale drafts. archive_posts runs a dry run first and archives after your yes.

Switch between personal and LinkedIn company page. list_accounts, pick a page, bind it with company_page_id. Each account has its own cadence.

Read the full cookbook

Pair FeedSquad with Overwride's MCP

Overwride rewrites a draft and keeps the original next to the rewrite on a public record that anyone can check. Add both MCP servers to the same assistant and keep this order, so the text you approve is the text that publishes:

1. create_post as a draft, already fitted to its platform (length, one post, not a thread).
2. overwride_rewrite with that draft's exact text.
3. update_post with the rewrite exactly as returned. Add Overwride's footer line only if you want it.
4. confirm_post when you have read it.

Any edit after the rewrite means the post no longer matches its Overwride record. On X, a post with a web address can't match, because X rewrites links. Threads splits text over 500 characters, so keep those posts shorter.

This uses your own Overwride plan: MCP needs Overwride Pro or API (not Starter). Your draft goes to Overwride, which uses xAI's model, and the original and the rewrite are public on the record.

Scopes

OAuth 2.1 with PKCE. Tokens are bound to https://feedsquad.com/api/mcp per RFC 8707.

• View your content
• Manage your drafts
• Publish to your social platforms
• Create campaigns on your behalf
• Connect new platforms
• View post performance
• View pricing & plan
• Read your brand brain
• Suggest additions to your brand brain
• Confirm who you are
• Your email address

Security

OAuth 2.1 with PKCE. Your social credentials never reach the AI provider.

Approval before publishing. A draft never goes live without an explicit confirm step.

Scoped permissions. Agents get only the scopes they need. Revoke a connection under Settings, MCP.

Request IDs. Every response includes x-mcp-request-id for support.

FAQ

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants connect to external tools. FeedSquad implements MCP so you can manage social media from your AI chat.

Do I need API keys?

No. You connect social accounts with OAuth. There is no developer app and no API key.

Is there a free tier?

Yes. Handler Free publishes up to 10 posts per month on LinkedIn and Threads and queues up to 10 active posts per channel. X publishing, campaigns and media attachments through MCP are not included in Handler Free. Plans describes what each plan includes.

Can I see what changed?

Yes. Every action runs through the same create_post → confirm_post → publish_post flow you see in your calendar. Agents can pass dry_run: true on most write tools to preview the effect first.

More answers are in the FAQ.