Model Context Protocol

LinkedIn MCP server: connect Claude to LinkedIn

Bring your LinkedIn inbox, prospect signals, outreach drafts, and CRM into Claude through Linxa. Connect your account, then start with a read-only request.

Get my token Connect Claude step by step

Read access is free. Write access is $7/month standalone — and already included in Outreach and Team.

Give Claude your product context

Connect your LinkedIn workspace first. For outreach, add your website to prepare a product brief and ICP, then review the result. Claude can use that saved context when helping you prepare messages and campaigns.

ICP derived for you

Paste a URL once. Your agent inherits who to target and why, no prompt engineering required.

Full write access

Reply to post comments, prepare drafts, configure outreach, and review supported external actions before approving them.

Every request itemised

Full detail on every LinkedIn call the agent makes. Nothing happens that you cannot audit.

Prefer not to wire it up yourself? The same engine runs behind the AI LinkedIn Agent and Smart Inbox. Same account, same data — MCP is just the door for people who already live in their own tools.

Core Capabilities

Products & ICP

Create products, generate ICP rules, and keep your agent grounded in what you sell.

Find the right leads

Launch a search from a persona or LinkedIn URL, then work only with scored results.

Control sequences

Build steps, attach a lead-search audience, preview everything, then start or pause.

Handle replies

Prioritize conversations, prepare or edit contextual drafts, approve exact recipients, and verify delivery status.

How to connect Claude to LinkedIn

Connect the hosted Linxa LinkedIn MCP server to Claude Desktop, Claude on the web, or Cowork. Start with an inbox read, then add drafts and outreach when you need them.

Before you begin: use your own Linxa account and a Claude account that allows custom connectors. Your organization may require an owner to add the connector. Check Claude’s current connector instructions ↗

Connect your LinkedIn account to Linxa
Install the Linxa Chrome extension, sign in to Linxa, and connect the LinkedIn account you want to use. Linxa does not ask for your LinkedIn password. You can read your inbox without first creating an outreach campaign.
Get the Linxa Chrome extension →
Create your personal MCP token
Open Linxa MCP Setup and generate or copy your personal API token. Use your own token for your own account; keep it out of chat messages, screenshots, and shared configuration files.
Open Linxa MCP Setup →
Add a custom connector in Claude
Open Customize → Connectors, choose + Add → Add custom connector, and name it Linxa. In interfaces that use Settings → Connectors, open Add custom connector there. Paste the server URL below and continue to authentication.
MCP server URL
```
https://app.uselinxa.com/api/mcp/rpc
```
Set the authorization header
For this token-based setup, select No sign in under Authentication. Add a request header named authorization and enter Bearer followed by a space and your personal Linxa MCP token. Keep Required enabled. Do not put the token in the server URL or a chat message.
Authorization header format
```
Bearer <your Linxa MCP token>
```
Connect and enable Linxa in your chat
Finish with Add, then Connect if Claude prompts you. In a new Claude or Cowork conversation, use + → Connectors to enable Linxa. This setup uses the token in the header; it does not require an OAuth sign-in page. For Team or Enterprise accounts, an owner may need to add the connector first.
Verify with a read-only request
Paste the verification prompt below. A successful result shows your Linxa plan, timezone, and session state. A successful MCP connection and a valid LinkedIn session are separate checks: reconnect LinkedIn in Linxa if the session is unavailable.
Read-only verification prompt
```
Use the Linxa tool linxa_get_user_settings. Show my current plan, timezone, and LinkedIn session state. Do not change data or send anything.
```
Expected result: your plan, timezone, and session state. This check does not return usage quotas and does not send a LinkedIn message.

Using Claude Code or another client? Follow the Claude Code instructions or choose your MCP client.

Connection checklist if the first request fails

Connection or authentication error: check the HTTPS URL and the complete authorization header, including the space after Bearer. Use a current personal token.
Linxa tools are missing: enable the connector in this conversation. Check your organization’s connector permissions.
LinkedIn session is unavailable: reconnect LinkedIn through Linxa. This is separate from MCP authentication.
A write tool is unavailable: check your Linxa plan and token permissions. Do not start an outreach sequence just to test the connection.

Practical Claude LinkedIn outreach and inbox workflows

Copy a prompt, replace the placeholders, and work through one task at a time. These are examples of what to ask, not claims that an action has already run.

