# LinkedIn MCP connector

The LinkedIn connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent read and update your LinkedIn ad accounts, campaign groups, campaigns and creatives, as the person who signed in, with every action logged.

Source: https://elaichi.ai/connectors/linkedin/

## Facts

| | |
| --- | --- |
| Application | LinkedIn |
| Category | Marketing Automation |
| AI tools | 295 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, 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 is connected

- Which LinkedIn campaigns are active in the EMEA ad account?
- Pause every campaign in the Q3 webinar campaign group.
- List creatives in the product launch campaign and their status.

## Connect LinkedIn in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick LinkedIn.
2. Optionally set Share with, then press Connect.
3. Supply your own LinkedIn app, then approve. LinkedIn needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which LinkedIn tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## LinkedIn 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 MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## LinkedIn 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. The plugin directory lives at chatgpt.com/plugins.

## LinkedIn 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.

## LinkedIn MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect LinkedIn 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 things", which you tick yourself. Calling a LinkedIn tool needs "Use your connected apps". 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 Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with LinkedIn through Elaichi

### Pause a whole campaign group in one ask

Paid media. Ask for every campaign in the webinar campaign group to be paused before the event date moves, and check the list afterwards to confirm nothing is still running.

### See which LinkedIn campaigns are live today

Marketing. Get a plain list of active campaigns across every LinkedIn ad account, with their campaign group and status, without opening Campaign Manager tab by tab.

### Set up a launch campaign group quickly

Demand generation. Create a new campaign group for the product launch, add the campaigns under it, and update budgets and dates as the plan changes.

### Review every client ad account at once

Agency. List all the LinkedIn ad accounts you manage, pull one by name to answer a client question, and update account details when a client renames or restructures.

### Fix creatives pointing to the wrong page

Marketing ops. List the creatives in a campaign, find the ones using a stale landing page, and update them in one pass instead of editing each by hand.

### Keep the ad account list tidy

Finance. Check which LinkedIn ad accounts still exist, confirm each maps to a cost center, and remove accounts that are no longer used so spend is easier to reconcile.

## Elaichi vs Zapier MCP vs Composio for LinkedIn

All three can connect LinkedIn 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 tools | Allow or restrict single LinkedIn 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 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 | Free for one person; $15 per user per month on Gold. | 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 to Claude?

Connect LinkedIn in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. LinkedIn requires an OAuth application registered inside LinkedIn itself, so one person on your team brings that application's client ID and secret once when setting up the connection. After that, each person signs in to LinkedIn through the usual OAuth prompt and nobody else ever handles a credential.

### Does LinkedIn work with ChatGPT and Cursor as well as Claude?

Yes. The LinkedIn connection you set up once in Elaichi works from Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. They all use the same endpoint, https://api.elaichi.ai/mcp, so there is nothing to repeat per client.

### What can an AI agent actually do with my LinkedIn data?

With LinkedIn connected, an agent can list your ad accounts, campaign groups, campaigns and creatives, pull up any one of them, create or update campaign groups and campaigns, and update creatives. In practice that means asking which LinkedIn campaigns are active, pausing a campaign group, or fixing a creative's details without opening Campaign Manager. Short concrete asks, such as naming the campaign group and the change you want, work better than long paragraphs.

### Does connecting LinkedIn give the AI access to all of my ad accounts?

No. Every call to LinkedIn runs as the person who signed in, so the agent only sees the ad accounts, campaign groups and campaigns that person can already see in LinkedIn. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what LinkedIn itself allows.

### Can my team share one LinkedIn connection?

Yes. One person connects LinkedIn in Elaichi and shares the connection with a team, so nobody else needs the OAuth application's client ID or secret. Each teammate still signs in as themselves, so the audit log names the actual person who changed a LinkedIn campaign.

### Can I stop an agent from deleting or changing things in LinkedIn?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting LinkedIn ad accounts or campaign groups for a role or for one person while leaving listing and updating open. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a LinkedIn connection when someone leaves?

Offboarding a person in Elaichi ends their LinkedIn access at once, across every client they used. If they were using a shared LinkedIn connection, it keeps working for everyone else on the team. Disconnecting LinkedIn once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the LinkedIn MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. LinkedIn 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, Microsoft Copilot, 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?

