# LinkedIn Sales Navigator MCP connector

The LinkedIn Sales Navigator connector brings your sales contracts, seats, analytics exports and CRM profile matches into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, where each person works inside their own access with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | LinkedIn Sales Navigator |
| Category | Sales Intelligence |
| AI tools | 10 |
| 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 Sales Navigator is connected

- Which seats on the EMEA contract went unused this quarter?
- Export last month's activity outcomes for the enterprise team.
- Which CRM accounts have no matching Sales Navigator profile?

## Connect LinkedIn Sales Navigator in Elaichi

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

1. Open Connections, choose Add connection, and pick LinkedIn Sales Navigator.
2. Optionally set Share with, then press Connect.
3. Supply your own LinkedIn Sales Navigator app, then approve. LinkedIn Sales Navigator 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 Sales Navigator tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## LinkedIn Sales Navigator 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 Sales Navigator 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 Sales Navigator 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 Sales Navigator 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 Sales Navigator 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 Sales Navigator 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 Sales Navigator 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 Sales Navigator through Elaichi

### Pull the quarter's activity export in one ask

Sales Operations. Ask for an activity data export for the enterprise team, then check on the job until it is ready, without opening the LinkedIn Sales Navigator admin screens.

### Check which CRM accounts match Navigator profiles

Revenue Operations. Search the profile associations to see which CRM contacts and accounts are linked to a LinkedIn Sales Navigator profile, and run a CRM data validation export to find the gaps.

### See outcomes by rep, not just activity

Sales Leadership. Create an activity outcome export for a contract and ask for a plain summary of which reps turned InMails and saved leads into real conversations.

### Reconcile seats against the contract before renewal

Finance. List the sales contracts, start a seat data export, and compare paid seats with assigned seats ahead of the LinkedIn Sales Navigator renewal.

### Find reps who are not using their seat

Sales Enablement. Run a seat data export and ask which assigned seats show little or no activity, so coaching goes to the people who need it.

### Review who holds an access token

IT. List the access tokens issued for LinkedIn Sales Navigator and confirm that only current staff and approved systems still hold one.

## Elaichi vs Zapier MCP vs Composio for LinkedIn Sales Navigator

All three can connect LinkedIn Sales Navigator 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 Sales Navigator tools | Allow or restrict single LinkedIn Sales Navigator 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 Sales Navigator 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 Sales Navigator to Claude?

Connect LinkedIn Sales Navigator in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. LinkedIn Sales Navigator requires an OAuth application registered on its own side, so one admin brings a client ID and secret once, after which everyone else just signs in with their LinkedIn login. Nobody else ever handles a credential.

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

Yes. Once LinkedIn Sales Navigator is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect it once and every client picks it up.

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

It can list your LinkedIn Sales Navigator contracts and access tokens, start activity, outcome and seat exports and check when they are ready, and look up which CRM records are matched to a Sales Navigator profile, including a CRM data validation export to find the gaps. In practice that means asking for last quarter's outcomes by rep or which seats sat idle. Short, concrete asks work better than long sentences.

### Does connecting LinkedIn Sales Navigator give the AI access to every contract and seat?

No. Every call runs as the person who signed in, so the agent only sees the LinkedIn Sales Navigator contracts, seats and exports that person is already allowed to see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what LinkedIn Sales Navigator grants.

### Can my team share one LinkedIn Sales Navigator connection?

Yes. One admin connects LinkedIn Sales Navigator and shares the connection with a team, and nobody else handles the client ID or secret. Each person still signs in as themselves, so every export or lookup in the audit log carries their own name.

### Can I stop an agent from changing things in LinkedIn Sales Navigator?

Yes. Restrictions in Elaichi apply per action, for example creating exports in LinkedIn Sales Navigator, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

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

Offboarding that person in Elaichi ends their access to LinkedIn Sales Navigator through every client at once. A shared LinkedIn Sales Navigator connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting it once in Elaichi removes it from every client.

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

Yes. LinkedIn Sales Navigator 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 Sales Navigator?

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

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

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

## All 10 LinkedIn Sales Navigator tools

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