Inbox and post reads can start with free read access. Saving drafts or campaign setup requires write access. Your connected account, current tool catalog, and permissions determine what Claude can use.

Read access

Start the day with the right conversation

You have LinkedIn conversations in Linxa and want to find what needs attention.

Start the day with the right conversation prompt

Use Linxa to show the conversation that needs my attention, with its direct inbox link and the reason. If none needs attention, show recent follow-ups and their due status. Do not mark anything as read, change data, or send a message.

What to expect: The next Needs Attention conversation, or recent follow-ups if that folder is empty, with links back to the inbox.
What changes: Reading only. No messages or account settings change.

Explore Smart Inbox →

Write access to save drafts

Prepare a reply with conversation context

Choose an existing conversation and replace [contact] with the person you mean.

Prepare a reply with conversation context prompt

Find my Linxa conversation with [contact]. If more than one matches, ask me which one. Prepare and save a concise reply using the conversation and product context. Respect no-contact decisions and follow-up dates. Show the complete draft. Do not send or schedule it.

What to expect: A saved, reviewable reply draft for the exact selected conversation, when the conversation is eligible for a reply.
What changes: Saving a draft changes your workspace. Sending requires a separate preview of the exact recipient and text, followed by your approval.

See the reply workflow →

Read first; write access to publish

Review LinkedIn post signals

Your own posts and their engagement have been synced to Linxa.

Review LinkedIn post signals prompt

Show my latest stored LinkedIn posts and their sync times. Ask me which post to inspect, then show its commenters and reactions with the engagement fetch time. Suggest a useful reply to one comment as text in this chat. Do not publish anything.

What to expect: People and comments from the selected owned post, with data freshness visible and a proposed reply to review.
What changes: Stored engagement is not a live refresh. Publishing a comment requires a dry-run preview and approval; a reaction alone does not prove buying intent.

Explore LinkedIn signals →

Write access for saved setup

Prepare a Claude LinkedIn outreach campaign

You have a product website and a specific audience hypothesis.

Prepare a Claude LinkedIn outreach campaign prompt

Use [website URL] to prepare a product brief and ICP in Linxa. Show them for review before saving changes. After I approve the audience, help prepare an invitation, first message, and two follow-ups. Preview drafts for selected prospects. Keep invitation automation and sequences off; do not start a campaign or send anything.

What to expect: A reviewed product brief, audience criteria, and draft sequence prepared in stages, with automation kept off.
What changes: Research and drafts do not launch outreach. Source collection can take time; campaign activation and sending are separate decisions.

Explore cloud LinkedIn outreach →

Read access for analysis

Review a running campaign before changing it

You have an existing Linxa sequence with recorded activity.

Review a running campaign before changing it prompt

List my Linxa sequences and ask which one to inspect. Read its steps and available statistics. Summarize the reported counts and identify one message worth reviewing. State which data is missing. Suggest a revision in this chat; do not edit, pause, resume, or start the sequence.

What to expect: An explanation grounded in the selected sequence and its available statistics, plus a proposed edit.
What changes: No campaign settings change. Sparse results are not proof of why a campaign performed as it did.

Check the available MCP tools →

Available Tools

Discover the current tool catalog for inbox review, outreach, your own posts, and engagement. Available tools depend on your plan and token permissions. Publishing a post comment or an exact reply always starts with a preview and waits for your approval.

linxa_get_next_actions

Get the one Needs Attention chat that needs you now, with a direct Smart Inbox link; fall back to ten recent follow-ups only if that folder is empty.

linxa_list_my_posts

List your stored LinkedIn posts with content, media, performance, and sync status.

linxa_get_post_engagement

See the actual people who reacted or commented, what they wrote, and whether you already replied.

linxa_comment_on_post

Preview a top-level comment on one of your posts, then publish it only after explicit approval.

linxa_reply_to_post_comment

Preview an exact reply to one commenter, then publish only after explicit approval.

linxa_prepare_replies

Prepare Smart Inbox-quality drafts for exact conversations without sending, while respecting follow-up dates and no-contact decisions.

linxa_send_drafts

Preview full drafts and recipients, then queue only exact approved conversation IDs with a short-lived approval token.

linxa_list_products

Read the products and ICP context that guide your agent.

linxa_search_leads

Start an asynchronous lead search from a persona or LinkedIn search URL.

