LinkedIn MCP with CRM

LinkedIn outreach tool Salesbot + built-in CRM for AI agents Connect Claude, Antigravity, Cursor or any MPC client to your LinkedIn account and run…

CommunityRequires local installNo sign-inGlobalFreeCan modify data
This server only runs on your computer. It cannot be added to Claude or ChatGPT web. See the project docs for installation.

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    LinkedIn outreach tool Salesbot + built-in CRM for AI agents

    Connect Claude, Antigravity, Cursor or any MPC client to your LinkedIn account and run human-in-the-loop outreach: research prospects, draft personalized messages for your approval, sync your inbox, and track everything in a built-in sales CRM. Built for targeted outreach, not bulk spam.

    What it can do (45 tools)

    • Lead discovery: search people on LinkedIn, Google X-Ray, or a Sales Navigator URL.
    • Contacts & campaigns: manage contacts and multi-step outreach sequences.
    • AI messaging: generate personalized drafts, review, then approve or reject — nothing sends without your OK.
    • Inbox: read conversations and reply in real time.
    • CRM: a persistent pipeline with configurable stages, notes, tasks, custom fields and full lead context.
    • CRM configuration: rename or add pipeline stages and define custom fields straight from your AI assistant.

    Safety first (anti-block)

    • Human approval queue for AI-initiated sends.
    • Enforced

    Requires a local install: run the server on your machine, then point your client at it.

    How to connect

    How to connect LinkedIn MCP with CRM to Claude

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect LinkedIn MCP with CRM to ChatGPT

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect LinkedIn MCP with CRM to Cursor

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    Tools not fetched yet: the server requires sign-in; the list appears after a manual check.