# LinkedIn outreach from Claude

> Run LinkedIn outreach from Claude Code or Claude Desktop with HeyLead, an MCP server that finds the right people, writes in the voice of your own LinkedIn posts, follows up and handles replies. Setup in two minutes.

This is the Markdown twin of https://heylead.dev/claude-linkedin-outreach (the page, in text). Index for agents: https://heylead.dev/llms.txt

Last updated 23 September 2026

Claude can run your LinkedIn outreach once it has the tools. HeyLead is an MCP server that gives it them: find the right people, write to them in the voice of your own LinkedIn posts, follow up, handle replies.

## Connect HeyLead

Paste this into Claude Code or your AI chat:

`Set up HeyLead using https://heylead.dev/llms.txt`

Your AI will follow the setup for your client. The hosted connection needs no Python, uv or API key.

### Claude Code terminal

`claude mcp add --transport http --scope user heylead https://heylead.dev/mcp`

Open `/mcp`, select HeyLead, and follow the browser sign-in. If HeyLead is not listed, start a new session and open `/mcp` again.

### Claude Code desktop, without the CLI

If `claude` is not on PATH, paste the setup prompt above into the Code tab. Your agent can add the remote server to your Claude Code configuration without installing a CLI. It must preserve your existing settings. Start a new session, then sign in through `/mcp`.

### Claude Desktop chat, Cowork and claude.ai

Open Customize → Connectors (or Settings → Connectors), choose **Add custom connector**, and enter:

`https://heylead.dev/mcp`

Click Add, then Connect and complete browser sign-in. Enable HeyLead in your conversation. If Add custom connector is unavailable, check your Claude plan or ask your workspace administrator.

### Cursor

Add this to `.cursor/mcp.json`, merging it with existing servers, then connect and sign in:

`{"mcpServers":{"heylead":{"url":"https://heylead.dev/mcp"}}}`

### Finish and verify

1. Sign in with Google when your client opens HeyLead in the browser.
2. Connect LinkedIn in the [dashboard](https://heylead.dev/dashboard/).
3. Ask your AI: “Show my HeyLead status.” It should call `show_status` and report your workspace, even if you have no campaigns yet.
4. Describe your product and audience, and ask for a draft campaign. Review it before asking HeyLead to launch.

A saved server configuration is only the first step. Setup is verified when HeyLead answers a tool call. If sign-in fails or tools do not appear, follow the [troubleshooting steps](https://heylead.dev/llms.txt).

## Then just ask

- "Find me heads of engineering at Series A fintech startups in London."
- "Show me the prospects before anything goes out."
- "Launch it."
- "Who replied this week, and what did they say?"
- "Pause everything."

A campaign is a draft until you say launch. After that, HeyLead stays within daily and weekly limits for each account and sends on weekdays, 08:00 to 22:00 in your time zone.

## Also works in

Cursor and any other MCP client that can run a stdio server. See [the MCP server page](https://heylead.dev/linkedin-mcp-server).

Related: [LinkedIn MCP server](https://heylead.dev/linkedin-mcp-server) · [Open-source AI SDR](https://heylead.dev/open-source-ai-sdr) · [What is HeyLead?](https://heylead.dev/what-is-heylead)