# 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. Source: https://elaichi.ai/connectors/linkedinpersonal/ ## Facts | | | | --- | --- | | Application | LinkedIn Personal | | Category | Marketing Automation | | AI tools | 8 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once LinkedIn Personal is connected - 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 ## Connect LinkedIn Personal in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick LinkedIn Personal. 2. Optionally set Share with, then press Connect. 3. Approve it in LinkedIn Personal. LinkedIn Personal's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which LinkedIn Personal tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## LinkedIn Personal MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect LinkedIn Personal to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a LinkedIn Personal tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with LinkedIn Personal through Elaichi ### Publish the campaign post on schedule Marketing. 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. ### Share a case study as a document Sales. Attach the customer PDF and a short intro, and the agent publishes it as a document post your prospects can flick through on LinkedIn. ### Turn meeting notes into a founder update Leadership. 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. ### Announce an opening with a video Recruiting. Upload the team's short clip and a few lines about the role. The agent finalizes the video and posts it to your profile. ### Fix a live post without starting over Communications. 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. ### Celebrate a customer win with a photo Customer Success. Share the launch photo and a thank-you to the customer team, published to your LinkedIn Personal profile while the moment is still fresh. ## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 my team share one LinkedIn Personal connection? Yes. One person connects LinkedIn Personal in Elaichi and shares the connection with a team, and nobody else ever handles a LinkedIn credential. Each teammate still signs in to Elaichi as themselves, so every post published through the shared LinkedIn Personal connection is recorded in the audit log under the name of the person who asked for it. ### 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. ## All 8 LinkedIn Personal tools Every tool below is callable through https://api.elaichi.ai/mcp once LinkedIn Personal is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all LinkedIn Personal me** (List). Get the connected member's OpenID Connect profile from LinkedIn's userinfo endpoint. Takes no input. LinkedIn returns one object, so the result is a list with one item. Use `sub` to build the member's person URN, `urn:li:person:{sub}`. `email` and `email_verified` are optional claims and can be missing. - **Create a LinkedIn Personal post** (Create). Publish a post to the connected member's own LinkedIn feed. The author is set for you to `urn:li:person:{sub}`; do not send `author`. Send `commentary` and a `visibility` of PUBLIC (default) or CONNECTIONS. For media, upload first with images.create, videos.create then videos.complete, or documents.create, and pass the URN in `content.media.id`. For a link preview send `content.article`. Returns `id`, the new post URN, copied from LinkedIn's `x-restli-id` response header. Pass it unchanged to posts.update and posts.delete. - **Update a LinkedIn Personal post by ID** (Update). Edit one of the connected member's posts by its URN. Send only the fields to change, as flat fields. Truto builds LinkedIn's partial-update request from them (a POST with `X-RestLi-Method: PARTIAL_UPDATE` and a `{"patch": {"$set": {...}}}` body). LinkedIn lets these fields change: commentary, contentCallToActionLabel, contentLandingPage and lifecycleState. Sponsored-content fields are not exposed. Pass `id` as the plain post URN, such as urn:li:share:6844785523593134080. Truto URL-encodes it. Send at least one field. Returns an empty 204 on success. - **Delete a LinkedIn Personal post by ID** (Delete). Delete one of the connected member's posts by its URN. Pass `id` as the plain post URN, such as urn:li:ugcPost:12345 or urn:li:share:12345. Truto URL-encodes it. Deletion is idempotent: deleting a post that is already gone still returns an empty 204. Required: id. - **Create a LinkedIn Personal image** (Create). Start an image upload for the connected member (LinkedIn's initializeUpload action). Send no body: the owner is set for you to `urn:li:person:{sub}`. Returns `value.uploadUrl`, `value.uploadUrlExpiresAt` and `value.image`, the image URN to use in posts.create as `content.media.id`. This call only registers the image. Upload the file yourself, outside Truto, by sending a PUT of the binary to `uploadUrl` with the member's bearer token. JPG, GIF and PNG, under 36,152,320 pixels; GIFs up to 250 frames. - **Create a LinkedIn Personal video** (Create). Start a multipart video upload for the connected member (LinkedIn's initializeUpload action). Send `initializeUploadRequest` with `owner` (`urn:li:person:{sub}` from me.list) and `fileSizeBytes`. Returns the video URN, `uploadInstructions` (one `uploadUrl`, `firstByte` and `lastByte` per 4 MB part) and `uploadToken`. Upload each part yourself, outside Truto, with a PUT of its bytes to its `uploadUrl`, and keep the `ETag` response header of each part. Then call videos.complete. MP4 only, 3 seconds to 30 minutes, 75 KB to 500 MB. - **LinkedIn Personal videos complete** (Complete). Finish a multipart video upload (LinkedIn's finalizeUpload action) after every part has been uploaded. Send `finalizeUploadRequest` with `video` (the URN from videos.create), `uploadToken`, and `uploadedPartIds` (the ETag of each part, in part order). Returns an empty 200 on success. The video then processes asynchronously before it can be used in a post. - **Create a LinkedIn Personal document** (Create). Start a document upload for the connected member (LinkedIn's initializeUpload action). Send no body: the owner is set for you to `urn:li:person:{sub}`. Returns `value.uploadUrl`, `value.uploadUrlExpiresAt` and `value.document`, the document URN to use in posts.create as `content.media.id` (with a `title`). This call only registers the document. Upload the file yourself, outside Truto, by sending a PUT of the binary to `uploadUrl` with the member's bearer token. PPT, PPTX, DOC, DOCX or PDF, up to 100 MB and 300 pages.