LinkedIn MCP · checked Nov 20, 2026
LinkedIn MCP: what's official, what can post
LinkedIn's only official MCP, Hiring Pro, posts jobs. Servers on LinkedIn's API can post as you, and post to company pages only once LinkedIn approves their app.
Set up Gin for this project.
Read and follow https://trygin.ai/setup.md
My one-time code: GIN-XXXX-XXXXGet your one-time code from "Add Gin to your agent" in the app; it works once, for 10 minutes. Or run npx @winding-labs/gin setup. Your agent drafts, you swipe to post. We make Gin. Compare every option.
Hiring Pro is LinkedIn's own connector in Claude's directory: it drafts one free job post, never a feed post. Posting as you uses the self-serve Share on LinkedIn permission; posting as a company page needs LinkedIn's Community Management review. Servers that drive your logged-in browser break section 8.2 of LinkedIn's User Agreement and put your account at risk.
Sample data
Every LinkedIn MCP option, compared
What each one is, how it reaches LinkedIn, and what it can post, read from each listing, README and LinkedIn's docs on November 20, 2026. We make Gin, one of the options here, so weigh that. We didn't test the other servers; every claim links to its source below.
| Option | Who makes it | How it reaches LinkedIn | Posts to | Can it post? | Account risk |
|---|---|---|---|---|---|
| LinkedIn Hiring Pro (Claude connector) | LinkedIn (official) | Remote MCP at mcp.linkedin.com, LinkedIn sign-in, job-posting scope only | Jobs, not the feed | One free job, after you press "Agree and post" | None |
| Zapier MCP (Claude connector) | Third party | Zapier's own LinkedIn connection (official API) | Profile and company page | Yes: Create Share Update, Create Company Update | Low |
| Typefully, Taplio (Claude connectors) | Third party | Each app's own LinkedIn connection | Profile; pages vary by app | Drafts and schedules posts | Low |
| Self-hosted, Share on LinkedIn (souravdasbiswas, fredericbarthelet) | Open source | Official API through your own LinkedIn app (w_member_social) | Your profile | Yes, live the moment the call succeeds | Low |
| Self-hosted, Community Management API | You | Official API; your app must pass LinkedIn's review | Company page | Yes, after approval, for registered companies only | Low |
| Browser-session servers (stickerdaniel, eliasbiondo) | Open source | Drives a Chromium browser with your LinkedIn session | Your account | No post tool; stickerdaniel sends messages and invites after you confirm | High |
| Hosted browser services (Linked API, gtm-api) | Third party | A cloud browser signed in as you | Your account | Messages, invites and search | High |
| Gin (we make it) | Winding AI | Official API for your profile; pages by copy and open | Profile; a page after you press Post | Only after a person swipes right | Low |
Checked 2026-11-20.
Risk means risk to your LinkedIn account under LinkedIn's rules, not code quality. "Low" still means a token on disk that can post as you.
Open-source LinkedIn MCP servers on GitHub
The pattern is plain. The most-starred servers read profiles, inboxes and feeds, which no open LinkedIn permission covers, so they run your logged-in browser. The servers on the official API can post as you and little else. None of the servers we read posts as a company page.
| Repository | Stars | Last commit | How it works | Posts? |
|---|---|---|---|---|
| stickerdaniel/linkedin-mcp-server | 4,262 | Nov 20, 2026 | Patchright browser that reuses or imports your LinkedIn cookies | No; 25 tools including inbox, send_message, connect_with_person |
| eliasbiondo/linkedin-mcp-server | 221 | Oct 24, 2026 | Patchright browser with a saved login | No; profiles, companies, jobs |
| Linked-API/linkedapi-mcp | 69 | Nov 19, 2026 | Hosted cloud browser | Messages, search, profiles |
| gtm-api/linkedin-mcp | 61 | Nov 19, 2026 | Hosted anti-detect cloud browser with its own proxy | Search, invites, messages |
| Dishant27/linkedin-mcp-server | 53 | Oct 16, 2026 | Official API; its README warns people search calls an undocumented endpoint | No |
| fredericbarthelet/linkedin-mcp-server | 41 | Mar 19, 2025 | Official API (w_member_social), MCP draft auth flow | Yes, as you; not as a page |
| souravdasbiswas/linkedin-mcp-server | 20 | Mar 23, 2026 | Official API through your own app, OAuth | Yes, as you, plus comments and reactions |
Checked 2026-11-20.
The most-starred one, stickerdaniel's, drives your logged-in browser, which section 8.2 of LinkedIn's User Agreement bans; its own FAQ says accounts using automated tools "can be restricted or banned". The official MCP Registry lists 79 servers matching "linkedin", and none is published under LinkedIn's namespace. If you only need a post as a company page from an agent, Zapier's MCP is the plainest route today.
Set up a LinkedIn MCP in Claude Code, Cursor or Codex
Pick an option from the table, then add it to your agent. Three shapes cover them all: Gin's setup, a remote server you sign in to, and a local server you run. The syntax is from the Claude Code, Cursor and Codex MCP docs.
Claude Code
- Gin. Paste the setup prompt above. Claude runs
npx @winding-labs/gin setupwith your code, asks you to confirm the account, then adds Gin's plugin: hooks, a skill and theginMCP server, which runs locally over stdio. To add the server by hand after setup:Terminalclaude mcp add gin -- ~/.gin/bin/gin mcp - A remote server with sign-in (Typefully shown). Then type
/mcpin Claude Code and sign in in your browser. Add--scope userto load it in every project.Terminalclaude mcp add --transport http typefully https://mcp.typefully.com/mcp - A local server on the official API (souravdasbiswas shown). You need your own LinkedIn app with Sign In with LinkedIn and Share on LinkedIn.
Terminal
claude mcp add linkedin \ -e LINKEDIN_CLIENT_ID=your_client_id \ -e LINKEDIN_CLIENT_SECRET=your_client_secret \ -- node /path/to/linkedin-mcp-server/dist/index.js
Cursor
Paste the same prompt into Cursor's agent. Setup prints the lines to add to ~/.cursor/mcp.json (use your full home path). A remote server takes a url instead, and Cursor runs its sign-in when the server asks.
{ "mcpServers": {
"gin": { "command": "/Users/you/.gin/bin/gin", "args": ["mcp"] },
"typefully": { "url": "https://mcp.typefully.com/mcp" }
} }Codex
Paste the same prompt into Codex. Setup adds Gin's plugin (skill, hook, MCP); Codex runs plugin hooks only once trusted, so type /hooks and trust Gin's. By hand, or for a remote server:
codex mcp add gin -- ~/.gin/bin/gin mcp
codex mcp add typefully --url https://mcp.typefully.com/mcp
codex mcp login typefullyA working example: from a merged PR to a LinkedIn draft
Restart your agent so the new tools load, then ask it to tell Gin what shipped. Gin's MCP answers with what it did, and the draft lands in your deck.
you › Tell Gin what we shipped in PR #2203.
claude › calls gin · send_message
text: "Zest now emails a three-line standup of what your
agents did overnight, every morning at 6."
url: https://github.com/…/pull/2203
gin › Gin is routing it; drafts show up in the Gin app to swipe.The last line is Gin's real reply text. The product and PR are sample data. Our Claude Code marketing guide shows what the session hook sends, and what it never sends.
What LinkedIn's API allows, and what needs a browser
An MCP server is a thin layer over an API, so the real question is which LinkedIn permissions its app holds. LinkedIn says most permissions need its approval. Only three are open to every developer.
| The agent wants to | Permission | Who can get it |
|---|---|---|
| Read your name, photo, email | profile, email | Any developer, self-serve |
| Post, comment and like as you | w_member_social (Share on LinkedIn) | Any developer, self-serve |
| Read your own posts back | r_member_social | Closed: "not accepting access requests" (FAQ) |
| Post as a company page | w_organization_social (Community Management API) | Registered organizations, after review |
| Read messages, the feed, other profiles | No open permission | Partners only, or nobody |
Checked 2026-11-20.
Three limits that shape every API server
- No drafts, no scheduling. The Posts API accepts only
PUBLISHEDwhen a post is created. The call is the post. - 150 calls a day per member on Share on LinkedIn, and 100,000 per app.
- Company pages need paperwork. A verified business email, the company's legal details and privacy policy, a page super admin's approval, and a screen recording for the standard tier (app review). You also need the administrator, content admin or sponsored content poster role on the page.
If you'd rather start from your release notes than an API call, the LinkedIn post generator drafts the text in your browser.
Browser automation and LinkedIn's rules
Section 8.2 of LinkedIn's User Agreement (effective November 3, 2025) says you will not use "bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts". It also bans software that scrapes "profiles and other data".
LinkedIn's help page on prohibited software says members who use such tools "risk having their accounts restricted or shut down". Two more things to weigh:
- Your session is a password. A browser server keeps your LinkedIn cookies on disk. Anything that reads that folder can act as you.
- Your agent reads strangers' text. Issues, READMEs and web pages can carry instructions. A tool that sends messages gives that text a way to try. Choose tools that need a person to approve.
Twitter MCP: posting to X from an agent
X is the other half of a builder's feed, and it runs its own MCP server. The hosted one at api.x.com/mcp connects through the xurl bridge and your own X developer app. Its docs list post reads, search, users, bookmarks, trends and Articles. To create posts from an agent, X's open-source xdevplatform/xmcp turns the whole X API into tools; X_API_TOOL_ALLOWLIST limits which ones load.
X charges per call: $0.015 a post, $0.20 a post with a link, with no subscription. X's developer guidelines say non-API automation, meaning scraping or browser automation, "results in permanent suspension".
Gin: your agent drafts, a person posts
Every API server above shares one gap: the call publishes at once, so whatever wraps it decides who approves. Gin answers that with a person. Your coding agent tells Gin what shipped, Gin writes a post for each channel that fits, and you swipe right to post, left to pass, or hold to remix.
- Posts:
send_message,draft_post,remix_post,list_deck - Setup:
gin_status,add_product,add_channel,connect - Results:
get_results,suggest_boost
Keys can't publish. An agent key can send messages, draft and remix. It can never post, swipe, turn on autopilot, start a boost or touch billing; those need a person signed in to Gin. If a poisoned README talks your agent into draft_post, the worst case is a card you swipe left.
On LinkedIn, Gin posts to your profile through the official API. For company pages, Gin copies the text and opens the composer, and you press Post. Keys die after 90 days unused. If you only want a scheduler for posts you write, our Buffer alternatives page compares them.
Questions
Is there an official LinkedIn MCP server?
Yes, one. LinkedIn Hiring Pro is in Claude's connector directory, made by LinkedIn and Anthropic verified, added October 2026. It drafts and posts one free job after you press "Agree and post". It doesn't write feed posts, read messages or manage company pages. Every other LinkedIn MCP server is a third-party project.
Can a LinkedIn MCP server post to a company page?
Only through an app with LinkedIn's Community Management API, which LinkedIn grants to registered organizations after review, and only if you're an administrator or content admin of the page. Zapier's MCP has a Create Company Update action. The open-source servers we read post as you, not as a page.
Will a LinkedIn MCP server get my account banned?
Servers on LinkedIn's official API are allowed. Servers that drive your logged-in browser or reuse your cookies break section 8.2 of the User Agreement, and LinkedIn says accounts using such tools risk being restricted or shut down.
Can an MCP server read my LinkedIn messages or feed?
Not through any permission LinkedIn opens to developers. Servers that read your inbox or feed do it through your browser session, which LinkedIn prohibits.
Can the LinkedIn API save drafts or schedule posts?
No. The Posts API accepts only PUBLISHED when a post is created, so it goes live the moment the call succeeds. Drafts and scheduling live in the tool, not in LinkedIn.
How do I add Gin's MCP to Claude Code, Cursor or Codex?
Sign in to Gin, copy your one-time code from "Add Gin to your agent", and paste the setup prompt into your agent, or run npx @winding-labs/gin setup. It adds the gin server for Claude Code and Codex and prints the config for Cursor. Agent keys can draft and remix but never publish.
Related guides
Sources
Checked November 20, 2026. Prices and limits change; each link goes to the page we read.
- Claude directory: LinkedIn Hiring Pro
- LinkedIn: Hiring Pro
- Claude directory: Zapier
- Zapier: LinkedIn actions
- Claude directory: Typefully
- Typefully MCP docs
- Claude directory: Taplio
- MCP Registry: search "linkedin"
- LinkedIn: Getting access to LinkedIn APIs
- LinkedIn: Share on LinkedIn
- LinkedIn: Posts API
- LinkedIn: Community Management overview
- LinkedIn: Community Management app review
- LinkedIn User Agreement, section 8.2 (read via the Nov 18, 2026 archive copy)
- LinkedIn Help: Prohibited software and extensions
- stickerdaniel/linkedin-mcp-server
- eliasbiondo/linkedin-mcp-server
- Linked-API/linkedapi-mcp
- gtm-api/linkedin-mcp
- fredericbarthelet/linkedin-mcp-server
- souravdasbiswas/linkedin-mcp-server
- Claude Code docs: MCP
- Cursor docs: MCP
- Codex docs: MCP
- X docs: MCP
- X API pricing
- X developer guidelines
You ship. Gin posts.
Get the app, paste one message into your coding agent, and swipe through your first cards tonight.