Coming soon

Build LinkedIn campaigns from Claude, ChatGPT, or any AI assistant

Q: What is the We-Connect LinkedIn MCP server?

It is a native Model Context Protocol server that connects your We-Connect account to AI assistants like Claude, ChatGPT, and Cursor. From your assistant you can build a Lead Engine campaign in plain language, then review and launch it in We-Connect.

Q: What can I do with it?

You can create a Lead Engine campaign, add one of your saved audiences, and build and save the outreach flow, all from your AI assistant. The saved campaign then opens in We-Connect for you to review and launch.

Q: Is my LinkedIn account safe if the AI makes a mistake?

Yes. Account safety is enforced by We-Connect, not by the AI assistant. All activity runs within We-Connect's pacing and daily limits, so the assistant cannot exceed them even if it misbehaves.

Q: Which AI assistants does it work with?

Any MCP-compatible assistant, including Claude, ChatGPT, Gemini, and Cursor. MCP is an open standard, so the same connection works across clients that support it.

Q: Is this a Zapier or n8n bridge?

No. It is a native MCP server. Your assistant works with We-Connect directly rather than passing text to a separate automation tool that forwards it.

Q: Do I need to write code to use it?

No. You connect your assistant to We-Connect once, then work in plain language. There is no code to write and no server to host.

Q: How do I connect my assistant?

Connect your We-Connect account to your assistant once through MCP. After that, you work in plain language, and the connection stays available across your sessions.

Q: Does it work with my existing Lead Engine setup?

Yes. The MCP builds campaigns to the same structure the Lead Engine uses and saves them to your account, so they open and run in We-Connect like any other campaign.

We-Connect's native MCP server lets your AI assistant build a Lead Engine campaign in plain language. Create the campaign, add a saved audience, and construct the outreach flow, ready to review and launch in We-Connect.

See how it works

HOW IT WORKS

Build a campaign by describing it

Connect your assistant to We-Connect once, then work in plain language. The MCP handles the campaign structure behind the scenes while you describe the outreach you want.

Connect once

Connect Claude, ChatGPT, or any MCP client to We-Connect once, no code to write

Describe your campaign

Tell your assistant the campaign you want and the saved audience to use

Auto-build the flow

The MCP builds the Lead Engine flow, steps, conditions, and settings, to the same structure the Lead Engine uses

Auto-save

It saves the campaign to your We-Connect account

Review & launch

You open it in We-Connect to review and launch

WHAT IT DOES

From a sentence to a saved campaign

Describe the outreach you want and the MCP assembles it in your We-Connect account, ready to review and launch.

Create the campaign

Create a Lead Engine campaign from your assistant

Add one of your saved audiences to the campaign

Build and save the flow

Build the outreach flow with LinkedIn actions and conditions

Save to We-Connect and open in the Lead Engine to launch

THE BIGGER PICTURE

An assistant that does more of the work

The MCP keeps expanding across the outreach workflow, so more of what you do in We-Connect becomes something you can do from your assistant.

Launch, pause, and resume campaigns

Read campaign performance and surface who is interested

Work from Watchlist buying signals to reach contacts showing intent

Add contacts to campaigns that are already running

Build and refine audiences from a description

Reach across LinkedIn and email in one sequence

NATIVE CONNECTION

A native connection, not a Zapier handoff

Many tools connect to AI assistants through a bridge like Zapier or n8n, where the assistant writes text and a separate tool passes it along. The We-Connect MCP is native. Your assistant works with We-Connect directly, so building a campaign is one conversation, not a chain of handoffs between tools.

Bridge tools

The assistant never works with the tool itself. It produces text that something else forwards.

We-Connect MCP

The assistant builds the campaign in We-Connect directly. One conversation, no middle tool.

Your account safety is never in the AI's hands

Account safety is enforced by We-Connect, not by the AI assistant. Every action runs within We-Connect's pacing and daily limits. Even if an assistant misbehaves or misunderstands a request, it cannot push past those limits, because the safeguards live in We-Connect's execution layer, not in the model.

BRING YOUR OWN ASSISTANT

Works with the AI you already use

MCP is an open standard, so the same connection works across assistants that support it. Connect the one you already use.

Frequently asked questions

What is the We-Connect LinkedIn MCP server?+

What can I do with it?+

Is my LinkedIn account safe if the AI makes a mistake?+

Which AI assistants does it work with?+

Is this a Zapier or n8n bridge?+

Do I need to write code to use it?+

How do I connect my assistant?+

Does it work with my existing Lead Engine setup?+

Coming soon

Build your outreach from the chat you already use

Connect your assistant to We-Connect and build LinkedIn campaigns without leaving the conversation.

Get started

CONNECT | ENGAGE | EXPAND

We-Connect is not affiliated with LinkedIn. All LinkedIn trademarks and logos belong to LinkedIn.