Post to LinkedIn (and X, and Threads) from ChatGPT
Connect ChatGPT to FeedSquad and it can draft, schedule, and publish to LinkedIn, X, and Threads — inside the chat. No LinkedIn developer app, no API keys, no tokens to babysit. You approve every post before it goes live.
This is the ChatGPT guide. The FeedSquad connector speaks the Model Context Protocol, so the same server also works in Claude, Cursor, and any MCP client — that full list lives on /mcp. Here we stay on ChatGPT: how you connect it, what you type, and where you stay in control.
Connect ChatGPT to FeedSquad
ChatGPT connects to FeedSquad as an MCP connector, and you sign in once. OpenAI renames its settings from time to time, so the labels on your screen may differ. The endpoint stays the same.
The FeedSquad MCP endpoint (paste this):
https://feedsquad.com/api/mcp- 01
Find FeedSquad in ChatGPT
Once FeedSquad is listed in ChatGPT's plugin directory, add it from there and go to the sign-in step. Until then, use a custom connector.
- 02
Add FeedSquad as a custom connector
Turn on Developer mode in ChatGPT's settings, then create a connector and paste the FeedSquad endpoint above. 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.
- 03
Authorize once in your browser
ChatGPT hands you off to FeedSquad's OAuth screen. Sign in, approve the scopes, and you land back in the chat. FeedSquad holds your LinkedIn, X, and Threads tokens — they never reach ChatGPT.
- 04
Say hello
Ask ChatGPT to run an account health review on FeedSquad. It is read-only, so nothing can go wrong on the first try — and it confirms the connection is live.
Stuck, or the menu looks different? OpenAI moves these settings from time to time. The endpoint stays https://feedsquad.com/api/mcp, and the docs keep the current walkthrough.
Open the MCP docs →What you actually type
You write plain English. ChatGPT calls the FeedSquad tool behind each request. Lead with the read-only ones — nothing to undo.
Run an account health review on FeedSquad.get_calendar_health·Read-only. Shows your gaps and cadence before you touch anything.
Connect my LinkedIn account.connect_platform·Opens the OAuth link in the chat. Same for X and Threads.
Turn these three bullet points into a LinkedIn post and schedule it for Tuesday morning.create_post·Arrives as a draft with a suggested slot — publishing waits for your confirm.
Adapt that post for X and Threads.adapt_for_platform·Rewrites for each platform instead of cross-posting the same text.
Build a 4-week LinkedIn campaign on the launch.create_campaign·Plans the dated sequence. Pass the copy in, or fill the placeholders afterwards. Campaigns need paid Handler.
Approve the Tuesday post.confirm_post·This is the step that commits a draft. Publishing only happens after you say so.
You approve every post
The connector is built create → confirm → publish, on purpose. A request to write a post never publishes on its own.
Drafts, not surprises
create_post makes a draft. It sits on your calendar until you run confirm_post to approve it. Delete it, edit it, or leave it — your call.
Drafts until you approve
Depending on your ChatGPT settings, ChatGPT may ask before it runs a tool that changes something, or remember your answer. Either way, a post FeedSquad creates stays a draft until you approve it.
Your credentials stay with FeedSquad
OAuth 2.1 with PKCE. Your LinkedIn, X, and Threads tokens live in FeedSquad and are never shared with ChatGPT. Every response carries an x-mcp-request-id you can trace.
Revoke anytime
Permissions are scoped to what you approve. Pull any connected platform from Settings → Connections whenever you want.
How this compares
Two honest comparisons, because both alternatives are real and one of them ships an MCP too.
Taplio's LinkedIn MCP
Taplio ships its own MCP at mcp.taplio.com. Per Taplio's own page it covers research, drafting, scheduling, publishing with your confirmation, analytics, comments, and image and video attachments. It is LinkedIn-only. If LinkedIn is your only channel and you already pay for Taplio, its MCP is a clean fit.
Where FeedSquad differsFeedSquad differs on breadth. One connector covers LinkedIn, X and Threads. It plans multi-week campaigns and keeps one shared calendar. In clients that render MCP widgets, it returns interactive preview cards instead of plain text.
Open-source LinkedIn MCPs
The LinkedIn MCP servers on GitHub are genuinely useful developer tools. If you are comfortable registering a LinkedIn developer app and managing OAuth tokens yourself, they get you posting from a single platform for free.
Where FeedSquad differsFeedSquad manages the platform OAuth for you — no developer app, no API keys, no token refresh to maintain — and pairs a content calendar with interactive widgets in clients that render them. And it is three platforms, not one.
Start on the free plan
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 media attachments through MCP. Publishing cadence still applies. No credit card required.
Want weekly LinkedIn campaigns written in your voice? Ghost is €39/month and includes Handler.
Frequently asked questions
ChatGPT setup follows OpenAI's developer documentation. OpenAI moves these settings from time to time, so the steps name the endpoint rather than every menu, and /docs/mcp keeps the current walkthrough. Taplio's LinkedIn MCP is LinkedIn-only per taplio.com/taplio-linkedin-mcp. FeedSquad capability claims map to shipped MCP tools in our own registry. Prices come from our pricing config. Spot something out of date? support@feedsquad.com.
Handler · Social Scheduler
Post to LinkedIn from ChatGPT.
Free to start. The connector takes minutes.
Start with one real job. FeedSquad shows you the finished work before anything publishes, and you keep the final say.
Get started free →