Kasar

MCP server

LinkedIn MCP server: your LinkedIn conversations inside Claude and ChatGPT

Kasar gives Claude, ChatGPT or Cursor access to your LinkedIn conversations through a remote MCP server at https://platform.kasar.app/api/mcp/mcp. The assistant signs in to Kasar with OAuth 2.1, your LinkedIn account is linked once inside Kasar through the Chrome extension, and every message goes through a preview before it leaves.

Facts checked on October 6, 2026

01What the assistant does with LinkedIn

Once connected, the assistant reads your LinkedIn conversations live, pulls the history already recorded on a record, adds the person from a conversation to the CRM and drafts replies it shows you before sending. It works with your LinkedIn account and your role in Kasar: whatever you cannot see in the CRM stays out of its reach too.

Seven of the server’s 39 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.

crm_conversations

What it does on LinkedIn
Lists your live LinkedIn conversations and opens their messages, page by page.
Writes?
No, read only

crm_inbox

What it does on LinkedIn
Reads back the LinkedIn threads the CRM has already recorded.
Writes?
No

crm_find_activity

What it does on LinkedIn
Shows the history of a contact or company, filtered to LinkedIn.
Writes?
No

crm_sync_participant

What it does on LinkedIn
Creates or finds the person’s record, links their company and imports the history.
Writes?
Yes, never deletes

crm_send_message

What it does on LinkedIn
Replies in a conversation, or opens one with a contact whose profile is linked.
Writes?
Yes, after preview and confirmation

crm_manage_integrations

What it does on LinkedIn
Tells whether your LinkedIn account is connected.
Writes?
No

crm_manage_emails_phones

What it does on LinkedIn
Links or replaces the LinkedIn profile on a record.
Writes?
Yes

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.

02How 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.

03Add the Kasar connector to Claude

  1. 1

    Add a custom connector

    In Claude, open Customize, then Connectors, and pick “Add custom connector”. Give it a name, paste the URL above and save without changing anything else.

  2. 2

    Grant access to your workspaces

    The Kasar consent page opens. Tick at least one workspace, choose the default one, then click Authorize. The client registers itself, so there is no key to copy.

  3. 3

    Check the channel

    Ask “is my LinkedIn account connected to Kasar?”. The assistant reads the connection status and answers yes or no.

The assistant connects with OAuth 2.1 and PKCE. The token lasts 90 days, shows up in your list of keys and can be revoked at any time. That protocol links the assistant to Kasar; your LinkedIn session is the extension’s business. In ChatGPT, the same URL goes in as a custom MCP app, under Apps, Create. In ChatGPT, sending and other write actions need full MCP, in beta for Business, Enterprise and Edu plans, on the web, as of 6 October 2026; on Pro, ChatGPT reads only. For Claude Code or Cursor, create a key under Settings, MCP tab, and send it in the Authorization header instead. The full walkthrough is in the Claude and LinkedIn tutorial.

On Claude’s side, custom connectors are open on every plan, the free plan included, which allows one. On Team and Enterprise, organisation owners add them (Claude help centre, read on 6 October 2026).

04Five prompts to copy

  1. 1

    “Which LinkedIn conversations this week came from people who are not in the CRM?”

    The assistant lists your conversations with crm_conversations, keeps those whose status says no record exists, then offers to add them one by one.

  2. 2

    “Summarise my LinkedIn exchanges with Claire Martin and tell me where her deal stands.”

    Global search finds the record, crm_find_activity filters the history to LinkedIn, and the linked opportunity gives the pipeline stage.

  3. 3

    “Add the person from my latest conversation to the CRM, in the VivaTech list.”

    crm_sync_participant gets the LinkedIn member id returned by the read: the record is created or matched without a duplicate, the company enriched, the history imported, the list filled.

  4. 4

    “Tell Julien that Thursday at 10 works for me. Show me the message first.”

    crm_send_message runs as a preview. You read it, you say yes, and the assistant sends it with the confirmation token.

  5. 5

    “Is my LinkedIn account still connected to Kasar?”

    crm_manage_integrations returns the channel status. If it dropped, the assistant tells you to reconnect from Chrome.

05A preview before every send

A LinkedIn message cannot be unsent, so the server works in two steps. On the first call the send 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 or the recipient changes after the preview, the send is refused and a new preview is needed.
  • Duplicates : an identical send repeated within a short window goes out once.
  • Pace : the server accepts at most 30 message sends per hour per user.
The assistant drafts, you decide, Kasar sends.

06LinkedIn’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’s send tool does not send invitations; it can, however, 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 a week) and 80 messages a day. 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. 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.

07Is there an MCP server published by LinkedIn?

We did not find any MCP server published by LinkedIn in its developer documentation as of 6 October 2026. The “LinkedIn MCP” servers on GitHub and in directories are independent projects with no tie to LinkedIn. What sets Kasar apart is less the protocol than the destination: your sales conversations land on CRM records, next to emails, calls and the deal, and the assistant works there with your permissions.

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

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.

Not with the message tool. It can build an automation containing the “LinkedIn connection request” block, dry-run it, then publish it once you confirm. Your account caps apply to those invitations as well.

Yes, with one caveat for ChatGPT. It takes the same URL as a custom MCP app, with the same OAuth sign-in, but sending and other write actions there need full MCP, in beta for Business, Enterprise and Edu plans, on the web, as of 6 October 2026; on Pro, ChatGPT reads only. Claude Code and Cursor use an MCP key created under Settings, MCP tab, carrying your own permissions and the workspaces you tick.

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.

Kasar, the CRM that prospects, follows up and fills itself in.

  • It captures.

    Emails, LinkedIn, WhatsApp, calls and meetings land on the record, with no data entry.

  • It acts.

    Tasks, meeting notes, follow-ups: the CRM keeps itself current and tells you what to do next.

  • It prospects.

    One sequence chains email, LinkedIn and WhatsApp. The reply lands on the record, next to the deal.

  • It takes your shape and connects to everything.

    Your objects, your fields, your relationships. Everything else goes through webhooks, the API and the MCP server.

See every feature

Read next

See what it looks like on your own data

14-day free trial. Or spend 30 minutes with us on your pipeline.

Start for free