/Docs

MCP Server

Connect FeedSquad to Claude, ChatGPT, Cursor, or any MCP-compatible AI client. Post to LinkedIn, X, and Threads from chat — with OAuth, scheduling, cadence enforcement, and per-platform adaptation.

Public tools

Platforms

OAuth 2.1

PKCE auth

60 s

To install

Install in 60 seconds

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "feedsquad": {
      "url": "https://feedsquad.com/api/mcp"
    }
  }
}

Claude Code / Cowork

claude mcp add feedsquad https://feedsquad.com/api/mcp

ChatGPT

Settings → Connected Apps → search FeedSquad → Connect.

Cursor & other MCP clients

Any client that supports the MCP HTTP transport. Point it at https://feedsquad.com/api/mcp.

What it can do

Twenty tools, grouped into four areas. Every tool returns structured responses with recovery_hint fields on errors so agents can self-correct.

Drafting & scheduling

create_post · idempotent drafts with optional scheduling
update_post · reschedule_post · delete_post
set_post_image · attach validated HTTPS images
confirm_post · publish_post · idempotent publish path

Campaigns

create_campaign · batch cadence pre-flight, no silent breaches
confirm_campaign · approve all in one call
adapt_for_platform · LinkedIn ↔ X ↔ Threads adaptation

Discovery & analytics

get_calendar · filter by platform, status, date
get_calendar_health · gaps, clusters, cadence drift
get_post · search_posts
get_performance_insights · metrics + AI summary

Account & billing

connect_platform · OAuth to LinkedIn / X / Threads
list_accounts · personal + LinkedIn company pages
get_usage · get_plans · get_help

Built-in safeguards

Three problems agents typically run into are solved at the server layer — so the LLM doesn’t have to.

Cadence pre-flight

Per-platform daily / weekly caps + minimum spacing are enforced when scheduling, not at publish time. Timezone-aware so a Tokyo founder doesn’t silently bypass the cap by straddling UTC midnight.

Idempotent retries

Pass an idempotency_key on create_post or publish_post. Retries after a network drop replay the original row instead of creating duplicates.

Recovery hints

Every error response includes a recovery_hint pointing at the next tool to call (with pre-filled args where possible) — so agents stop retrying blindly.

Cookbook & reference

MCP Cookbook

Eight task-oriented recipes for agents and humans. Loadable as an LLM system prompt.

Open cookbook

Tool reference

Per-tool parameter reference, scopes, response shapes, and OAuth scope tables.

Open reference

Common recipes

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

Schedule a week of LinkedIn posts — Batch via create_campaign with cadence-aware pre-flight.

Multi-platform adaptation — One brief → LinkedIn + X + Threads, per-platform voice.

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

Reschedule with cadence respect — Move a post without breaching daily caps or spacing.

Switch between personal and LinkedIn company page — list_accounts → pick page → bind via company_page_id. Independent cadence per account.

Read the full cookbook

Scopes

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

posts:readposts:writeposts:publishcampaigns:writeconnections:writeanalytics:readbilling:read

Security

OAuth 2.1 with PKCE — credentials never reach the AI provider.

Approval-gated publish — drafts never go live without an explicit confirm step.

Scoped permissions — agents only get the scopes they need; revoke from Settings.

Request IDs — every response includes x-mcp-request-id for support correlation.

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. FeedSquad handles all platform integration. You connect social accounts via OAuth — no developer app, no API keys.

Is there a free tier?

Yes. Handler Free gives you 10 posts per month with the calendar and campaign tracking. See pricing for upgrade options.

Can I see what changed?

Yes. Every action runs through the same create_post → confirm_post → publish_post flow visible in your calendar. Agents can use dry_run: true on most write tools to preview the effect without committing.

Ready to connect?

Free to start — install in your AI client of choice, sign in with FeedSquad, and post.

Get started free Read the cookbook