LinkedIn MCP Servers: Pages, Posts, Ads, and Sales Navigator with AI
Every other LinkedIn MCP server on GitHub is either a scraper that violates LinkedIn's Terms of Service or a thin wrapper around unofficial endpoints that can break at any time. Some use Patchright (a Playwright fork) to automate the browser. Others reverse-engineer private APIs. LinkedIn actively blocks these — and your account is at risk if you use them.
MCPBundles ships two LinkedIn MCP servers that work the way LinkedIn allows you to work:
- LinkedIn — built on LinkedIn's official REST API with OAuth 2.0. Manages company pages, publishes posts with images and carousels, engages with comments and reactions, runs ad campaigns, and tracks analytics.
- LinkedIn Sales Navigator — drives Sales Navigator search, profile lookups, InMail, and inbox as your connected LinkedIn account. Sign in once on a hosted page (no cookies, no extensions, no scraping); the bundle then runs SN-grade prospecting and outreach with built-in per-account rate caps so a careless agent can't get the seat banned.
You can connect either or both. The pages are the canonical product surfaces — keep this article open if you want the comparison; jump to the skill page when you're ready to use one.
Which one do you want?
| Workflow | Pick | Why |
|---|---|---|
| Post from a company page or personal profile | Official Posts API; supports text, image, multi-image, document carousel, video, reshare. | |
| Run LinkedIn Ads (campaigns, creatives, analytics) | Full Marketing API surface, OAuth-scoped. | |
| Read or reply to comments and reactions | Community Management API with versioned endpoints. | |
| Search Sales Navigator (people, accounts, with SN filters) | LinkedIn Sales Navigator | Hosted sign-in runs as your LinkedIn account; SN seat required for SN-only filters. |
| Send InMail or connection requests | LinkedIn Sales Navigator | Spends from the connected account's normal LinkedIn quota. |
| Read your LinkedIn inbox / reply inside a chat | LinkedIn Sales Navigator | Inbox surface only available via the connected-account flow. |
| Coordinate prospecting → outbound → company-page follow-up | Both | Connect both servers; one bundle, one MCP endpoint. |
The two bundles share nothing at runtime — different identity model, different API, different rate limits. They live as two separate /skills/{slug} pages on purpose.
Why the Official API Matters
The community LinkedIn MCP servers fall into two categories:
Scrapers (e.g., eliasbiondo/linkedin-mcp-server): Use headless browsers to navigate LinkedIn's web UI. Profile scraping, search automation, connection requests. LinkedIn detects and blocks these. Your account can be restricted or banned.
Unofficial API wrappers (e.g., some repos using undocumented endpoints): These use internal LinkedIn API paths that aren't part of any public contract. They work until LinkedIn changes the endpoint — which happens regularly.
MCPBundles uses the LinkedIn Marketing API and Community Management API with OAuth 2.0 scopes (rw_organization_admin, w_organization_social, r_ads, rw_ads, etc.). These are documented, versioned, and supported by LinkedIn. Your AI's actions show up in LinkedIn's official API audit logs.
What Your AI Can Do
Company Page Management
| What you ask the AI | What happens |
|---|---|
| "List the company pages I manage" | Returns all organizations you administer with IDs, names, and details |
| "Look up MCPBundles on LinkedIn" | Searches by vanity name, returns organization profile |
| "How many followers does our page have?" | Dedicated follower count tool — exact number, not an estimate |
| "Show me our follower demographics" | Follower statistics broken down by geography, industry, seniority |
Content Publishing
Your AI creates posts for your personal profile or company page. Every content type LinkedIn supports:
| Post Type | How it works |
|---|---|
| Text-only | Highest algorithm weight — no link penalty |
| Single image | Upload image first → attach to post |
| Multi-image (2-20) | Upload each image → create gallery post |
| Article link | Link preview card with title, description, thumbnail |
| Document/carousel | Upload PDF/PPTX → swipeable carousel viewer |
| Reshare | Repost someone else's content with your commentary |
The workflow for image posts is two steps: upload the image (from a URL or base64), then create the post referencing the image URN. Same pattern for documents and carousels. Your AI handles both steps automatically.
Engagement
- Comments — Read and reply to comments on any post
- Reactions — Like, Praise, Empathy, Entertainment, Interest, Appreciation
- Edit posts — Update post text after publishing
- Delete posts — Remove posts entirely
Advertising
Full LinkedIn Ads API coverage through the same connection:
- Ad accounts — List accounts, check status and budget
- Campaign groups — Top-level organizational containers
- Campaigns — Create and manage ad campaigns with targeting
- Creatives — Ad content linked to campaigns
- Analytics — Performance metrics: impressions, clicks, CTR, engagement, video views
Algorithm Knowledge Built In
Every LinkedIn connection on MCPBundles comes with a skill that includes current algorithm data your AI reads before posting:
- External links in body: 40-50% fewer impressions (March 2026 update intensified this)
- Link in first comment: Reduces penalty to 5-15%
- Image posts: 87% higher engagement vs text-only
- Carousels (PDF): 3-5x more dwell time than text — highest engagement format
- Personal > company: Personal profiles get 5x more engagement and 2.75x more impressions than company pages
- Golden hour: First 60 minutes determine amplification
Your AI applies these patterns automatically. When you say "post about our new feature with a link to the blog post," it knows to put the link in a comment, not the body. When you say "create a carousel about our product," it formats the content as swipeable slides.
The Personal + Company Page Flywheel
The skill includes a growth strategy your AI can execute:
- Post from your personal profile (higher reach) — text or image, no links
- Company page reshares the personal post (builds org content library)
- Company page posts product content — personal profile reshares with commentary
- Both grow together: personal posts drive company page followers
Your AI coordinates this workflow across both accounts.
Sales Navigator: prospecting and outreach without a scraper
Search LinkedIn Sales Navigator from chat — people search, account search, profile lookups, and InMail — using your connected LinkedIn account. No cookies, no scraping, no extensions.
The OAuth LinkedIn API does not expose Sales Navigator search, InMail, or your LinkedIn inbox. To do those things from an AI agent without breaking LinkedIn's ToS, you need to drive a real LinkedIn session — which is exactly what every scraper-based community server tries to do, and exactly why those accounts get banned.
The LinkedIn Sales Navigator bundle uses a hosted sign-in flow (you sign into LinkedIn on a hosted page operated by our connect partner), captures an opaque session identifier, and runs SN actions as your account. There are no cookies to copy, no browser extension to install, and no headless Chrome on the critical path.
What you ask the AI
Four kinds of prompt this bundle is designed to handle:
- People search with SN filters — "Find VPs of Engineering at US-based Series B SaaS companies with 50–500 employees, return the top 25 with current company and tenure." The bundle resolves freeform geographies like "San Francisco Bay Area" to LinkedIn ids and applies seniority, function, headcount, and geography filters that public LinkedIn does not expose.
- Account search with hiring signal — "List logistics companies in Germany with 200–1,000 employees showing employee headcount growth, summarise each one's industry and recent activity." Uses SN-only filters (headcount growth, fortune ranking, region).
- Personalised InMail — "Look up this profile, fan out their recent posts and comments, then draft a personalised InMail referencing one specific post and a mutual connection." Combines profile lookup, related-feed fan-out, and the send-message tool with
inmail=true. Burns one InMail credit from the connected account's monthly pool. - Inbox triage — "Show my LinkedIn inbox: list unread chats, drill into the most recent reply from a prospect, and draft a follow-up." Reads the inbox surface and replies inside an existing chat thread without leaving the AI conversation.
What it can do
| Surface | What you ask the AI |
|---|---|
| People search | Filter by seniority, function, geography, current company, past company, headcount range, school — all with the SN-only filter shape, not the public LinkedIn shape. |
| Account search | Filter by industry, headcount, headcount growth, fortune ranking, region, year founded. Public LinkedIn cannot do most of this. |
| Profile lookup | Resolve a person or company by URN or vanity URL, optionally fanning out their recent posts, comments, and reactions in one call. |
| InMail and invites | Send InMail (consumes one credit from the connected account's monthly pool) or a connection request from a single tool. |
| Inbox | Browse chats, drill into a thread, draft a reply — all within the AI conversation. |
Account safety, by design
LinkedIn does not publish API rate limits, but it actively detects non-human usage patterns and bans accounts that exceed them. The bundle ships with two server-side caps per connected LinkedIn account:
- 500 calls per UTC day — hard ceiling, resets at 00:00 UTC.
- 20 calls per minute — catches runaway loops before they chew through the daily budget.
Both caps are keyed by the connected LinkedIn account, not the credential row, so re-binding the same account does not reset the count. The skill content also tells the agent to pace within the day, spread load across multiple connected accounts when a workflow legitimately needs more throughput, and stop on the first restriction signal.
What it does not do
The Sales Navigator bundle does not post to your feed, manage company pages, or run ads. Those live on the OAuth LinkedIn server above. If you want both prospecting and content/ads, connect both bundles — they are independent and safe to use together.
Why a Hosted Server Matters
Unlike services such as Figma, Slack, or Sentry — which have released their own official MCP servers — LinkedIn has no first-party MCP offering. The community alternatives are scrapers that violate LinkedIn's ToS. MCPBundles fills this gap with two proper servers (one OAuth, one hosted-sign-in), and because they're hosted alongside your other MCP connections (Google Ads, HubSpot, Slack, etc.), your AI agent can coordinate cross-service workflows — research a prospect on Sales Navigator, log them into HubSpot, then schedule a follow-up post on the company page once they reply.
Setup
Company pages, posts, and ads:
- Enable the LinkedIn bundle on MCPBundles.
- Connect via OAuth (LinkedIn prompts for permissions).
- Ask your AI: "List my company pages and show our follower count."
Sales Navigator search and InMail:
- Enable the LinkedIn Sales Navigator bundle.
- Click Connect LinkedIn account — sign in to LinkedIn on the hosted page.
- Ask your AI: "Find VPs of Engineering at Series B SaaS companies in the US, top 25."
Both bundles can be added to the same MCP endpoint. One URL in your AI client, both surfaces available.
FAQ
Is this safe to use? Will my LinkedIn account get banned?
This is built on LinkedIn's official API with proper OAuth scopes — the same API that LinkedIn's own partners use. Your account won't be restricted for using official API endpoints. Scrapers and unofficial tools are what LinkedIn blocks.
Can my AI post to both my personal profile and company page?
Yes. Your AI uses your personal URN (urn:li:person:{id}) or organization URN (urn:li:organization:{id}) as the author. It can post, comment, react, and reshare from either identity.
Why can't I see my personal posts?
Listing personal posts requires the r_member_social scope, which LinkedIn restricts. Your AI can create and manage personal posts, but listing your feed requires organization context. Use organization_id with the list-posts tool to see company page posts.
Does this support LinkedIn ads?
Yes. Full LinkedIn Ads API coverage: ad accounts, campaign groups, campaigns, creatives, and performance analytics. Create campaigns, manage budgets, and pull engagement metrics.
How is this different from the community LinkedIn MCP servers?
Community servers either scrape LinkedIn's web UI (violates ToS, accounts get banned) or use undocumented internal APIs (break without notice). MCPBundles uses LinkedIn's official Marketing and Community Management APIs with versioned endpoints and OAuth for the company-page server, and a hosted-sign-in flow that runs as your real account for the Sales Navigator server. Neither path scrapes the LinkedIn web UI.
Should I connect the OAuth bundle or the Sales Navigator bundle?
If you want to post, run ads, manage company pages, or read comments and reactions, you want the LinkedIn (OAuth) bundle. If you want to search Sales Navigator, send InMail, run a connection request, or work in your LinkedIn inbox, you want the LinkedIn Sales Navigator bundle. Most teams want both — they are independent and run side-by-side from one MCP endpoint.
Will Sales Navigator search ban my account?
Aggressive querying on a single LinkedIn account can trigger LinkedIn's anti-scraping detection — that risk is real for any automated tool, including ones you write yourself. The Sales Navigator bundle limits each connected account to 500 calls per UTC day and 20 calls per minute server-side, and the skill content tells the agent to pace within the day and stop on the first restriction signal. Spread larger workflows across multiple connected accounts rather than pushing one harder.