The Unipile MCP server gives coding agents the Unipile API. Connect it to Cursor, Claude Code, Codex, Gemini CLI, VS Code, Windsurf or Claude Desktop. Your agent can then find the right endpoint, read its exact request and response schema, write the integration in your stack and test the call on your connected accounts.

It covers LinkedIn (Classic, Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram, email (Gmail, Outlook, IMAP) and calendars (Google, Outlook). The server is generated from the API reference, so it always matches the API.

Installation

1. Get your access token and your DSN

1. Generate an access token in the Unipile Dashboard. It goes in the X-API-KEY header of the MCP connection.
2. Copy your DSN from the top right of the Unipile Dashboard, for example https://api1.unipile.com:13111. Every v1 request goes to your DSN.

The access token is optional if the agent only reads the API reference. It is required for the agent to call the API.

Your access token gives access to the accounts of your Unipile application. Only configure it in clients and on machines you trust, and never commit it to a repository.

2. Set up your client

The server URL is https://developer.unipile.com/mcp?branch=v1.0.

{
  "mcpServers": {
    "unipile": {
      "url": "https://developer.unipile.com/mcp?branch=v1.0",
      "headers": {
        "X-API-KEY": "your-access-token"
      }
    }
  }
}

claude mcp add --transport http \
  --scope user \
  --header "X-API-KEY: your-access-token" \
  unipile "https://developer.unipile.com/mcp?branch=v1.0"

[mcp_servers.unipile]
url = "https://developer.unipile.com/mcp?branch=v1.0"
http_headers = { X-API-KEY = "your-access-token" }

{
  "mcpServers": {
    "unipile": {
      "httpUrl": "https://developer.unipile.com/mcp?branch=v1.0",
      "headers": {
        "X-API-KEY": "your-access-token"
      }
    }
  }
}

{
  "inputs": [
    { "type": "promptString", "id": "unipile_token", "description": "Unipile access token", "password": true }
  ],
  "servers": {
    "unipile": {
      "type": "http",
      "url": "https://developer.unipile.com/mcp?branch=v1.0",
      "headers": {
        "X-API-KEY": "${input:unipile_token}"
      }
    }
  }
}

{
  "mcpServers": {
    "unipile": {
      "url": "https://developer.unipile.com/mcp?branch=v1.0",
      "headers": {
        "X-API-KEY": "your-access-token"
      }
    }
  }
}

{
  "mcpServers": {
    "unipile": {
      "type": "http",
      "url": "https://developer.unipile.com/mcp?branch=v1.0",
      "headers": {
        "X-API-KEY": "your-access-token"
      }
    }
  }
}

3. Give the agent your DSN

The agent sees the generic server URL https://{subdomain}.unipile.com:{port} through the get-server-variables tool, but it cannot guess your DSN. Put it in your first prompt, or in your project's agent instructions (AGENTS.md, CLAUDE.md, Cursor rules):

Unipile API v1. My DSN is https://api1.unipile.com:13111.

What to ask your agent

Describe the feature you are building. The agent searches the endpoints, reads the schema, writes the code and can test the call. For example:

• "List my connected Unipile accounts and tell me which ones are LinkedIn, WhatsApp and Gmail."
• "Build a Sales Navigator lead search with seniority and company headcount filters. Test it on my LinkedIn account."
• "Write a function that sends a LinkedIn invitation with a note, and one that lists the invitations still pending."
• "Send an InMail from my Recruiter account to this profile, with a subject."
• "Sync WhatsApp and LinkedIn conversations into our inbox, and set up a webhook for new messages."
• "Send an email with Gmail, Outlook or IMAP through the same function, and reply in the same thread."

The v1 endpoints behind these features:

Available tools

• list-endpoints - Lists every API path and HTTP method with its summary
• search-endpoints - Searches paths, operations and parameters, for example inmail or sales_navigator
• get-endpoint - Returns an endpoint's full detail: parameters, request body, responses and security
• get-server-variables - Returns the server URL template (subdomain and port), to be filled with your DSN
• execute-request - Makes a live API call and returns the response. It needs your access token in the X-API-KEY header

📘

This page is for API v1

The same server also serves API v2: use branch=v2.0 instead of branch=v1.0. v1 and v2 are separate environments. v2 needs its own account on dashboardv2.unipile.com and its own API key, and accounts connected in v1 are not visible in v2. See the v2 MCP guide.

Resources

• github.com/unipile/unipile-mcp: registry manifest and setup for every client
• Node.js SDK: use it in the code the agent writes for your product