LinkedIn MCP server: connect Claude and ChatGPT to your LinkedIn messages
Kasar gives Claude (claude.ai and Claude Desktop), ChatGPT, Cursor or Claude Code access to your LinkedIn conversations and network through a remote MCP server at https://platform.kasar.app/api/mcp/mcp. Your LinkedIn account is linked once inside Kasar through the Chrome extension, with your own session; the assistant signs in to Kasar with OAuth 2.1; every message and every invitation goes through a preview before it leaves.
- Server address
https://platform.kasar.app/api/mcp/mcp- With Claude, ChatGPT, Cursor and Claude Code
- With Claude, ChatGPT, Cursor and Claude Code
Facts checked on October 16, 2026
You : Find Camille Durand, sales director at Exemple SA, and invite her with a note about our chat at the trade show.
crm_linkedin_network3 profiles found
Three profiles match. Which one is right?
- 1Camille DurandSales director · Exemple SA · 2nd degree
- 2Camille DurandConsultant · Lyon · 3rd degree
- 3Camille DurantPurchasing manager · Exemple Group · 3rd degree
You : The first one.
crm_linkedin_importRecord created, linked to Exemple SAcrm_linkedin_invitePreview, nothing sent
Here is the invitation. Shall I send it?
- To
- Camille Durand, Exemple SA
Hi Camille, great talking with you at the trade show on Thursday. I would be glad to stay in touch here.
Note of 200 characters at most · confirmation valid for 5 minutes
A LinkedIn MCP server is what lets an AI assistant such as Claude or ChatGPT read and act on your LinkedIn account through the Model Context Protocol. The only MCP connector published by LinkedIn that we found as of 1 November 2026, LinkedIn Hiring Pro, posts one free job; for your messages and invitations, the server comes from elsewhere. Kasar is one, tied to your CRM.
What the assistant does with LinkedIn
Once connected, the assistant reads your LinkedIn conversations live, pulls the history already recorded on a record, looks a person up in your network, adds them to the CRM, sends them an invitation and drafts replies it shows you before sending. Kasar acts on your behalf, with your LinkedIn session and your role in the CRM: whatever you cannot see in Kasar stays out of the assistant’s reach too.
Ten of the server’s 42 tools touch LinkedIn. The server keeps live reading, recorded history and action apart, so the assistant never mistakes a conversation it can see for one the CRM has stored.
| Tool | What it does on LinkedIn | Writes? |
|---|---|---|
| Lists your live LinkedIn conversations and opens their messages, page by page. | ReadNo, read only |
| Reads back the LinkedIn threads the CRM has already recorded. | ReadNo |
| Shows the history of a contact or company, filtered to LinkedIn. | ReadNo |
| Creates or finds the person’s record, links their company and imports the history. | WriteYes, never deletes |
| Replies in a conversation, or opens one with a contact whose profile is linked. | WriteYes, after preview and confirmation |
| Tells whether your LinkedIn account is connected. | ReadNo |
| Links or replaces the LinkedIn profile on a record. | WriteYes |
| Looks a person up (ten candidates at most, you pick the right one), gives the relationship status with a contact, lists pending or accepted invitations and remaining quotas. | ReadNo, read only |
| Sends an invitation to a CRM contact whose profile is linked, with a note of up to 200 characters. | WriteYes, after preview and confirmation |
| Adds the chosen profile to the CRM, or links it to an existing record, without overwriting any value. | WriteYes, never overwrites |
Every live conversation carries a link status: the person has no record, has one, or the exchange is already stored. The assistant uses it to suggest adding a stranger to the CRM, and never does it behind your back.
How your LinkedIn account connects to Kasar
LinkedIn is not connected from the chat with the assistant. You link it once, inside Kasar, with the Kasar Chrome extension: it reads the LinkedIn session open in your browser and hands it to your Kasar account. That takes three things: Google Chrome, the extension, and a signed-in session on linkedin.com in that same Chrome. When the extension recognises the account, the button shows your name and photo so you can check it is the right one.
Before you confirm, Kasar asks what should enter the CRM. By default only the conversations you add yourself are recorded, plus those with people who already have a record. Three other modes exist: every conversation, people you wrote to, people who replied. You set this in the app, never from the assistant.
Connect Claude and ChatGPT to LinkedIn, step by step
Is your LinkedIn account linked in Kasar? Then all that is left is to introduce Kasar to the assistant. The same URL works everywhere; only the path changes from one client to the next. The tutorial to connect Claude to LinkedIn walks the same route from the assistant’s side, with five prompts to copy.
- 1
Claude on the web (claude.ai)
- 1Open Customize, then Connectors, click “+ Add”, then “Add custom connector”.
- 2Enter a name, Kasar, and paste the server URL. Continue.
- 3Let Claude detect the Kasar OAuth settings. If the screen asks which OAuth client to use, choose “Register automatically”, then Add.
- 4On the Kasar consent page, tick the workspaces to open, pick the default one, then Authorize. The token lasts 90 days and can be revoked from Kasar at any time.
- 5In a conversation, “+” button, Connectors: switch Kasar on.
According to Claude’s help centre, checked on 16 October 2026, custom connectors are open on every plan, and Free allows one. On Team and Enterprise, an owner adds Kasar in the organisation settings, then each member clicks Connect. The same page advises choosing “Allow always” only for tools you trust: keep manual approval on crm_send_message and crm_linkedin_invite.
- 2
Claude Desktop
The desktop app picks up the remote connectors of your Claude account: the help centre lists them as available in Claude, Cowork and Claude Desktop, configured and brokered through the account. The path is the same, Customize then Connectors. No desktop extension to install: those are for local servers, and Kasar is a remote one.
- 3
ChatGPT
On chatgpt.com, open Plugins, click “+”, then “Add custom MCP server”. Give it a name, paste the URL under Connection, choose OAuth authentication, tick “I understand and want to continue”, then “Create as a plugin”. Once the plugin is installed, type @ in a new conversation and pick Kasar. According to OpenAI’s help centre, checked on 16 October 2026, full MCP, write actions included, is open to Business, Enterprise and Edu plans, on the web only; on Business, an admin or owner creates the connection. On Pro, a custom server connects read-only: ChatGPT reads your conversations, and sends go out from Claude or from Kasar.
- 4
Cursor and Claude Code
For a client installed on your computer, create a key in Kasar under Settings, MCP tab, and send it in the Authorization header. It carries your own permissions, on the workspaces you tick, and expires on the date you choose.
Check everything with one question: “Is my LinkedIn account connected to Kasar, and how many invitations do I have left today?” crm_manage_integrations gives the channel status, crm_linkedin_network the quotas. The assistant-side walkthrough, screen by screen, is also in the Claude and LinkedIn tutorial.
What you can ask the agent
You : “Which LinkedIn conversations this week came from people who are not in the CRM?”
crm_conversations
What the assistant does : crm_conversations lists your conversations; the assistant keeps those whose status says no record exists, then offers to add them one by one.
You : “Open my conversation with Julien and tell me what he needs from me.”
crm_conversations
What the assistant does : crm_conversations opens the messages; the assistant sums up the request and suggests a reply, without sending it.
You : “Summarise my exchanges with Claire Martin, LinkedIn and email, and tell me where her deal stands.”
crm_find_activity
What the assistant does : Global search finds the record, crm_find_activity gathers the history, and the linked opportunity gives the pipeline stage.
You : “Find Camille Durand, sales director at Example Ltd, on LinkedIn.”
crm_linkedin_network
What the assistant does : crm_linkedin_network returns up to ten profiles, with headline, location, connection degree and any CRM link. You point to the right one; the assistant never picks for you.
You : “Add her to the CRM and send her an invitation that mentions our chat at the trade show.”
crm_linkedin_import
crm_linkedin_invite
What the assistant does : crm_linkedin_import creates the record, then crm_linkedin_invite returns a preview of the invitation and its note, 200 characters at most. The invitation goes once you say yes.
You : “Which invitations were accepted since I last checked?”
crm_linkedin_network
What the assistant does : crm_linkedin_network lists accepted invitations and those still pending. You can follow up with “write each of them a thank-you note, one at a time, showing me every text”.
You : “Tell Julien that Thursday at 10 works for me. Show me the message first.”
crm_send_message
What the assistant does : crm_send_message runs as a preview. You read it, you say yes, and the assistant sends it with the confirmation token.
You : “Build an automation that invites every contact added to the Webinar list, then messages them.”
crm_manage_automations
What the assistant does : crm_manage_automations writes the flow, dry-runs it and publishes it only once you confirm.
You : “How many invitations can I still send this week?”
crm_linkedin_network
What the assistant does : crm_linkedin_network reads your counters for today and this week, against the caps set on your account.
A preview before every send
A LinkedIn message or invitation cannot be taken back, so the server works in two steps. On the first call the tool sends nothing: it returns the exact text, the recipient and a confirmation token. Sending takes a second call with that token. The assistant is instructed to show you the preview and wait for your yes before that second call, and Claude or ChatGPT also ask you to approve the call, depending on your settings.
- Lifetime : the token expires after 5 minutes and works once.
- Binding : it is tied to the message. If the text, the note or the recipient changes after the preview, the send is refused and a new preview is needed.
- Duplicates : an identical send repeated within 60 seconds goes out once.
- Pace : at most 30 sends per hour per user, invitations included, and 15 to 30 seconds between two of the assistant’s LinkedIn actions on one account.
Two calls for one send
- 1
previewNothing goes out. The server returns the exact text, the recipient and a confirmation token.crm_send_message
- 2You“Yes, send it.”
- 3
with the tokenThe message goes out. The token, valid for 5 minutes, cannot be used again.crm_send_message
The assistant drafts, you decide, Kasar sends.
LinkedIn’s rules stay LinkedIn’s
From Kasar, a direct message only goes to a first-degree connection; for anyone else, an invitation comes first. The assistant sends it with crm_linkedin_invite, after a preview, then writes once the invitation is accepted. It can also write an automation that chains an invitation and a message, dry-run it and publish it once you confirm.
Kasar counts every action taken with your account and stops before its own caps: by default 20 invitations a day (80 over a rolling seven days), 80 messages a day, 60 profile views a day and 600 searches a month. Those thresholds are set by Kasar: you can lower them, or raise them up to a maximum Kasar also sets; they are not limits published by LinkedIn. When a cap is reached, the server tells you when to resume. LinkedIn, for its part, publishes the software and practices it prohibits, unauthorised automation among them, and can restrict an account whose activity looks abnormal. Keep volumes human and read what the assistant drafts.
Limits worth knowing
- Connecting takes Google Chrome, the Kasar extension and a signed-in session on linkedin.com; it cannot be done from the conversation.
- The tools cover messaging, invitations, people search and profile import. Publishing posts and reading the feed are not part of them.
- Messages sent by the assistant are text, without attachments.
- The live read goes through conversations page by page, without keyword search; for an older exchange, go through the contact’s record.
- An invitation targets a CRM contact whose LinkedIn profile is linked; crm_linkedin_import takes care of that in one request.
- In ChatGPT, sending a message or an invitation needs a Business, Enterprise or Edu plan, on the web.
Other LinkedIn MCP servers
The only MCP server published by LinkedIn that we found as of 1 November 2026 is the LinkedIn Hiring Pro connector, added to Claude’s directory in October 2026, which drafts and posts one free job. For messaging and invitations, we found no server published by LinkedIn, neither in that directory as of 1 November 2026 nor in its API documentation as of 16 October 2026. LinkedIn’s API documentation covers the Consumer, Learning, Marketing, Talent, Sales and Compliance lines, with no mention of MCP. The “LinkedIn MCP” servers in directories and on GitHub are independent projects.
| Route | What it does with LinkedIn | What it takes to connect |
|---|---|---|
| LinkedIn Hiring Pro, published by LinkedIn | What it does with LinkedInDraft and post one free job. Its listing rules out paid jobs, editing jobs and managing applicants; it does not mention messaging or invitations. | What it takes to connectThe connector added from Claude’s directory, signed in to your LinkedIn account. |
| linkedin-mcp-server, independent project | What it does with LinkedInProfiles, companies, job posts, messaging, invitations and feed, by driving a real browser session. | What it takes to connectAn install on your machine (uvx, Docker or a Claude Desktop extension). Its repository warns that an account using automated tools can be restricted. |
| What it does with LinkedInReads your conversations, finds a person, adds them to the CRM, invites them and replies, every send after a preview. | What it takes to connectThe Kasar Chrome extension once, then a remote connector in the assistant, over OAuth. LinkedIn from the Pro plan. |
Among them, linkedin-mcp-server, with about 3,900 GitHub stars as of 16 October 2026, describes itself as an independent open-source project, not affiliated with LinkedIn or Microsoft. It installs on your computer (uvx, Docker or a Claude Desktop extension), drives a real browser session and covers profiles, companies, jobs, messaging, invitations and the feed. Its own repository warns that an account using automated tools can be restricted.
What sets Kasar apart is less the protocol than the destination. The server is remote: the assistant reaches it through OAuth, with nothing to install. Your sales conversations land on CRM records, next to emails, calls and the deal, and every send goes through a preview and through your account’s caps.
LinkedIn comes with the Pro plan, which includes one social account of your choice, LinkedIn or WhatsApp. The Max plan includes one LinkedIn and one WhatsApp. The MCP server itself is part of every plan, Free included: see pricing. For what LinkedIn does inside Kasar without an assistant, read the LinkedIn integration page; for every parameter, the messaging tools reference.
Frequently asked questions
Yes, but for hiring. The only one we found as of 1 November 2026 is LinkedIn Hiring Pro, a Claude connector published by LinkedIn in October 2026, which drafts and posts one free job. For messaging, we found none. The “LinkedIn MCP” servers on GitHub and in directories are independent projects. Kasar does not use a LinkedIn API: it acts on your behalf, with your session, through its Chrome extension.
In two steps. First link your LinkedIn account in Kasar with the Chrome extension. Then add Kasar to Claude: Customize, Connectors, “Add custom connector”, the server URL, then authorise your workspaces. The same connector works on claude.ai and in Claude Desktop.
No. The Chrome extension reads the session already open in your browser; you never type LinkedIn credentials into Kasar. Connecting or reconnecting can sometimes sign you out of LinkedIn in Chrome: just sign back in on linkedin.com.
No. LinkedIn is linked through the Chrome extension, inside Kasar. Once it is linked the assistant can check the connection and read your conversations, but it cannot link the account or change your sync settings.
Yes, with crm_linkedin_invite, to a CRM contact whose profile is linked, with a note of up to 200 characters. The tool first returns a preview; the invitation goes once you confirm, within the caps set on your account.
Yes, with one caveat for ChatGPT. It takes the same URL as a custom MCP server, from Plugins, with the same OAuth sign-in, but sending and other write actions there need full MCP, open to Business, Enterprise and Edu plans, on the web, as of 16 October 2026; on Pro, ChatGPT reads only. Claude Code and Cursor use an MCP key created under Settings, MCP tab.
The MCP server is part of every Kasar plan, Free included. The LinkedIn channel itself opens from the Pro plan, and the Max plan adds WhatsApp.
The integration page covers LinkedIn inside Kasar: inbox, invitations, enrichment, sequences. This page covers what an AI assistant can do with that channel through the MCP server, and how to plug it in.
Sources
Every fact on this page can be checked on the official page below, read on the date shown.
- Claude, aide : Get started with custom connectors using remote MCP · read on October 16, 2026
- OpenAI, aide : Connecting custom MCP servers in ChatGPT · read on October 16, 2026
- LinkedIn, documentation API (aucun serveur MCP listé) · read on October 16, 2026
- Claude, répertoire des connecteurs : LinkedIn Hiring Pro (publié par LinkedIn) · read on November 1, 2026
- LinkedIn, aide : Prohibited software and extensions · read on October 16, 2026
- GitHub : stickerdaniel/linkedin-mcp-server (projet indépendant) · read on October 16, 2026
- Kasar, documentation : outils MCP de messagerie · read on October 6, 2026