- **List all LinkedIn Sales Navigator sales contracts** (List). List the Sales Navigator contracts on which the signed-in member has an active seat (finder contractsByMember). Use the contract URN with the analytics export methods; hasReportingAccess tells whether the member may export data for it. Needs a 3-legged OAuth connection with r_sales_nav_analytics.
- **Get sales analytics export job by ID** (Get). Get the latest status of a Sales Navigator analytics export job by its job ID (returned by the sales_analytics_*_exports create methods). When status is COMPLETED the job carries downloadUrl (CSV, needs the Authorization header), expireAt and rowCount. Needs a 3-legged OAuth connection with r_sales_nav_analytics.
- **List all LinkedIn Sales Navigator sales access tokens** (List). Get a short-lived, limited-scope Sales Access Token for the signed-in member (finder viewerAndDeveloperApp), to pass in the Sales Navigator Display Services iframe query string instead of a login pop-up. Needs a 3-legged OAuth connection with r_sales_nav_display and a Team or Enterprise Sales Navigator contract.
- **Sales navigator profile associations search** (Search). Look up the high-confidence match between one CRM record and a LinkedIn member, identified by the CRM partner, CRM instance ID and record ID (key (instanceId:...,partner:...,recordId:...)). Returns the member URN, Sales Navigator profile URL and photo URL; 404 means no match is available. 400 with service error 40001/40002 means CRM Sync is not enabled or its status cannot be determined for the instance. Needs a client-credentials (2-legged) connection with r_sales_nav_profiles.
- **List all sales navigator profile associations** (List). Batch-get the LinkedIn member matches for several CRM records at once (Rest.li batch_get). Pass ids as a Rest.li list of keys, e.g. List((instanceId:inst1,partner:MS,recordId:rec1),(instanceId:inst1,partner:MS,recordId:rec2)). The response maps each key to its match under results, with per-key statuses and errors. Needs a client-credentials (2-legged) connection with r_sales_nav_profiles.
- **Create a LinkedIn Sales Navigator CRM data validation export job** (Create). Start a CRM Sync data validation export for a CRM instance: it lists CRM records whose data (for example job title or company) is out of date compared with the matched LinkedIn profiles, from exportStartAt onwards. LinkedIn answers 201 Created with the new job ID in the X-RestLi-Id / Location response headers (no body); then poll crm_data_validation_export_jobs.get. 403 with 40003/40004 means CRM Sync or Data Validation is not enabled for the instance. Needs a client-credentials (2-legged) connection with r_sales_nav_validation.
- **Get CRM data validation export job by ID** (Get). Get a CRM data validation export job by its job ID (from the create call) and CRM instance. When status is COMPLETED it has downloadUrls (valid 1 hour), expireAt and nextExportStartAt. Needs a client-credentials (2-legged) connection with r_sales_nav_validation.
- **Create sales analytics activity data export** (Create). Start an export of activities performed by seat holders (for example saving leads, performing searches and sending InMail) for a Sales Navigator contract (action exportActivityData). Returns a new export job with status ENQUEUED; poll sales_analytics_export_jobs.get with its id and the same contract until COMPLETED, then download the CSV from downloadUrl. The contract needs an Enterprise Sales Navigator subscription and the member needs reporting access. Needs a 3-legged OAuth connection with r_sales_nav_analytics.
- **Create sales analytics activity outcome data export** (Create). Start an export of activity outcomes (for example InMails accepted and declined) for a Sales Navigator contract (action exportActivityOutcomeData). Returns a new export job with status ENQUEUED; poll sales_analytics_export_jobs.get with its id and the same contract until COMPLETED, then download the CSV from downloadUrl. The contract needs an Enterprise Sales Navigator subscription and the member needs reporting access. Needs a 3-legged OAuth connection with r_sales_nav_analytics.
- **Create a LinkedIn Sales Navigator sales analytics seat data export** (Create). Start an export of seat-holder data (for example seat holder name, seat status, Social Selling Index scores and total connections) for a Sales Navigator contract (action exportSeatData). Returns a new export job with status ENQUEUED; poll sales_analytics_export_jobs.get with its id and the same contract until COMPLETED, then download the CSV from downloadUrl. The contract needs an Enterprise Sales Navigator subscription and the member needs reporting access. Needs a 3-legged OAuth connection with r_sales_nav_analytics.
