TL;DR

• The seven LinkedIn MCP servers here come in two kinds. Four action servers (Curviate, Linked API, ConnectSafely, BeReach) hand your agent LinkedIn itself: search, profiles, messages, invitations, posts. Three campaign servers (HeyReach, Botdog, Dripify) hand your agent a vendor's campaign tool: lead lists, sequences, stats.
• Per LinkedIn account per month on monthly billing (October 2026): ConnectSafely USD 10, Curviate EUR 20, BeReach about EUR 50 (credit-capped), Linked API USD 69 to 99, HeyReach, Botdog and Dripify USD 79.
• Linked API has the most GitHub stars of the action servers (60 to 80 per agent repo). Curviate is youngest: released May 2026, 0 stars, no reviews.
• Choose an action server if your agent should decide what happens on LinkedIn. Choose a campaign server if your sequences already live in HeyReach, Botdog or Dripify and the agent should steer them.

Every "LinkedIn MCP" vendor promises to connect Claude to LinkedIn. They mean different things. Some expose LinkedIn actions, so your agent searches, reads and writes as you. Others expose their own campaign engine, which the vendor then runs. This comparison sorts seven servers by that split, then by price, connection and gaps. Curviate, a LinkedIn API, CLI, MCP server and TypeScript SDK for AI agents, is my own product, listed with its gaps.

What should you compare in a LinkedIn MCP server?

Compare what the server exposes first, then eight more criteria.

1. What the MCP exposes. LinkedIn actions (search people, send a message) or campaign objects (create campaign, add leads): your agent or the vendor's sequencer is in charge.
2. Tool count. An unpublished or vague count makes coverage hard to check before you pay.
3. Auth. OAuth, an API key in a header, or a token in the URL, which leaks wherever the URL is logged.
4. Transport. Hosted URL or local process.
5. Price per LinkedIn account, with period and currency.
6. Sales Navigator and Recruiter. Tools in the MCP, not just 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 at one.
9. Repeat reads. Whether reading the same profile twice spends the account's LinkedIn budget twice.

How the account connects matters too. 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, auth and price?

The seven split into four action servers and three campaign servers, from USD 10 (ConnectSafely) per LinkedIn account per month on monthly billing. Cells as of October 2, 2026, from each vendor's pricing page and MCP docs. The price column is per account per month, monthly / billed annually, in USD unless marked EUR; Curviate and BeReach state theirs before tax. Currencies are not converted.

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

Which servers let your agent act on LinkedIn directly?

Four do: Curviate, Linked API, ConnectSafely and BeReach, though BeReach drafts first messages for your approval.

Curviate. A hosted MCP server at app.curviate.com/mcp over Streamable HTTP, with OAuth in Claude and ChatGPT, an API key as a Bearer header, or, as a last resort, the key in the URL. The MCP server, REST API, CLI and TypeScript SDK share one key and one per-account budget. Its tools are grouped in toolsets. Sales Navigator and Recruiter tools are off by default, labelled beta, need the matching LinkedIn licence, and its llms.txt says they are "not yet exercised against a real premium account." EUR 20 per account per month or EUR 192 per year billed annually, no action metering (pricing). Gaps: released May 2026, 0 GitHub stars, no public reviews, n8n and Make "coming soon", no campaign UI.

Choose it if you want LinkedIn as raw actions for your own agent, the same surface in MCP, CLI and API, and a flat price, and accept a young product with beta premium tools.

Linked API. The action server with the most GitHub stars. The MCP runs 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 with a workflow id. Around it: Node and Python SDKs, a CLI, agent skills, n8n and Make. Its repos show 68 stars on linkedapi-mcp and 80 on linkedin-skills. Pricing: Core USD 69 per account per month, or USD 49 per month billed annually; Plus, which adds Sales Navigator, USD 99 or USD 74 per month billed annually. Recruiter is not listed on its pricing, MCP tool list or llms.txt.

Choose it if you want the larger ecosystem (n8n, Make, a Python SDK) and Sales Navigator is worth the Plus price.

ConnectSafely. Mostly 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 lowest per-account price here. 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 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. Its spec has no Recruiter endpoints.

Choose it if price decides it and your agent needs classic reads and writes, not Recruiter.

BeReach. 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; follow-up sequences are excluded by design. Pricing is per workspace: Pro EUR 99 per month covers two LinkedIn accounts and a monthly credit pool.

Choose it if you want an agent that proposes and waits for approval, not a tool surface for your own agent.

Which servers steer a campaign tool instead?

Three do: HeyReach, Botdog and Dripify, whose MCP tools work on the vendor's campaigns and lead lists, not on LinkedIn itself.

HeyReach. Multi-sender outreach for agencies. Each workspace gets its own MCP URL and key (MCP page). Per its pricing page, agents can create campaigns, split lead lists and tag replies. The tool count is not published. Behind it: a public REST API (OpenAPI 3.1, 87 paths, inbox send included, no people search found) and an official CLI. Pricing: Growth at USD 79 per sender per month, or USD 63 per month billed annually, under 10 senders, USD 59 or USD 47 from 10; Unlimited at USD 2,999 per month for up to 300 senders. API and MCP are on Growth, the lowest paid plan.

Choose it if you run many sender accounts and the agent should build and steer campaigns.

Botdog. Automation centred on Sales Navigator. 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; no LinkedIn search, profile read or message-send tool appears. Pricing: Solo USD 79 per account per month, or USD 55.33 per month billed annually, API included; the plan for MCP is not stated.

Choose it if your team works from Sales Navigator, wants a campaign UI and wants Claude to report on campaigns.

Dripify. 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). No messaging. It authenticates with an API key header, and Dripify states that Claude web and mobile and ChatGPT "currently can't connect"; OAuth is planned. It needs Pro or Advanced: Pro is USD 79 per account per month, or USD 59 per month billed annually (pricing).

Choose it if you run Dripify and want an agent to feed it leads.

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

Add the server's hosted URL to Claude, then sign in or pass a key; every server here offers one (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. Where a key travels in the URL (Linked API's hosted URL, Curviate's ?token= option), treat the URL as a secret. And check which tools the client 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, not how LinkedIn sees the result. Three vendors say so. Curviate's terms: "That design lowers the risk; it does not remove it." Linked API's terms: using it does "not exempt you from LinkedIn's enforcement actions." BeReach's docs: "Any tool that acts through your account carries some risk."

Who holds the brakes differs. Linked API caps each action per day, week or month and errors 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; its agent docs say the default posture returns a crossed ceiling as a warning, and the enforce setting makes it a refusal. With an agent in the loop, set the refusal.

Repeat reads are the other lever. Curviate answers a person-profile read inside its 12-hour default from a per-workspace store, and serves stored chats and messages at any age, refreshing them when a message event says they changed. Stored answers make no LinkedIn request and spend none of the account's action budget, leaving more of it for the actions that matter (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's cached profile visits cost 0 credits. Linked API documents caching for conversations only.

How was this comparison made?

Every competitor fact comes from the vendor's own pages, docs, API specs, GitHub and npm, read on October 2, 2026. "Not published" describes the page, not the product. I did not run paid trials of the competitors. Curviate is my product; weigh its rows accordingly. Check each pricing page before buying.

Where does Curviate fit among LinkedIn MCP servers?

Curviate sits with the action servers, built for an agent that already plans the work and needs actions, not a second planner: LinkedIn search, messages, invitations and posts as tools, the same calls in the CLI and API, EUR 20 per account per month, excl. VAT. If your work is campaigns, HeyReach, Botdog or Dripify fit better. Not affiliated with LinkedIn Corporation.