LinkedIn Personal MCP connector
The LinkedIn Personal connector lets Claude, ChatGPT, Cursor or the Elaichi Agent draft, publish, edit and remove posts on your LinkedIn profile, with images, videos and documents attached, under your own LinkedIn sign-in and a full audit log.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect LinkedIn Personal to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect LinkedIn Personal once
-
Open Connections, choose Add connection, and pick LinkedIn Personal.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in LinkedIn Personal. LinkedIn Personal's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
LinkedIn Personal MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
LinkedIn Personal MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
LinkedIn Personal MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect LinkedIn Personal to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with LinkedIn Personal through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Publish the campaign post on schedule
Hand the agent the approved copy and the hero image, and the post goes live on your LinkedIn Personal profile without copying text between tabs.
-
Sales
Share a case study as a document
Attach the customer PDF and a short intro, and the agent publishes it as a document post your prospects can flick through on LinkedIn.
-
Leadership
Turn meeting notes into a founder update
Paste the notes from the all-hands and ask for a post in your voice. Review the draft, then publish it to LinkedIn Personal in one step.
-
Recruiting
Announce an opening with a video
Upload the team's short clip and a few lines about the role. The agent finalizes the video and posts it to your profile.
-
Communications
Fix a live post without starting over
Spot a wrong date or a typo after publishing and ask the agent to correct that LinkedIn Personal post in place, keeping the original link.
-
Customer Success
Celebrate a customer win with a photo
Share the launch photo and a thank-you to the customer team, published to your LinkedIn Personal profile while the moment is still fresh.
Try asking
- “Draft a post announcing our Thursday webinar and publish it”
- “Fix the typo in yesterday's post about the product launch”
- “Post the new case study PDF with a short intro”
Compare
Elaichi vs Zapier MCP vs Composio for LinkedIn Personal
All three can connect LinkedIn Personal to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over LinkedIn Personal tools | Allow or restrict single LinkedIn Personal tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per LinkedIn Personal call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
LinkedIn Personal tools for your AI agents
8 tools are ready to call through Elaichi's MCP endpoint the moment you connect LinkedIn Personal, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting LinkedIn Personal gets you
6 screens from the product, each doing one job for your LinkedIn Personal account.
The agent
Draft and publish LinkedIn Personal posts by asking.
Three starter prompts turn a plain request into a published post or a quick edit.
- posts
- images
- videos
- documents
Ask Elaichi to work across your apps.
Draft a post announcing our Thursday webinar and publish it
Fix the typo in yesterday's post about the product launch
Post the new case study PDF with a short intro
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts LinkedIn Personal in every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
8 LinkedIn Personal tools, ready without writing code.
Posts, images, videos and documents are covered, with every method listed in the catalog.
- List all LinkedIn Personal me
- Create a LinkedIn Personal post
- Update a LinkedIn Personal post by ID
- Delete a LinkedIn Personal post by ID
Toolboxes
Every team gets its own LinkedIn Personal toolbox.
Marketing publishes, Recruiting announces openings, each team scoped to the work it does.
- Marketing
- Sales
- Leadership
- Recruiting
Shared connections
Teammates post through one connection, never see credentials.
The connections table shows who connected each account and which teams and members use it.
- Marketing
- Founder
- Sales EMEA
- Recruiting
Audit log
Every published post traces back to a person.
The log records when, who, what happened, type and resource for every call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns recent posts into a digest.
Posts are fetched, grouped and drafted into a digest a person approves before it publishes.
LinkedIn Personal digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch posts
LinkedIn Personal
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
LinkedIn Personal
Queued
Collections and dashboards
Post volume by team, refreshed without being asked.
Four metrics, a 14 day chart of posts created and a team breakdown, no model involved.
LinkedIn Personal health
Refreshed 4 minutes ago · every 15 minutes · from the posts collection
Posts
1,284 ↓ 12%
Images
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Posts created
Last 14 days
By team
Share of activity
Marketing 34%
Founder 27%
Sales EMEA 21%
Recruiting 18%
FAQ
Frequently asked questions
How do I connect LinkedIn Personal to Claude?
Connect LinkedIn Personal in Elaichi first: you are sent to LinkedIn's normal sign-in page, approve access, and come back. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can work with your LinkedIn Personal profile.
Does LinkedIn Personal work with ChatGPT and Cursor as well as Claude?
Yes. The LinkedIn Personal connection you make in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect LinkedIn Personal once and every client picks it up.
What can an AI agent actually do with my LinkedIn Personal account?
With LinkedIn Personal connected, an agent can look up your own profile, write and publish a post, edit a post you already published, and delete one. It can also attach an image, a video or a document such as a PDF to a post. Short, concrete asks work best, for example "post this photo with a two-line caption" rather than a long paragraph of instructions.
Does connecting LinkedIn Personal give the AI access to more than my own profile?
No. LinkedIn Personal access follows the person who signed in, so the agent can only post, edit and delete on that person's own profile, exactly as they could themselves on LinkedIn. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what LinkedIn already allows the signed-in person.
Can I stop an agent from deleting or changing posts in LinkedIn Personal?
Yes. Restrictions in Elaichi work per action, so you can allow publishing to LinkedIn Personal while blocking edits or deletions. A restricted action is left out of the list the AI client receives, so it cannot be called no matter how the prompt is worded.
What happens to a LinkedIn Personal connection when someone leaves?
Offboarding that person in Elaichi ends their access to LinkedIn Personal and every other connected application at once. A LinkedIn Personal connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting LinkedIn Personal once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the LinkedIn Personal MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. LinkedIn Personal is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for LinkedIn Personal?
Yes. Both let Claude, ChatGPT or Cursor use LinkedIn Personal. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LinkedIn Personal call.
How is Elaichi different from Composio for LinkedIn Personal?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LinkedIn Personal: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put LinkedIn Personal in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.