Yes. Both let Claude, ChatGPT or Cursor use LinkedIn. 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 call.

### How is Elaichi different from Composio for LinkedIn?

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: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 295 LinkedIn tools

Every tool below is callable through https://api.elaichi.ai/mcp once LinkedIn is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all LinkedIn me** (List). Get the signed-in member (OpenID Connect userinfo): member id (sub), name, email and picture. GET /v2/userinfo. Needs the openid, profile and email scopes.
- **List all LinkedIn ad accounts** (List). Search the ad accounts the member can access (GET /rest/adAccounts?q=search). Optional search filters by status, type, name, reference or test. Paginated with pageToken.
- **Get single LinkedIn ad account by ID** (Get). Get one ad account by its numeric ID (GET /rest/adAccounts/{id}): name, currency, type, status, owning organization and serving statuses.
- **Create a LinkedIn ad account** (Create). Create an ad account (POST /rest/adAccounts) owned by an organization. Required: name, currency, reference (organization URN) and type. The new ID is returned in the x-restli-id header.
- **Update a LinkedIn ad account by ID** (Update). Update Ad Account. Ad Accounts can be updated through a partial update by patching the fields you want to change. A successful response returns a HTTP status code. LinkedIn POST /rest/adAccounts/{id}. id: URL-encode URNs. Sends X-RestLi-Method PARTIAL_UPDATE. Required: id, patch.
- **Delete a LinkedIn ad account by ID** (Delete). Delete Ad Account. Ad Account can be deleted. Use DELETE method to delete a account. To start the process of deleting non DRAFT account, update the status to . LinkedIn DELETE /rest/adAccounts/{id}. id: URL-encode URNs. Required: id.
- **List all LinkedIn ad campaigns** (List). Search campaigns in an ad account (GET /rest/adAccounts/{ad_account_id}/adCampaigns?q=search). Optional search by status, type, campaignGroup, name or id. Paginated.
- **Get single LinkedIn ad campaign by ID** (Get). Get one campaign (GET /rest/adAccounts/{ad_account_id}/adCampaigns/{id}): budget, bid, schedule, targeting and status. Required: id, ad_account_id.
- **Create a LinkedIn ad campaign** (Create). Create a campaign (POST …/adCampaigns). Required: account, campaignGroup, name, type, costType, dailyBudget or totalBudget, unitCost, locale, runSchedule, targetingCriteria, status.
- **Update a LinkedIn ad campaign by ID** (Update). Partially update a campaign (POST …/adCampaigns/{id} with X-RestLi-Method PARTIAL_UPDATE), e.g. {"patch": {"$set": {"status": "PAUSED"}}}. Required: id, ad_account_id, patch.
- **Delete a LinkedIn ad campaign by ID** (Delete). Delete a DRAFT campaign (DELETE …/adCampaigns/{id}); live campaigns are archived or canceled with update instead. Required: id, ad_account_id.
- **LinkedIn ad campaigns batch get** (Get). Batch-get adCampaigns. Batch Get Campaigns. Multiple campaigns can be fetched in a single call by chaining together multiple . All requested campaigns must belong to the same Ad Account. LinkedIn GET /rest/adAccounts/{ad_account_id}/adCampaigns. Required: ad_account_id, ids.
- **List all LinkedIn ad campaign groups** (List). Search campaign groups in an ad account (GET /rest/adAccounts/{ad_account_id}/adCampaignGroups?q=search). Optional search by status, name, id or test. Paginated.
- **Get single LinkedIn ad campaign group by ID** (Get). Get one campaign group (GET /rest/adAccounts/{ad_account_id}/adCampaignGroups/{id}). Required: id, ad_account_id.
- **Create a LinkedIn ad campaign group** (Create). Create a campaign group in an ad account (POST …/adCampaignGroups). Required: account URN, name, runSchedule.start and status; totalBudget optional.
- **Update a LinkedIn ad campaign group by ID** (Update). Partially update a campaign group (…/adCampaignGroups/{id}) with a Rest.li patch, e.g. {"patch": {"$set": {"status": "PAUSED"}}}. Required: id, ad_account_id, patch.
- **Delete a LinkedIn ad campaign group by ID** (Delete). Delete a DRAFT campaign group (DELETE …/adCampaignGroups/{id}); other statuses must be archived or canceled with update instead. Required: id, ad_account_id.
- **LinkedIn ad campaign groups partial update** (Update). Update a Campaign Group. Campaign groups can be updated with a partial update. LinkedIn POST /rest/adAccounts/{ad_account_id}/adCampaignGroups/{campaign_group_id}. Sends X-RestLi-Method PARTIAL_UPDATE. Required: ad_account_id, campaign_group_id, patch.
- **LinkedIn ad campaign groups batch get** (Get). Batch-get adCampaignGroups. Batch Get Campaign Groups. Multiple campaign groups can be requested in a single call by chaining together parameters that each have a corresponding campaign group ID. LinkedIn GET /rest/adAccounts/{ad_account_id}/adCampaignGroups. Required: ad_account_id, ids.
- **LinkedIn ad campaign groups batch update** (Update). Batch-update adCampaignGroups. Batch Update Campaign Groups. Multiple campaign groups can be updated in a single call. LinkedIn POST /rest/adAccounts/{ad_account_id}/adCampaignGroups. Sends X-RestLi-Method BATCH_PARTIAL_UPDATE. Required: ad_account_id, ids, entities.
- **LinkedIn ad campaign groups batch delete** (Delete). Batch-delete adCampaignGroups. Batch Delete Campaign Groups. Multiple campaign groups can be deleted. Use DELETE method to delete campaign groups. LinkedIn DELETE /rest/adAccounts/{ad_account_id}/adCampaignGroups. Sends X-RestLi-Method BATCH_DELETE. Required: ad_account_id, ids.
- **List all LinkedIn creatives** (List). Search creatives (ads) in an ad account (GET /rest/adAccounts/{ad_account_id}/creatives finder). Filter with campaigns, intendedStatuses, isTestAccount. Paginated.
- **Get single LinkedIn creative by ID** (Get). Get one creative (GET …/creatives/{id}). id is the URL-encoded creative URN, e.g. urn%3Ali%3AsponsoredCreative%3A123. Required: id, ad_account_id.
- **Update a LinkedIn creative by ID** (Update). Partially update a creative (POST …/creatives/{id}, PARTIAL_UPDATE), e.g. {"patch": {"$set": {"intendedStatus": "PAUSED"}}}. id is the URL-encoded creative URN.
- **Create a LinkedIn creative** (Create). Create a creative that sponsors an existing post (POST …/creatives). Required: campaign URN, content.reference (post URN) and intendedStatus.
- **Delete a LinkedIn creative by ID** (Delete). Delete a DRAFT creative (DELETE …/creatives/{id}). id is the URL-encoded creative URN; live creatives are archived with update instead. Required: id, ad_account_id.
- **LinkedIn creatives batch get** (Get). Batch-get creatives. Batch Get Ad Creatives. Fetch a list of Ad Creatives with associated IDs. When you perform a batch create, the header X-RestLi-Method must be included in the request and set to . LinkedIn GET /rest/adAccounts/{ad_account_id}/creatives. Required: ad_account_id, ids.
- **LinkedIn creatives batch update** (Update). Batch-update creatives. Batch Partial Update Ad Creatives. When you perform a batch partial update, the header X-RestLi-Method must be included in the request and set to . LinkedIn POST /rest/adAccounts/{ad_account_id}/creatives. Sends X-RestLi-Method BATCH_PARTIAL_UPDATE. Required: ad_account_id, ids, entities.
- **LinkedIn creatives batch delete** (Delete). Batch-delete creatives. Batch Delete Ad Creatives. Multiple creatives can be deleted. Use DELETE method to delete creatives that meet one of the following conditions. LinkedIn DELETE /rest/adAccounts/{ad_account_id}/creatives. Sends X-RestLi-Method BATCH_DELETE. Required: ad_account_id, ids.
- **LinkedIn creatives create inline** (Create). Creatives Inline Schema. The following tables describe the schemas available for . LinkedIn POST /rest/adAccounts/{ad_account_id}/creatives (action=createInline). Required: ad_account_id.
- **LinkedIn creatives list by criteria** (List). Cursor based Pagination for search APIs. The creatives API implements cursor based pagination using the pageSize and pageToken parameters for search method. The max allowed pageSize is 100. LinkedIn GET /rest/adAccounts/{ad_account_id}/creatives (q=criteria). Required: ad_account_id.
- **List all LinkedIn in mail contents** (List). Batch-get Message Ad (InMail) contents by ID (GET /rest/inMailContents?ids=…). Required: ids, one or more URL-encoded adInMailContent URNs separated as the API expects.
- **Get single LinkedIn in mail content by ID** (Get). Get one Message Ad content (GET /rest/inMailContents/{id}). id is the URL-encoded adInMailContent URN.
- **Create a LinkedIn in mail content** (Create). Create Message Ad content (POST /rest/inMailContents). Required: account, name, subject, sender (person URN), htmlBody and subContent (regular CTA or guidedReplies).
- **Update a LinkedIn in mail content by ID** (Update). Partially update Message Ad content (/rest/inMailContents/{id}) with a Rest.li patch, e.g. {"patch": {"$set": {"subject": "New subject"}}}. id is the URL-encoded URN.
- **LinkedIn in mail contents partial update** (Update). Sample Request. http curl. LinkedIn POST /rest/inMailContents/{in_mail_content_urn}. Sends X-RestLi-Method PARTIAL_UPDATE. Required: in_mail_content_urn, patch.
- **LinkedIn in mail contents send test** (Send). Send Test InMail. The sendTestInMail action can be used to trigger a test message for a draft message or conversation ad. LinkedIn POST /rest/inMailContents (action=sendTestInMail). Required: account.
- **Get single LinkedIn carousel ad by ID** (Get). Get a carousel ad post (GET /rest/posts/{id}). id is the URL-encoded post URN, e.g. urn%3Ali%3Ashare%3A123.
- **Create a LinkedIn carousel ad** (Create). Create a sponsored carousel post (POST /rest/posts) with 2-10 image cards; then sponsor it with creatives.create. Required: author, commentary, visibility, distribution, content.carousel, lifecycleState.
- **Create a LinkedIn text ad** (Create). Create a text ad creative (POST /rest/creatives) in a TEXT_AD campaign: headline, description, landing page and optional image. Required: campaign, content.textAd, intendedStatus.
- **Get single LinkedIn text ad by ID** (Get). Get a text ad creative (GET /rest/creatives/{id}). id is the URL-encoded creative URN, e.g. urn%3Ali%3AsponsoredCreative%3A123.
- **Update a LinkedIn text ad by ID** (Update). Partially update a text ad creative (POST /rest/creatives/{id}) with a Rest.li patch, e.g. {"patch": {"$set": {"intendedStatus": "PAUSED"}}}.
- **Create a LinkedIn image ad** (Create). Create a sponsored single-image post (POST /rest/posts); upload the image first (assets.create), then sponsor the post with creatives.create.
- **Get single LinkedIn article ad by ID** (Get). Get an article (link) ad post (GET /rest/posts/{id}). id is the URL-encoded post URN.
- **Create a LinkedIn article ad** (Create). Create a sponsored article (link) post (POST /rest/posts) with source URL, title, description and thumbnail image; then sponsor it with creatives.create.
- **Create a LinkedIn video ad** (Create). Create a sponsored video post (POST /rest/posts) referencing an uploaded video URN; then sponsor it with creatives.create.
- **Create a LinkedIn document ad** (Create). Create a sponsored document post (POST /rest/posts) referencing an uploaded document URN (PDF, PPT, DOC); then sponsor it with creatives.create.
- **Create a LinkedIn asset** (Create). Register an image or video upload (POST /rest/assets?action=registerUpload). Returns the asset URN and an uploadUrl; PUT the file bytes to uploadUrl, then use the URN in ad posts.
- **Get single LinkedIn asset by ID** (Get). Check Status of Upload. Retrieve asset information using the Asset ID from the URN. Depending on content size, it might take a few minutes for the upload to complete. LinkedIn GET /rest/assets/{id}. id: URL-encode URNs. Required: id.
- **LinkedIn assets complete multipart upload** (Complete). Complete Multi-Part Upload. When you register a video as a multi-part upload by setting and , you receive a response with multiple upload URLs and headers. LinkedIn POST /rest/assets (action=completeMultiPartUpload).
- ...and 245 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
