How to give Claude access to your LinkedIn DMs
Short answer: three of the four available routes will waste your time. The official LinkedIn API cannot open your inbox. Browser automation wants your session cookie. Building your own wrapper over a messaging API costs more per month than buying a finished one. The fourth route is a hosted service that already did the work.
The four routes, honestly
| Route | Reads your DMs | Account risk | Your cost |
|---|---|---|---|
| Official LinkedIn API | No | Low | Weeks of partner applications, then it still cannot |
| Browser automation MCP | Yes | High | Free, plus your session cookie and ongoing repair |
| Your own wrapper on a messaging API | Yes | Low | About $55/mo plus everything you build |
| A finished hosted product | Yes | Low | $20/mo |
Why the official API is a dead end here
LinkedIn's API is gated per partner program. The programs cover advertising, recruiting systems, and managing pages you already administer. There is no general messaging product open to third parties.
This is worth understanding before you spend a month on it. A tool built on the official API can publish a post and read your own page analytics. It cannot open your inbox, and no amount of application paperwork changes that. Any product that does read your DMs is using an authenticated session, whatever its marketing says.
Why a session cookie is a bad trade
Most free LinkedIn MCP servers on GitHub ask you to paste your li_at cookie into a config file.
That cookie is a bearer credential. Anything holding it can act as you for as long as it lives, and it commonly survives a password change. You are handing full account control to a process on your laptop, a container, or someone else's server, with no scope and no revocation short of ending every session you have.
The second cost is maintenance. These servers parse rendered LinkedIn HTML, so a layout change breaks them silently. You will find out when a draft references the wrong company.
The better arrangement is a provider that takes your login on its own hosted page and hands the tool an opaque handle. Ask any vendor two questions. Where is my password entered. What do you store afterward.
Why building your own wrapper does not pay
The strongest hosted messaging API for LinkedIn is Unipile, and it is a genuinely good product. Iridium runs on it. If you are wiring it up yourself, here is the real arithmetic.
Unipile starts at 49 euros a month for up to ten linked accounts, which is roughly 55 US dollars. That is the floor whether you connect one account or ten. For a single personal inbox you are paying the ten-account price.
Then you build the part that is not an API call:
- An MCP server. OAuth, tool definitions, error handling, session refresh.
- A review queue. Drafts that persist, with approve, edit, rewrite, and skip.
- An activity log. Append-only, recording exact sent text and every failure.
- Voice matching. Storing your examples and getting drafts that read like you.
- Inbox classification. Deciding which of forty threads need an answer.
- Scheduling. Send windows in the recipient's timezone.
- Rate limiting. Enforced server-side, because a limit in a prompt is a suggestion.
- Retention. Deleting other people's profile data on a schedule, which is a legal obligation once you store it.
That is a real project, and it is a project that keeps running after it ships. You would be spending 55 dollars a month plus your weekends to arrive at 20 dollars a month of finished product.
Build it if the building is the point. If the inbox is the point, buy it.
What to check before you connect anything
Your LinkedIn inbox contains other people's private messages. Whatever you connect inherits that. These are the questions worth asking, and Iridium's answers are next to them.
| Question | Iridium |
|---|---|
| Where is my LinkedIn password entered? | On Unipile's hosted page. Iridium never receives or stores it and holds only an opaque handle. |
| How long is other people's data kept? | Discovered profile and post data is purged by a daily job seven days after collection. |
| What happens to unactioned drafts? | Comment drafts leave your queue after 24 hours. Outreach drafts leave after 3 days. |
| Can I disconnect LinkedIn without deleting my account? | Yes. Disconnecting revokes the session at the provider. Your Iridium account and settings stay. |
| What happens when I delete my account? | The LinkedIn session is destroyed and every device is signed out immediately. Personal data is erased within 30 days, and you can restore the account inside that window. |
| Who are the subprocessors? | Named individually in the Privacy Policy, with what each one does. |
| Is my data used to train models? | Our Privacy Policy makes no training commitment, so we will not claim one. Every subprocessor is named individually so you can read their terms yourself. |
| Can it send without me? | No. There is no auto-approve mode. Limits are enforced server-side. |
A vendor who cannot answer the first two quickly has not thought about them.
Questions people ask next
Is Unipile a competitor to Iridium?
No. Unipile is the connectivity layer Iridium is built on, and it is the right choice for that job. Unipile sells developer infrastructure. You bring an API key and build the product around it. Iridium is that product, already built, at a third of the entry price for a single account.
Which LinkedIn MCP servers actually expose messaging?
Fewer than the category implies. Several hosted options are built on LinkedIn's official API, which means they can publish posts and read analytics and cannot touch your inbox. Publishing and messaging are different products wearing the same label. Check which one you are buying before you pay.
What can Claude do with my inbox once it is connected?
Sort what came in, tell you which threads are waiting on you, draft replies from the full thread in your voice, and schedule each one for the hour you pick. Ask it what it sent yesterday and it reads the answer out of the activity log.
Will automating replies get my account restricted?
Unattended volume is what causes trouble, and repetition is what makes it visible. Approving each reply yourself removes both. It does not make automated outreach risk-free, and you stay responsible for using any tool inside LinkedIn's terms.
How long does setup take?
About five minutes. Create an account, connect LinkedIn through the hosted flow, then add https://api.iridiumhqmcp.com/mcp as a custom connector in Claude and approve it once.
Do I have to use Claude?
No. Iridium is a complete web app with the same inbox, queues, and log. The MCP server is a second surface. Any MCP client works, including Cursor and Codex.
How Iridium does it
Iridium is a finished LinkedIn product for agents, running on Unipile for connectivity. Your agent gets the inbox, drafting, commenting, publishing, and the activity log as tools. Every outgoing action is a draft. Approving is a separate step and it is the only thing that sends.
A tool call returns in about six seconds. It is $20 a month for one LinkedIn account, with a seven-day free trial and no card.
Your LinkedIn inbox, in Claude
7-day free trial. No credit card. Cancel anytime.
Start free → Replies that sound like you