The short answer
- LinkedIn has no public MCP server. There is no endpoint to add to Claude, Cursor or any other client.
- LinkedIn does ship two apps inside ChatGPT: "LinkedIn" (look up a professional) and "LinkedIn Ads" (read-only ad set performance, in beta).
- Everything else is third party, in two kinds: tools on LinkedIn’s official APIs (posting, company pages, ads) and scrapers that drive your logged-in session (profiles, messages, people search).
- LinkedIn’s User Agreement forbids the second kind, and accounts using them get restricted.
Current as of October 2, 2026.
"LinkedIn MCP" is eight different requests wearing one name. Posting as yourself has a sanctioned route. Reading other people’s profiles does not. Which one you mean decides both the tool and the risk, so this guide takes them one at a time. If ads are the job, go straight to LinkedIn Ads over MCP.
Does LinkedIn have an official MCP server?
No public one. LinkedIn’s developer documentation covers OAuth, Marketing, Sales, Talent and Compliance APIs and no MCP server, and Claude’s connector directory has no LinkedIn connector.
What LinkedIn has built lives inside ChatGPT. ChatGPT apps run on MCP under the hood, which is why the distinction matters:
- LinkedIn looks up a professional and links to their profile. It is a lookup, not a data export.
- LinkedIn Ads is a read-only beta for ad set performance. It cannot create, pause or change anything.
Both work in ChatGPT and nowhere else. If you use Claude, Cursor, Copilot or your own agent, there is no LinkedIn-published server to connect to, and everything below is a third party.
What LinkedIn’s rules actually say
Worth reading before choosing a server, because several of the first results break them. LinkedIn’s User Agreement, section 8.2, lists what members agree not to do, including:
- using software, scripts or bots "to scrape or copy the Services, including profiles";
- using another person’s account, "such as sharing log-in credentials or copying cookies";
- using "bots or other unauthorized automated methods" to send messages or create, like and share posts.
LinkedIn’s help centre spells out the consequence: people who use scraping or automation software "risk having their accounts restricted or shut down", and the tools can become non-operational without notice. LinkedIn’s automated activity page describes the restriction and how an account is re-enabled. LinkedIn also enforces this in court: hiQ Labs ended its scraping case in December 2022 under a permanent injunction, and Proxycurl shut down in July 2025 after LinkedIn sued it that January.
The line is simple. A tool that uses LinkedIn’s official APIs through its own approved app is fine. A tool that drives your logged-in session, or needs your cookie, is automating your account.
The official routes an MCP server can use
| API | What it allows | Who can use it |
|---|---|---|
| Sign In with LinkedIn | Your own name, headline, photo and email | Any developer |
| Share on LinkedIn | Post, comment and like as the signed-in member | Any developer |
| Community Management API | Company page posts, comments and analytics | Registered organizations with a commercial use case, after review |
| Advertising API | Campaigns, audiences, lead forms and reporting | Approved apps; edits on up to five ad accounts until the Standard tier |
| Sales Navigator | Sales Navigator data inside partner tools | Sales Navigator partners only |
| Talent APIs | Job posting, apply flows, recruiter sync | Talent partners only |
What is missing is the point. No open permission reads other members’ profiles, searches people or sends messages. Any server offering those is either a LinkedIn partner, which none of the popular ones are, or automating your account.
Every LinkedIn MCP option, compared
| Server | What it does | How it reaches LinkedIn | Standing |
|---|---|---|---|
| Sprites | LinkedIn Ads: read, change with approval; company posts; competitor ads | Official Advertising API; public Ad Library | Sanctioned |
| Taplio | Research, draft, schedule and publish posts; analytics | Your Taplio account; no scraping or browser automation | Sanctioned |
| ContentIn | Voice-trained writing, scheduling, analytics | ContentIn’s approved LinkedIn app, official API | Sanctioned |
| Zapier | Create a share update or a company update | Zapier’s LinkedIn integration; two tasks per call | Sanctioned |
| Composio | Posts, comments, company info, page and share stats | Managed LinkedIn OAuth | Sanctioned |
| danielpopamd/linkedin-ads-mcp | Create, update and delete campaigns, groups and ads | Your own developer app with Advertising API approval | Sanctioned |
| stickerdaniel/linkedin-mcp-server | Profiles, people search, messages, jobs, feed | Your logged-in browser session and cookies | Against terms |
| Apify | Profile scraping, about $10 per 1,000 results | Scraping, no LinkedIn login | Against terms |
| Bright Data | Person and company profile data | Scraping; 5,000 requests a month free | Against terms |
The most popular community server, stickerdaniel/linkedin-mcp-server, is also the most capable, and honest about it. It drives a real browser logged in as you, can import your session from Chrome, Brave or Edge, and exposes profile lookups, people search, your inbox and sending messages. Its README says LinkedIn prohibits automated access and that accounts using such tools "can be restricted or banned". Take it at its word.
Older servers that promise people search over the official API, such as felipfr/linkedin-mcpserver, call endpoints the open permissions do not grant, and have had no commits since March 2025. Expect them to fail.
The top LinkedIn MCP servers on GitHub, compared
Search GitHub for a LinkedIn MCP server and the same handful of repositories comes back. They split cleanly along the line above: the most-starred ones act as you, and the two built for ads use LinkedIn’s own API.
| Repository | What it does | How it reaches LinkedIn | Standing |
|---|---|---|---|
stickerdaniel/linkedin-mcp-server | Profiles, companies, your inbox, messages, connection requests and jobs. The most-starred LinkedIn server by a wide margin, with more than 3,700 stars | Your own logged-in browser session, run on your machine | Against terms |
eliasbiondo/linkedin-mcp-server | People, company and job search, and profiles scraped section by section, contact details included | Browser automation signed in to your LinkedIn account | Against terms |
Linked-API/linkedapi-mcp | Lead search, profile analysis, reading and sending messages | Your account, driven from the vendor’s cloud browser | Against terms |
gtm-api/linkedin-mcp | Search, connection requests, messages and enrichment, with pacing limits on each action | Your account, run in a hosted cloud browser | Against terms |
felipfr/linkedin-mcpserver | People search and profiles over the official API | Endpoints the open permissions do not grant; no commits since March 2025 | Likely broken |
danielpopamd/linkedin-ads-mcp | Campaigns, creatives, audiences and reporting, with full write access | Your own developer app on the Advertising API | Sanctioned |
Liam, stan-rym/liam-linkedin-ads-MCP | Campaigns created as drafts, matched audiences, reporting and competitor ads from the Ad Library | Your own developer app on the Advertising API | Sanctioned |
Stars measure capability, not safety. The servers that read profiles and send messages can only do it by acting as you, which is the behaviour LinkedIn’s User Agreement names and the help centre says gets accounts restricted. A managed cloud browser with pacing changes how often the account acts, not whether it is automated.
The two ads servers are the sanctioned ones on GitHub, and both start with the same step: registering a LinkedIn developer app and getting it approved for the Advertising API before the first call. Writes then run on your own credentials, with whatever confirmation the server itself asks for. Sprites removes that step: it connects through its own approved Advertising API app, and every change comes back as an approval card. The setup is on the LinkedIn Ads MCP server page.
Which one to use, by what you are doing
- Writing and scheduling your own posts: Taplio or ContentIn. Both publish without scraping or browser automation, and both learn your voice.
- One-off posting from an automation: Zapier or Composio. Cheap and sanctioned, and blind to what performs.
- Company page content: a tool on the Community Management API, or Zapier’s company update action.
- Prospecting and people research: Sales Navigator, in the browser, by a person. There is no sanctioned MCP route, and the account at risk is yours.
- LinkedIn Ads: Sprites to run campaigns with approval, or LinkedIn’s own ChatGPT app for read-only numbers.
LinkedIn in Claude and ChatGPT, through Sprites
Sprites is an AI marketing agent with its own MCP server, and LinkedIn Ads is one of its channels, connected through LinkedIn’s official Advertising API. From Claude, ChatGPT, Cursor or any MCP client, it:
- reads campaign groups, campaigns, ads, lead forms and audiences, and answers performance questions about them;
- proposes budget, status, audience, lead form and campaign changes as approval cards you edit before anything applies;
- lists your company page’s posts, so a post that is working organically can become sponsored content;
- pulls any company’s ads from LinkedIn’s public Ad Library for competitor research, with no connected account needed.
It does not read people’s profiles, search members or touch your inbox, because there is no sanctioned route to do so. LinkedIn is available on the Grow plan and above, alongside Google, Meta, TikTok and Reddit on the same endpoint. The setup and the comparison with the other options are on the LinkedIn Ads MCP server page.
Related
- Every ad platform’s MCP server, and which can change things
- Reddit MCP: the other network with no public server
- The best MCP servers for marketers, by job
- Is MCP safe: what to check before granting write access
LinkedIn MCP questions
Does LinkedIn have an official MCP server?
Not one you can connect to. LinkedIn publishes no MCP endpoint for Claude, Cursor or any other client. It does ship two first-party apps inside ChatGPT — "LinkedIn", which looks up a professional, and "LinkedIn Ads", a read-only beta for ad set performance — and those work in ChatGPT only.
Is there a Claude MCP for LinkedIn?
Not from LinkedIn. Claude’s connector directory has no LinkedIn connector. LinkedIn reaches Claude through third parties: for ads, Sprites, Supermetrics or Windsor.ai; for posting, Taplio or ContentIn, added as custom connectors.
What is the URL for the LinkedIn MCP server?
There is no official one. Every LinkedIn MCP URL belongs to a third party — for example mcp.taplio.com for posting through Taplio, or mcp.sprites.ai/mcp for LinkedIn Ads through Sprites — and each one only reaches what its own LinkedIn integration is allowed to.
What is the best LinkedIn MCP server on GitHub?
stickerdaniel/linkedin-mcp-server is the most-starred and the most capable, and it works by driving your logged-in LinkedIn session, which LinkedIn’s User Agreement prohibits. For LinkedIn Ads, danielpopamd/linkedin-ads-mcp and Liam (stan-rym/liam-linkedin-ads-MCP) use the official Advertising API through a LinkedIn developer app you register yourself.
How do I get Claude to scrape LinkedIn?
You can, with a session-based server or a scraping API, and LinkedIn’s User Agreement forbids it: it bans software that scrapes profiles and the copying of cookies, and LinkedIn restricts accounts that use such tools. Use Sales Navigator in the browser for prospecting, and an official-API tool for anything automated.
Can ChatGPT scrape LinkedIn profiles?
No. LinkedIn’s own app in ChatGPT looks up a professional and links to their profile; it does not export profile data. Bulk profile data only comes from third-party scrapers, which LinkedIn’s User Agreement prohibits.
Will I get banned for using a LinkedIn MCP server?
You can be restricted for using one that automates your account. LinkedIn’s help centre says users of scraping or automation software "risk having their accounts restricted or shut down". Servers built on LinkedIn’s official APIs — posting, company pages, ads — carry no such risk.
Can an MCP server post to LinkedIn for me?
Yes, legitimately. LinkedIn’s open "Share on LinkedIn" permission lets an app post, comment and like on your behalf, and company pages go through the Community Management API. Taplio, ContentIn, Zapier and Composio post through LinkedIn’s own APIs rather than your browser.
Is there a LinkedIn Ads MCP server?
Not a public one from LinkedIn — only the read-only LinkedIn Ads app inside ChatGPT. Hosted options such as Sprites read and change LinkedIn campaigns through the Advertising API, with each change held for approval. The full comparison is on the LinkedIn Ads MCP page.