There is no one-click “LinkedIn” button inside Claude. This guide covers exactly what a Claude LinkedIn integration can and can’t do in 2026, the official read-only route through LinkedIn’s Marketing API, and the custom MCP connector path — step by step, with the tradeoffs most guides skip.
1Why Connect Claude to LinkedIn?
LinkedIn holds the data most B2B teams actually work from — company page performance, prospect research, candidate pipelines, and the drafts of every post and message that goes out under a brand’s name. Claude is good at reasoning over that kind of unstructured, judgment-heavy work: summarizing a prospect’s activity before a call, drafting a post in a consistent voice, or turning a spreadsheet of leads into a prioritized outreach list. A Claude LinkedIn integration is really an attempt to remove the copy-paste step between the two.
- Research before outreach: Pull a company page’s recent activity or posting cadence into a chat instead of tab-switching to look it up manually.
- Consistent content voice: Draft, refine, and format LinkedIn posts inside a chat that already has your brand’s tone and prior examples as context.
- Reporting without exports: Ask Claude to summarize Company Page follower growth or post performance instead of building a manual export routine.
- Faster qualification: Feed Claude a list of profiles or companies and ask it to flag which ones match your ideal customer profile.
What it isn’t is a replacement for LinkedIn’s own interface for anything sensitive — messaging, connection requests, or account-level actions carry real platform risk, covered in section 7.
2What the Integration Actually Does (and Doesn’t)
Before wiring anything up, it’s worth being precise about the plumbing, because this is where most “Claude LinkedIn MCP” guides get vague. Claude connects to external services through the Model Context Protocol (MCP) — an open standard that lets Claude call tools exposed by a remote server. LinkedIn itself doesn’t run one of these servers, and Anthropic doesn’t maintain one either. Every LinkedIn connector you’ll find is a third party sitting in between, translating whatever LinkedIn access it has into MCP tools Claude can call.
That middle layer only has as much access as its own connection to LinkedIn allows, and LinkedIn splits that access into two very different tiers:
What’s realistically available depending on which LinkedIn access the MCP server uses
| Access Type | What It Can Do | How It’s Obtained |
|---|---|---|
| Official Marketing API | Read-only analytics for Company Pages you administer — followers, post stats, demographics | LinkedIn developer app + OAuth, approved by LinkedIn |
| Official Share/Post API | Publish posts to a Company Page you manage | LinkedIn developer app with approved product access |
| Personal profile automation | Reading DMs, sending connection requests, scraping profiles | Not offered by LinkedIn’s public API at any tier — third-party tools that do this rely on browser automation or session cookies |
In practice, that means the safest and most durable version of a Claude LinkedIn integration covers Company Page analytics and content drafting — not personal-profile messaging automation.
3Prerequisites Before You Start
- A Claude plan that supports custom connectors. Custom connectors are available on Pro, Max, Team, and Enterprise plans, not the free tier.
- Admin access to the LinkedIn Company Page you want data from, if you’re going the official Marketing API route — you can’t pull analytics for a page you don’t administer.
- A decision on scope. Know upfront whether you need read-only reporting, content drafting support, or something closer to outreach automation — that decision determines which MCP server is even appropriate, before you pick one.
- For Team/Enterprise accounts: confirm who your Owner or Primary Owner is, since only they can add a connector at the organization level before individual members can connect to it.
4Step-by-Step: How to Connect Claude to LinkedIn
The mechanics inside Claude are identical no matter which LinkedIn MCP server you choose — what changes is the URL you paste in and what you authenticate against. Here’s the general path:
- Choose your MCP server based on scope, not marketing copy. If you only need Company Page analytics, look for a server built specifically on LinkedIn’s official Marketing API — it will be explicit about being read-only. If you need broader access, understand that it’s operating outside LinkedIn’s approved API before you connect anything.
- Copy the server’s MCP endpoint URL. Every legitimate MCP server publishes a single HTTPS URL (commonly ending in
/mcp) — this is what you’ll paste into Claude, not an API key on its own. - Open Connectors in Claude. On Pro or Max, go to Settings → Connectors. On Team or Enterprise, an Owner first adds it under Organization Settings → Connectors → Add → Custom before individual members can connect.
- Click “Add custom connector” and paste the URL. Give the connector a clear name (e.g., “LinkedIn Company Page Analytics”) so it’s identifiable later if you add more connectors.
- Authenticate. Most servers use OAuth — you’ll be redirected to log in and approve the specific scopes being requested. Read the permissions screen; this is where you confirm whether it’s asking for read-only analytics or broader account access.
- Enable the connector in a conversation. Use the “+” button in the chat window to turn the connector on per-conversation — connectors aren’t active everywhere by default.
- Run a test prompt. Ask something low-stakes and verifiable first — “Show follower growth on our Company Page for the last 30 days” — and check the numbers against LinkedIn’s own dashboard before trusting it for anything reported externally.
That’s the full how to connect Claude to LinkedIn flow for the connector itself — most of the actual decision-making happens in step 1, choosing what kind of access you’re comfortable granting.
5After You Connect: What to Configure Next
- Scope review, not just connection status. “Connected” only confirms authentication worked — reread what permissions you approved, since OAuth screens list this explicitly.
- Per-conversation enablement. Decide whether the connector should be on by default or something you enable only for specific research or reporting chats — leaving it enabled everywhere isn’t necessary for most use cases.
- A human review step for anything published. If the connector can draft or post content, keep a manual approval step before anything goes live under your brand’s name.
- A re-authentication reminder. OAuth tokens for third-party connectors typically expire; set a recurring reminder rather than discovering the connector silently stopped working.
6What You Can Do Once Connected
Realistic use cases once a LinkedIn MCP server is live in Claude
| Use Case | What Claude Does | Access Tier Needed |
|---|---|---|
| Company Page reporting | Summarizes follower growth, engagement, and top posts on request | Official Marketing API (read-only) |
| Content drafting | Writes and refines post drafts using your prior posts as style reference | None required — works without a LinkedIn connector at all |
| Scheduled publishing | Pushes an approved post to a Company Page | Official Share/Post API |
| Prospect research | Synthesizes information you paste in about a company or contact | None required — manual paste-in, not a live connector |
| Outreach messaging | Drafts message copy for you to send yourself | None required for drafting; sending it automatically falls outside LinkedIn’s official API |
7Connector vs. Manual Workflow: Do You Need One?
Before adding a connector, it’s worth weighing it against just working in Claude without one. A connector earns its keep when you need current, live LinkedIn data on a recurring basis — not for one-off drafting.
Connector-based access vs. paste-in workflow with no connector
| Custom MCP Connector | Manual Paste-In (No Connector) | |
|---|---|---|
| Setup effort | Choosing a server, OAuth authentication, ongoing token renewal | None — works in any existing chat immediately |
| Data freshness | Live, pulled at the time you ask | As current as whatever you paste in |
| Account exposure | Depends entirely on the third-party server’s own access and security practices | None — Claude never touches your LinkedIn account |
| Best for | Recurring reporting on Company Pages you administer | Occasional drafting, research, and one-off summaries |
Teams running recurring Company Page reporting tend to find the connector worth the setup. Individuals mostly using Claude to draft posts or think through a prospect list are often just as well served without connecting anything.
8Troubleshooting Common Connection Issues
The connector shows “Connected” but Claude says it has no access
Enabling a connector at the account level doesn’t turn it on inside every chat. Use the “+” button in the specific conversation and confirm the connector toggle is switched on for that thread.
Authentication keeps failing
Confirm you’re logging in with the LinkedIn account that actually administers the Company Page in question — a personal profile with no admin role on the page will authenticate but return no usable data. If it still fails, disconnect and reconnect from Settings → Connectors.
Claude returns outdated follower or post numbers
Third-party MCP servers built on LinkedIn’s Marketing API typically cache results rather than querying live on every request. Numbers a few hours stale are usually a caching interval, not a broken connection.
The connector stopped working after a few weeks with no changes made
This is almost always an expired OAuth token. Go back to Settings → Connectors, disconnect, and reauthenticate — this is common enough with third-party connectors that it’s worth a standing calendar reminder.
An organization member can’t see the connector at all
On Team and Enterprise plans, an Owner has to add the connector to the organization first under Organization Settings → Connectors before it appears as something individual members can connect to.
9Is This Integration Right for You?
If your LinkedIn work is mostly Company Page reporting for a page you administer, connecting a read-only Marketing API-based MCP server is a low-risk way to save time on recurring exports. If what you actually want is Claude reading your personal profile’s DMs or sending connection requests on your behalf, that’s operating outside LinkedIn’s official API — worth going in with eyes open about the account risk rather than treating it as a standard setup step.
For most individual users, drafting content and researching prospects by pasting information into a normal Claude chat covers the bulk of the value without connecting anything at all.
10FAQs
No. Anthropic’s Connectors Directory doesn’t include a first-party LinkedIn app the way it does for tools like Slack or Notion. Any Claude LinkedIn connection goes through a custom connector pointing at a third-party MCP server.
Yes. Custom connectors are available on Pro, Max, Team, and Enterprise plans. The free tier doesn’t support adding custom MCP connectors.
Only if the MCP server you connect is built on LinkedIn’s official Share/Post API for a Company Page you administer. There’s no official API tier that lets an automated tool post from a personal profile.
Tools that automate personal-profile actions — messaging, connection requests, profile scraping — operate outside LinkedIn’s public API and its terms of service. LinkedIn actively enforces against this and can suspend accounts. That’s a real risk to weigh, not a configuration detail to skip past.
No. Drafting, editing, and refining post copy works in any Claude conversation without connecting anything — you only need a connector for live data like Company Page analytics or automated publishing.
During the OAuth authentication step, Claude and the server both show a permissions screen listing the exact scopes being requested before you approve anything. Read it before clicking through — it’s the clearest signal of whether a server is read-only or requesting broader access.