ClaudeReactIn
LinkedIn MCP connector

Drive your LinkedIn outreach from Claude

The MCP connector plugs ReactIn into Claude. You say what you want, Claude builds the lists, drafts the campaigns and reads your replies. Nothing happens on your LinkedIn account until you ask for it.

Get leads now
Claude
ReactIn connected

Build a list from everyone who liked this post, then draft a campaign on Marie's account.

ReactIn tools called

create_listcreate_campaign
List created · 148 leads
Campaign ready to launch
Waiting for your approval to start
Video tutorial

Seven minutes to see it for real

Setting up the connector, checking the connection, a lookalike list built from a single profile, then a campaign launched without leaving the chat.

Chapters

Watch on YouTube
Setup

Connected in five minutes

The connector is added from Claude — web, desktop or mobile. Nothing to install, nothing to code: one URL to paste and one authorization to confirm.

  1. 1

    Open Connectors in Claude

    Customize panel from the sidebar, then the Connectors tab. On mobile: menu, then Settings → Connectors.

  2. 2

    Add a custom connector

    The + button in the top right of the connector list.

  3. 3

    Paste the ReactIn server URL

    Name: ReactIn. URL: the one shown here. Leave the OAuth Client ID and Secret fields empty.

  4. 4

    Connect and authorize

    Click Connect, then Authorize on the ReactIn screen, checking which organization is being requested.

  5. 5

    Check that it answers

    Ask Claude: “List my ReactIn organizations.” If your organization comes back, the connector is live.

MCP server URL

https://app.reactin.io/mcp

This URL is not a web page

Opened in a browser it returns an authentication error — that is normal and expected. It is meant to be pasted into Claude, which authenticates over OAuth.

See the step-by-step tutorial, with screenshots
Use cases

Six requests, six tools called for you

You write one sentence, Claude picks the matching ReactIn tool. Here are the most common requests and the tool behind each one.

Build a list

“Build a list from everyone who liked this LinkedIn post.”

create_list

Draft a campaign

“Draft a campaign for this list, on Marie's account.”

create_campaign

Track performance

“What's my acceptance rate over the last 30 days?”

get_linkedin_account_analytics

Triage the inbox

“Show me the unread replies from the SaaS campaign.”

get_conversations

Enrich leads

“Enrich the leads in this list that have no job title.”

enrich_organization_lead

Step back

“What does the GTM Expert recommend this week?”

get_gtm_expert_recommendations
Security

Your LinkedIn account is never used by surprise

That is the server's first rule: a LinkedIn account is only used when you explicitly name it. Everything else reads data already stored on our side.

Reading consumes nothing

Lists, leads, conversations and analytics are read from our database. Zero LinkedIn action, zero quota spent.

Enrichment goes through our provider

Enriching a lead spends one of your organization's enrichment credits, never your LinkedIn account.

Sending needs your green light

Launching a campaign or replying to a lead runs on the account you name, after the exact message has been shown to you.

You can disconnect the connector at any time from the Connectors tab in Claude: access is revoked immediately.

FAQ

The questions we get asked

The Model Context Protocol is an open standard that lets an AI assistant call a product's tools. A LinkedIn MCP is a server exposing your LinkedIn actions to that assistant. ReactIn's exposes your lists, campaigns, inbox and analytics: Claude can use them the way you would in the app.

No. There is one URL to paste into Claude and one authorization to confirm. The OAuth Client ID and Secret fields stay empty: authentication happens on its own during the connection step.

Claude on the web, the desktop app (Mac and Windows) and mobile (iOS and Android), through custom connectors. Any other MCP-compatible client with OAuth authentication can connect too.

The API is for wiring ReactIn into your tools with code, using calls you write yourself. The MCP connector is for driving ReactIn in conversation: Claude picks the tool and writes the call for you.

Yes, if you ask for it. The server requires the exact text to be shown to you before sending, one message per call, and forbids bulk-replying to your conversations. Sends draw on the daily quota of that account, just like your campaigns.

Yes, the connector is included: there is nothing extra to buy. You need an active ReactIn account with at least one organization, and access to Claude. Only lead enrichment spends your organization's credits, exactly as it does in the app.
500+ teams
4.9/5 rating
27% reply rate

Your outbound stack, replaced. In 10 minutes.

7 days free. No credit card. Full access.

Get leads now