# Unipile MCP [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/unipile/unipile-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/unipile-mcp

## Description
LinkedIn, Sales Navigator, Recruiter, WhatsApp, Instagram, Telegram and email MCP for coding agents.

## Tools
Capabilities this server exposes over MCP:

- **search-endpoints** — Searches paths, operations and parameters, for example `sales-navigator`, `inmail` or `relation-requests
- **list-specs** — Lists the available OpenAPI specs; the others take the spec `title` as a parameter (`Unipile API`)
- **list-endpoints** — Lists every path and method with its summary
- **get-endpoint** — Returns one operation's full request/response schema, security and servers
- **execute-request** — Runs the request for real (a HAR object) against your own accounts

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "unipile-mcp": {
    "url": "https://developer.unipile.com/mcp?branch=v2.0"
  }
}
```

## Documentation

## What Unipile MCP does

Unipile MCP MCP server gives coding agents structured access to the Unipile API. The hosted service provides one MCP connection for integrations involving LinkedIn, LinkedIn Sales Navigator, LinkedIn Recruiter, WhatsApp, Instagram, Telegram, Gmail, Outlook, IMAP email, and Google or Outlook calendars.

Its primary purpose is build-time development. An agent can inspect the API contract, generate application code, and test calls against accounts connected to Unipile. The resulting application can call the Unipile REST API directly or use the Node.js or Python SDK; production code does not need to depend on MCP.

The available API surface includes searches, profiles, invitations, messages, InMails, company data, job postings, applicants, conversations, email, and calendar operations. Exact availability depends on the OpenAPI specification and the connected account type.

## How it works

The server exposes discovery tools for the Unipile API. An agent can list available specifications, search endpoint paths and parameters, list routes with their methods and summaries, and retrieve a selected operation's request and response schema, security requirements, and server details.

After inspecting a route, the agent can use `execute-request` to send a real request represented as a HAR object. Requests run against the accounts associated with the supplied Unipile credentials. This lets a developer validate request bodies and responses with a test account before implementing the equivalent call in application code.

LinkedIn account types remain distinct in the API. Classic LinkedIn, Sales Navigator, and Recruiter use different search routes, filters, and InMail behavior, so the agent should inspect the relevant operation instead of assuming that one route applies to all three.

## Setup and configuration

Connect a test account in the Unipile dashboard, create a Scope for that account, and generate a scoped Account API key. The hosted MCP endpoint is:

```text
https://developer.unipile.com/mcp?branch=v2.0
```

Configure the client to use HTTP transport and send the scoped key in the `X-API-KEY` header. For Claude Code, the documented command is:

```bash
claude mcp add --transport http unipile "https://developer.unipile.com/mcp?branch=v2.0" --header "X-API-KEY: your-scoped-api-key"
```

Cursor, VS Code, Codex, Gemini CLI, Windsurf, and Claude Desktop configurations are also provided by the project. Use a test account when calling `execute-request`, particularly for operations that send messages, invitations, or other changes.

## Tools and capabilities

The Unipile MCP MCP server exposes five MCP tools:

- `list-specs` lists available OpenAPI specifications, including the `Unipile API` specification.
- `search-endpoints` searches endpoint paths, operations, and parameters using terms such as `sales-navigator`, `inmail`, or `relation-requests`.
- `list-endpoints` returns paths and methods with their summaries.
- `get-endpoint` returns the full contract for one operation, including request and response schemas, security, and servers.
- `execute-request` performs an authenticated request using a HAR object.

These tools support workflows such as creating a Sales Navigator lead search, adding LinkedIn invitations to a CRM, synchronizing WhatsApp and LinkedIn conversations, or adding Gmail, Outlook, and IMAP sending to a sequence. The server is also suitable for inspecting calendar routes before implementing scheduling features.

## Limitations and notes

This is a hosted, build-time MCP service rather than a production integration layer. The application generated by the agent must call the Unipile REST API or an SDK after development is complete.

Real requests operate on connected accounts and can change their state. The account must support the requested product or feature; for example, Sales Navigator operations require a Sales Navigator seat. The server helps discover the API contract, but developers remain responsible for selecting the correct account, route, credentials, and test data.

_Full upstream README: https://allmcps.com/mcp/unipile-mcp/readme_