LinkedIn MCP servers compared: 7 options for agents in 2026

TL;DR

• Seven LinkedIn MCP servers, two kinds. Four action servers (Curviate, Linked API, ConnectSafely, BeReach) give your agent LinkedIn itself: search, profiles, messages, invitations, posts. Three campaign servers (HeyReach, Botdog, Dripify) give it a vendor's campaign tool: lead lists, sequences, stats.
• Per LinkedIn account per month on monthly billing (October 2026): Curviate EUR 20 flat, with no action metering and every interface included. ConnectSafely USD 10. BeReach about EUR 50, capped by credits. Linked API USD 69 to 99. HeyReach, Botdog and Dripify USD 79.
• Curviate puts the same actions behind one key and one per-account budget in MCP, CLI, REST API and TypeScript SDK. It signs in with OAuth in Claude and ChatGPT and answers repeat profile reads inside 12 hours without spending LinkedIn budget.
• If your agent should decide what happens on LinkedIn, pick an action server. A campaign server lets it steer a sequencer the vendor runs.

Every "LinkedIn MCP" vendor promises to connect Claude to LinkedIn. They mean different things by it. Some expose LinkedIn actions, and your agent searches, reads and writes as you. Others expose their own campaign engine, which the vendor runs. I sorted seven servers by that split, then by price, connection and gaps. One of them is mine: I build Curviate, a LinkedIn API, CLI, MCP server and TypeScript SDK for AI agents.

What should you compare in a LinkedIn MCP server?

Start with what the server exposes, then go down the list.

1. What the MCP exposes: LinkedIn actions (search people, send a message) or campaign objects (create campaign, add leads). It decides who is in charge, your agent or the vendor's sequencer.
2. Tool count. If it is unpublished or vague, you cannot check coverage before you pay.
3. Auth: OAuth, an API key in a header, or a token in the URL. A URL token leaks wherever the URL gets logged.
4. Transport: hosted URL or local process.
5. Price per LinkedIn account, with period and currency.
6. Sales Navigator and Recruiter as tools in the MCP itself, beyond a connectable account.
7. Writes versus reads. Can the agent send, or only look and queue?
8. Limits: who sets per-account ceilings, and what happens when one is hit.
9. Repeat reads: does reading the same profile twice spend the account's LinkedIn budget twice?

Then look at how the account connects. Curviate's safety page and Linked API's FAQ both describe a cloud browser per account where you log in yourself. Curviate's API connects an account with an email and password or a session cookie, and its privacy policy lists credentials as stored encrypted and kept until you disconnect the account. ConnectSafely stores your email, password and 2FA secret encrypted, or uses a Chrome extension. BeReach asks for your LinkedIn session cookie.

How do the seven servers compare on tools and price?

Action servers first, then campaign servers. I took every cell from the vendor's own pricing page and MCP docs on October 2, 2026. Price is per account per month, monthly / billed annually, in USD unless marked EUR. Curviate and BeReach quote theirs before tax. I did not convert currencies.

Linked API's pricing page shows a euro sign to EU visitors while its structured data says USD. The numbers are the same. BeReach bills credits per workspace, so EUR 49.50 per account per month on Pro is my own arithmetic, and the credit pool is the limit that actually binds.

Which servers let your agent act on LinkedIn directly?

Curviate, Linked API, ConnectSafely and BeReach. BeReach drafts first messages and waits for your approval before sending.

Curviate runs a hosted MCP server at app.curviate.com/mcp over Streamable HTTP. In Claude and ChatGPT you sign in with OAuth. Other clients pass an API key as a Bearer header, or, as a last resort, in the URL. The MCP server, REST API, CLI and TypeScript SDK share one key and one per-account budget. Tools are grouped in toolsets, and the Sales Navigator and Recruiter toolsets are off by default and need the matching LinkedIn licence. It costs EUR 20 per account per month, or EUR 192 a year billed annually, with no action metering (pricing). There is no campaign UI. Your agent plans, and each action is one tool call.

Linked API runs its MCP hosted at mcp.linkedapi.io, with both tokens passed in the URL query string, or locally via npx @linkedapi/mcp (installation). Its tool list has 62 rows: 34 standard LinkedIn tools, 8 Sales Navigator, 3 for workflows and usage, 17 admin. Actions run as asynchronous workflows that return a workflow id. Around the MCP sit Node and Python SDKs, a CLI, agent skills, n8n and Make. Pricing: Core is USD 69 per account per month, or USD 49 per month billed annually. Plus adds Sales Navigator for USD 99, or USD 74 per month billed annually. Recruiter is not listed on its pricing, MCP tool list or llms.txt. It suits teams that want n8n, Make or a Python SDK around the agent and will pay Plus for Sales Navigator.