linxa_set_autopilot

Set schedule, daily limit and ICP threshold — only after an explicit approval.

linxa_set_sequence_audience

Bind a sequence to explicit owned search sources; a missing audience never means all contacts.

linxa_get_action_status

Check whether a queued action was delivered, cancelled, skipped or failed.

Explore every tool and parameter

Security by Design

Your data stays yours. We prioritize strict security protocols.

No Password Sharing

We never ask for or store your LinkedIn password. Access is handled via a secure, user-controlled session token.

Token-Based Access

This Claude setup uses your personal MCP API token. Revoke or replace it in Linxa MCP Setup when you need to remove access.

Session Reliability

The extension connects your LinkedIn session. Outreach runs on Linxa servers and can continue when your computer is off, while the connected session remains valid.

Scoped Workspace Access

Claude accesses supported workspace data through the connected account and token permissions. Review the requested tools and data before enabling a workflow.

Troubleshooting

Token Invalid or Expired

Check the authorization header and use the current personal token from Linxa MCP Setup. Replace a token that has been revoked or rotated.

Extension Not Installed

Install the extension to connect your LinkedIn session. Outreach then executes on Linxa servers through a proxy in your selected country.

Not Signed Into LinkedIn

Ensure you are logged into LinkedIn in the browser where the extension is installed.

Sync Not Updating

Check the reported sync time and LinkedIn session state. Reconnect an unavailable session; cloud outreach does not require your computer to remain on.

Rate Limits

Follow the tool’s reported limit and retry/reset information. A scheduled or approved action may still be delayed or stopped by account limits.

How MCP is priced

One value unit, no surprises. If you already pay for Linxa, MCP is already included.

MCP read

Free

Read your inbox, conversations, prospects, and goal progress from any MCP client.

MCP write

$7/mo

Everything above, plus sourcing, scoring, invites, sequences, and drafted replies from your agent.

Outreach & Team

Included

MCP write access comes with both paid plans at no extra cost, alongside the Agent and Smart Inbox.

Get my token

Paste your URL, confirm your ICP, copy the token. About a minute.

LinkedIn MCP FAQs

How do I connect Claude to LinkedIn?

Connect your LinkedIn account to Linxa with the Chrome extension, create a personal MCP API token in Linxa MCP Setup, and add the Linxa server as a custom remote connector in Claude. Select No sign in and set the authorization request header to Bearer followed by a space and your token. Enable Linxa in the conversation, then run the read-only settings check on this page.

What is the LinkedIn MCP server URL?

The Linxa remote MCP endpoint is https://app.uselinxa.com/api/mcp/rpc. It uses Streamable HTTP. For the Claude setup on this page, authenticate with a personal API token in the authorization header, not in the URL.

Do I need to install a local MCP server for Claude Desktop or Cowork?

No. Add the hosted Linxa server as a custom remote connector. This route does not require a local JSON configuration file or an MCP bridge package. Claude Code uses its own client configuration; see the platform-specific setup guide.

What can I do with Claude LinkedIn outreach?

Use Claude with Linxa to review product and ICP context, prepare audiences and sequence drafts, inspect existing campaign statistics, and work with inbox replies. Saved changes require write access. Preparing a draft does not launch outreach; review the intended audience, messages, schedule, and sending controls before enabling a campaign.

How much does Linxa MCP access cost?

Read access is free. The standalone MCP write add-on is $7 per month; write access is also included in Outreach and Team. Your plan and token permissions determine which actions are available. Your Claude subscription is separate.

Does outreach keep running when my computer is off?

Yes, while your connected session remains valid. The extension connects your LinkedIn session without sharing your password. Outreach executes on Linxa servers through a proxy in your selected country, following your configured schedule, pacing, and limits. A cloud connection does not guarantee account safety or delivery.

Will connecting Linxa automatically send messages?

Connecting a client does not itself start a campaign. Use read-only prompts first. Saving drafts or configuration changes is different from sending. Supported message and comment tools require a preview and explicit approval before publishing; enabled sequence autopilot follows the settings you configured.

Why does Claude say it cannot reach Linxa?

Check the exact server URL, the authorization header name, and the complete Bearer token value including its space. Confirm the token has not been revoked or replaced and that the connector is enabled for the conversation. A valid MCP token can still report an unavailable LinkedIn session; reconnect the account in Linxa separately.