LinkedIn Plugin for Claude: What It Is and How to Add One

If you searched for a LinkedIn plugin for Claude and found nothing called a plugin, that is not your mistake. It is a naming mismatch, and clearing it up takes one sentence: “plugin” is what people call it, “connector” is what Claude’s own menu calls it, and “MCP server” is what the developer who built it calls it. Three words, one thing. Once that is settled, the rest of this page is straightforward.

Why does Claude call it a connector and not a plugin?

The word “plugin” comes from an older era of software add-ons. ChatGPT used it for a while, WordPress still does, and it stuck in people’s heads as the general word for “an extra piece that gives the software a new ability”. So when someone wants Claude to handle their LinkedIn posting, “LinkedIn plugin” is the phrase that comes to mind first.

Claude’s interface uses a different label. In Claude’s settings you will find Connectors, and inside that, the option to add a custom connector. That is the box you need. There is no “Plugins” section to hunt for, which is exactly why people search for one and come up empty.

Underneath both words sits the real technology: MCP, the Model Context Protocol — an open standard for connecting AI assistants to outside tools and services. An MCP server is a small service that speaks that standard. It publishes a list of actions it can perform, and the AI assistant calls them when you ask for something. LinkedIn publishes no official one, so every LinkedIn MCP server you find is built by a third party.

So if one page tells you to “add the MCP server URL” and another tells you to “add a custom connector”, they are giving you the same instruction in two different vocabularies.

What can Claude actually do with LinkedIn once a plugin is added?

On its own, Claude cannot touch LinkedIn at all. It will happily write you a post and show it in the chat window, but publishing means you copy the text, open LinkedIn, and paste. A connector removes that last step by giving Claude a set of named actions it can call on your behalf.

With Kalovio connected, the actions Claude gains include:

• Publish a post now — after showing you a preview and waiting for your approval.
• Schedule a post for a specific date and time, up to a year ahead.
• Run a weekly queue — set your posting slots once, then hand it a batch of posts and it spaces them out.
• Save and edit drafts, so a half-finished post survives between chats.
• Attach images — one image, or 2 to 9 images as a swipeable post.
• Post a PDF or document carousel — the slide-style posts people swipe through.
• Tag company pages and other Kalovio users as real clickable mentions, not plain text.
• Remember your writing voice in a saved profile, so drafts sound like you rather than like a press release.
• Track link clicks on links inside your posts.
• Delete a post that Kalovio published.

In practice you type something like “write a short post about what we learned moving Northwind off spreadsheets, then schedule it for Tuesday at 9am”. Claude drafts it, shows you the exact text and the exact time, and stops. Nothing goes out until you say yes.

Is there a free LinkedIn plugin for Claude?

Kalovio is free during its public beta. No card, no trial countdown, no paid tier holding back the posting features. Pricing may change after beta — it would be dishonest to promise otherwise — but nothing is charged today.

Two things people often mix up are worth separating:

• You do not need Claude Pro. Custom connectors work on Claude’s free plan. This surprises people, because the equivalent feature in ChatGPT does sit behind a paid plan.
• You do not need a paid LinkedIn account. The two LinkedIn products this is built on — “Sign In with LinkedIn” and “Share on LinkedIn” — are free and self-serve. No Premium, no Sales Navigator, no partner status.

How do I add the LinkedIn plugin to Claude?

The short version is three steps, and it takes about as long as reading them:

• In Claude, open Settings, then Connectors, then Add custom connector.
• Paste the URL https://kalovio.com/mcp.
• Approve the two sign-in screens that follow — one for Claude to reach Kalovio, one on LinkedIn’s own page giving Kalovio permission to post for you.

That LinkedIn screen is the one worth reading rather than clicking past. It is LinkedIn’s page, not ours, and it names the permission being requested: w_member_social (the scope that allows publishing posts on your behalf, and nothing else). You can take it back later from your LinkedIn settings without changing your password.

The full walkthrough — exact menu wording, what each consent screen says, and what to do if the connector never appears — lives on its own page so this one stays a plain explanation. See how to connect LinkedIn to Claude for the step-by-step, and the connector not showing up if something goes sideways.

What can a LinkedIn plugin for Claude not do?

This is the section most product pages leave out, which is a good reason to put it in the middle rather than the footer. These limits come from LinkedIn’s rules about what self-serve apps may do, not from a feature someone forgot to build.

• It cannot read posts it did not create. The permission for reading your existing LinkedIn activity, r_member_social, is closed to self-serve apps. So Claude cannot review your back catalogue or summarise your feed.
• There are no engagement analytics. No likes, comments, impressions or follower charts. That data needs LinkedIn’s partner-gated Community Management API. Kalovio tracks clicks on links inside your posts, which is useful but is a narrower measure.
• You reconnect roughly every 60 days. LinkedIn member tokens expire around that mark, and self-serve apps get no refresh token to renew them quietly. Kalovio tells you and hands you a reconnect link.
• No messages, no connection requests, no lead scraping. None of that is possible through this permission, and Kalovio does not try to reach it another way.
• Document and PDF posts cannot be scheduled yet — they publish immediately. Text and image posts schedule fine.
• You cannot drop an image into the Claude chat and have it reach the connector. Claude has no route for handing a chat attachment to a connector. You upload images through Kalovio’s upload panel or its browser upload link instead.
• Posts cap at 3000 characters, files at 20 MB each, 100 files per account, kept for 30 days.

Are there other LinkedIn plugins for Claude?

There are other LinkedIn MCP servers, but most are not built for posting — which matters a great deal if publishing is why you came looking.

• The most visible one on Google, stickerdaniel/linkedin-mcp-server, is a scraper that drives a logged-in browser session. Its README states plainly that it “does not publish or create posts on your behalf”, and warns that accounts “can be restricted or banned”.
• Apify and Bright Data offer LinkedIn MCP endpoints for data extraction — pulling information out, not putting posts in.
• Zapier’s LinkedIn MCP exposes roughly two actions.
• Taplio’s own page says its MCP is “text-only... you cannot upload images, video, or PDF carousels”.
• ContentIn’s LinkedIn MCP server does not exist yet — it is described as currently in build, with a waitlist.
• LinkedIn itself publishes no official MCP server.

So the real split is between tools that read LinkedIn by scraping it and tools that write to LinkedIn through the official API. Different jobs, different risks. It is worth knowing which one you are about to add.

Is using a LinkedIn plugin against LinkedIn’s rules?

That approval step is a security feature as well as a courtesy. Publishing, scheduling, queueing and deleting all work in two stages: the first call returns a preview plus a signed token covering the exact content, and nothing happens until a second call arrives with your confirmation and a matching token. If a web page Claude read tried to smuggle in an instruction to post something, it would fail that gate. Your LinkedIn token itself is encrypted on the backend and is never passed to the AI.

The short version

A LinkedIn plugin for Claude is a custom connector, which is an MCP server, and one that can genuinely publish sits at https://kalovio.com/mcp. It is free in beta, works on the free plan, posts through LinkedIn’s official API rather than by borrowing your browser session, and asks you to approve every post before it goes out. It cannot read your old posts or show engagement numbers, because LinkedIn does not permit that for self-serve apps. Those are the honest boundaries, and they are easier to work with when you know them upfront.