ConnectSafely is mostly about inbound engagement (post boosting, auto-commenting). Its API, MCP and CLI module costs USD 10 per LinkedIn account per month, USD 9 per month billed annually (pricing). The MCP is a personal link you paste into Claude as a custom connector. The MCP page claims "60+ tools" without listing them. Its OpenAPI file has 101 operations across messaging, connections, search, posts and companies. Sales Navigator coverage is four messaging operations, plus people and company search by Sales Navigator search URL. The spec has no Recruiter endpoints. If price decides it and your agent needs ordinary reads and writes without Recruiter, look here.

BeReach is an AI outreach agent that also exposes itself to Claude. Its remote MCP at mcp.bereach.ai/mcp signs in with OAuth (Claude page). Its pages claim 26 or 27 tools and name 25, among them find_people, draft_dm, approve_drafts and send_dm. First messages are drafted for your approval, and follow-up sequences are excluded by design. Pricing is per workspace: Pro at EUR 99 per month covers two LinkedIn accounts and a monthly credit pool. It suits someone who wants a ready-made agent that proposes and then waits for a yes.

Which servers steer a campaign tool instead?

HeyReach, Botdog and Dripify. Their MCP tools work on the vendor's campaigns and lead lists, and the vendor's engine does the LinkedIn work.

HeyReach is multi-sender outreach for agencies. Each workspace gets its own MCP URL and key (MCP page). Its pricing page says agents can create campaigns, split lead lists and tag replies. It does not publish a tool count. Behind the MCP sit a public REST API (OpenAPI 3.1, 87 paths, inbox send included, no people search that I could find) and an official CLI. Growth costs USD 79 per sender per month, or USD 63 per month billed annually, under 10 senders, and USD 59 or USD 47 from 10. Unlimited is USD 2,999 per month for up to 300 senders. API and MCP come with Growth, the lowest paid plan. HeyReach is built for running many sender accounts, with the agent building and steering campaigns.

Botdog is automation centred on Sales Navigator. You paste api.botdog.co/mcp into Claude, ChatGPT, Cursor or Claude Code and sign in with OAuth 2.1. The tool list has 41 entries such as list_campaigns and add_leads_to_campaign. I found no LinkedIn search, profile read or message-send tool in it. Pricing: Solo is USD 79 per account per month, or USD 55.33 per month billed annually, API included. The page does not say which plan includes the MCP. It fits a team that works from Sales Navigator, wants a campaign UI and wants Claude to report on campaigns.

Dripify sells per-seat drip campaigns. Its MCP has four tools: list campaigns, list a campaign's lead lists, look up a lead, upload up to 1,000 leads (help article). It cannot send messages. It authenticates with an API key header, and Dripify states that Claude web and mobile and ChatGPT "currently can't connect"; OAuth is planned. You need Pro or Advanced. Pro is USD 79 per account per month, or USD 59 per month billed annually (pricing). The MCP makes sense if you already run Dripify and want an agent to feed it leads.

How do you connect LinkedIn to Claude through an MCP server?

Every server here has a hosted URL. You add it to Claude, then sign in or pass a key. Linked API also runs locally. In Claude Code, with Curviate as the example (from the curviate-mcp README):

# Add the hosted server, then run /mcp and choose Authenticate
claude mcp add --transport http curviate https://app.curviate.com/mcp

In the Claude apps, add the same URL as a custom connector and sign in with OAuth. If a key travels in the URL (Linked API's hosted URL, Curviate's ?token= option), treat that URL as a secret. Also check which tools the client actually sees. Curviate's Sales Navigator and Recruiter tools stay hidden until you switch those toolsets on.

Does a LinkedIn MCP server put your account at risk?

Yes, some. An MCP server changes who decides what to do. LinkedIn still sees the same actions on your account. Three vendors say so in writing. Curviate's terms: "That design lowers the risk; it does not remove it." Linked API's terms say using it does "not exempt you from LinkedIn's enforcement actions." BeReach's docs: "Any tool that acts through your account carries some risk."

The brakes differ by vendor. Linked API caps each action per day, week or month and returns an error at the cap. HeyReach freezes an account at 200 actions a day. Botdog calls its limit zones "guidance, not caps." Curviate sets a ceiling per action. Out of the box, a crossed ceiling comes back as a warning; switch the account to enforce and the call is refused. With an agent in the loop, I would switch it on.

Repeat reads are the other lever. In Curviate, a person profile read within 12 hours (the default) comes back from your workspace's own store. Stored chats and messages come back at any age and get refreshed when a message event says they changed. None of that sends a request to LinkedIn or spends the account's action budget (caching guide). ConnectSafely's OpenAPI spec caches profiles for 6 hours, says "cached requests do not count against limit", and reads conversations with "DB-first caching". BeReach charges 0 credits for cached profile visits. Linked API documents caching for conversations only.

Where does Curviate fit among LinkedIn MCP servers?

Curviate is an action server. I built it for agents that already plan their own work and need LinkedIn actions to carry it out. Search, messages, invitations and posts are tools, the same calls work in the CLI and API, and it costs EUR 20 per account per month, excl. VAT. With a campaign server, your agent steers someone else's sequencer. With Curviate it decides every step, and the budget, ceilings and stored reads are already built in. Not affiliated with LinkedIn Corporation.