LeadAdapter turns LinkedIn engagement into pipeline — and lets your AI agent run it, governed.
Comment→DM automations, email-gated lead pages, and a 42-tool MCP server so Claude, ChatGPT or Cursor can operate LinkedIn inside hard safety caps.
- 7-day trial, no card
- Works with Claude, ChatGPT and Cursor
- Caps published before you buy
Your session, your IP
Actions run in your own Chrome, on your own connection. We never ask for, receive or store your LinkedIn password.
EU-hosted, GDPR-native
Application, database and queues run at Hetzner in Germany. DPA at signup, export and deletion self-serve.
Caps you can read before you buy
Default limits, quiet hours and pacing are printed further down this page — not discovered after your account is restricted.
No card. You will need Chrome and the LeadAdapter extension — actions run in your browser, not on our servers.
Execution model
Choose how your account connects
Browser execution is the current mode. A separately consented cloud connection is in private testing; full cloud automation has not yet passed launch acceptance.
- The account owner authorizes session transfer.
- The session is encrypted on our EU server.
- A profile read must succeed before the identity is marked verified.
Profile reads only in this test. Full cloud automation is not yet available.
- Our server queues a job.
- Your paired Chrome extension picks it up.
- LinkedIn requests run inside your open session.
Chrome must remain open in browser mode.
- No LinkedIn password is collected.
- Cloud session transfer requires separate consent.
- One executor owns an account at a time.
- Connection and successful data sync are separate states.
LinkedIn can restrict automated accounts. Neither execution mode removes that risk. Read the platform risk details
The core loop
Post. Comment. DM.
One automation, wired to one post. It is the motion that built this category, minus the parts that get accounts restricted.
Post
Write the post yourself, or schedule it here with the automation already attached. When it publishes, the automation binds to the post and goes live.
Scheduling is Pro and above. Attaching an automation to a post you published by hand works on every tier.
Comment
Your extension checks the post for new comments on a jittered ten-minute cadence while Chrome is open. Keywords match any, all, or a regular expression, with negative keywords to exclude the ones you do not want.
Every comment is deduped by its LinkedIn URN, so the same commenter never triggers the same automation twice.
DM
Matched commenters get your message with their first name and your lead-page link. Optionally connect first, reply publicly under the comment, and follow up after N minutes if they do not answer.
Every send passes the Governor first: caps, do-not-engage, dedupe, quiet hours, pacing and your autonomy mode.
Latency is minutes, not seconds. Comment polling runs in your browser on a deliberately jittered cadence — that pacing is the product working, not a limitation we are apologising for.
What you are buying
Owned inbound first. Outbound when you mean it.
Starter and Pro — owned inbound
Your posts. Your commenters. Your lead pages. Everything happens on an audience that already raised a hand.
- Comment→keyword→DM automations
- Email-gated lead pages and tracked links
- Post scheduling with the automation pre-attached (Pro)
- MCP owned-asset tools for your agent (Pro)
- Webhooks into your own stack (Pro)
Operator — outbound
Search, feed, the engagers on other people’s posts, and messages to people who never commented on anything of yours.
- Search people, companies and posts
- Engagers off any post, including a competitor’s
- DMs, InMail and connection requests
- Signals with heat scores from saved searches
- The full MCP catalogue
- Approval queue and the autonomy dial
That single line is where the price step is: Starter and Pro work your own audience, Operator works other people’s. Half the MCP catalogue sits behind it, and we are not going to blur it to make a sale.
MCP
Let your agent run it — inside caps it cannot raise
LeadAdapter is an MCP server. Connect it to Claude, ChatGPT or Cursor and your agent gets 42 tools: read the comments on your post, create an automation, publish a lead page, look somebody up, send a DM. Every call goes through the same governance layer as the dashboard, lands in the same audit log, and draws down the same daily budget. There is no second pool.
- OAuth 2.1 with PKCE and dynamic client registration for Claude and ChatGPT; a Bearer API key for Cursor and other stdio clients.
- Tier-gated: Pro gets the 21 owned-asset tools, Operator gets all 42.
- A blocked call returns a structured reason — cap_reached, do_not_engage, duplicate — so the agent re-plans instead of retrying into a wall.
- Every write tool accepts dry_run: true and returns the governance verdict without doing anything.
- Destructive calls require confirm: true. Your agent cannot cancel a scheduled post by accident.
The tool catalogue is readable without an account. Browse the tool list
Nine loadouts
A loadout is a named job: a system prompt, a tool allowlist and defaults that already make sense. Packaging rather than new capability — which is exactly why it works.
Author
Studies the top posts in your niche, drafts lead-magnet posts in your voice, and wires the comment→DM capture before you publish.
Gatekeeper
Ranks inbound connection requests by fit, accepts the ones worth accepting, and drafts the welcome message.
Scout
Pulls the engagers off a competitor’s post, qualifies them, and opens with context instead of a template.
Radar
Watches your feed and your signals, scores the moment, and engages with a reaction, a reply or a comment.
Matchmaker
Matches the people who gave you an email on a lead page back to LinkedIn, then picks the channel: DM, connect or email.
Bridge
Ranks connection targets by fit and intent, sends within caps, and escalates to InMail or email when a connect goes nowhere.
Shadow
Shows up where a prospect is already active — their comments, their communities — before anybody sends a DM.
Reviver
Finds threads that died, reads where they died, and drafts the follow-up that actually fits.
Medic
Health-checks your automations and volumes, diagnoses what is underperforming, and recommends only inside the safety envelope.
Where the product actually is
LeadAdapter is in private beta. Capture — automations, lead pages, caps, audit and emergency stop — is what beta users run today. The MCP server, scheduling and enrichment come next, then the Operator outbound tools, then agency seats. A tier opens when its capabilities do, and we would rather lose a sale than take money for something you cannot use yet. If a feature on this page decides it for you, ask us first.
Governance
The caps are the product
Anyone can send DMs. The hard part is not sending the one that gets you restricted. Every write — from the dashboard, from an automation, from your agent, from the API — passes through one gate, and it draws from one budget.
Default caps for a new profile
Per LinkedIn profile, per day. You can lower any of them whenever you like. You cannot raise one above your tier ceiling — that refusal is the feature.
| Channel | Default / day | Highest you may set | Weekly |
|---|---|---|---|
| Direct message | 100 | 250 | — |
| InMail | 10 | 20 | — |
| Connection request | 20 | 40 | 150 |
| Comment | 20 | 60 | — |
| Reaction | 60 | 200 | — |
| Profile view (enrichment) | 100 | 250 | — |
| Search page | 50 | 100 | — |
| Post | 3 | 5 | — |
| Email, via your own provider | 200 | 500 | — |
- Quiet hours from 22:00 to 07:00 in the profile’s own timezone, plus an optional weekend pause. Jobs wait — they do not pile up and fire at 03:00.
- Pacing: a randomised 45–180 second gap between writes, and never more than 6 writes in ten minutes across all channels combined.
- Do-not-engage by profile, email address or whole domain. Checked when the action is requested and again when it executes.
- Dedupe: the same person, the same action, inside 30 days is blocked — unless they replied to you since.
- Approval queue with previews, bulk approve and a 72-hour expiry. Nothing that expired is ever executed later.
- Rate-limit reflex: a 429, a 999 or a captcha pauses the profile for 6 hours and halves its caps for 48 hours.
- Emergency stop: one click cancels every queued job and pauses the profile. Turning it back on is manual, deliberately.
- Full audit log — every tool call, automation action and approval decision with actor, result and reason, exportable as CSV.
Four autonomy modes
How much your agent may do without you. New profiles start at “approve outbound”, not at “autonomous”.
Draft only draft_only
Writes become drafts and nothing ever executes. The rehearsal mode — use it for the first day.
Approve every write approve_writes
Everything waits for you, including comments and reactions.
Approve outbound approve_outbound
DMs, connects, InMails and emails wait for a decision. Comments, reactions and your own posts go. This is the default for a new profile.
Autonomous within caps autonomous
Executes without asking — still paced, still deduped, still cap-checked, still do-not-engage checked.
Read this before you buy
Platform risk is real, and it is yours
LinkedIn does not offer an API for any of this. Every action LeadAdapter takes is an ordinary user action performed by software, and LinkedIn’s User Agreement prohibits automated access. LinkedIn restricts accounts for it. This happens to individual users, and in 2026 it happened to vendors too — at least one automation company had its company page removed and its founder’s account banned.
We cannot insure that risk, we cannot indemnify you against it, and we are never going to call this product safe. A vendor who tells you their LinkedIn tool is safe is either not thinking about it or hoping that you are not.
What we can do is make the risky thing less risky, publish exactly how, and ship the conservative default instead of the impressive one. Here is the whole list, so you can judge it.
What LeadAdapter does about it
- Browser execution uses your open Chrome session. The private cloud profile-read test requires separate session-transfer consent; full cloud execution is not yet available.
- Ships defaults well below the tier ceilings and makes you raise them deliberately, one channel at a time.
- Paces writes with randomised gaps and a hard ceiling on writes per ten minutes, regardless of how much your agent wants to send.
- Holds outbound for your approval by default on every new profile.
- Stops at the first sign of trouble: a 429, a 999 or a captcha pauses the profile and halves its caps.
- Enforces quiet hours on both sides — the server will not hand out the job and the extension refuses it.
- Requires an explicit consent screen, naming what we will do as you, before a profile executes anything at all.
- Logs every action, so you can see exactly what was done in your name and when.
What we would tell a friend to do
- Start at the defaults. Resist raising caps in the first week, however tempting the maths looks.
- Prefer inbound. DMing someone who just commented on your post is a different risk profile from DMing a stranger off a search result.
- Warm up slowly on a new or lightly used account — volume from a cold account is the classic trigger.
- Write messages a human would actually send. Template-shaped spam gets reported, and reports are what escalate.
- Do not run this from an account you cannot afford to lose.
We will publish our observed restriction rate once we have enough accounts for the number to mean something. Until then we would rather say “we do not know yet” than show you a figure we made up.
Who this is for
Three people buy this
The creator or founder
You post three to five times a week and you are answering “sent!” by hand at midnight. Starter or Pro turns that into a loop that runs while you write the next post.
The AI-native operator
You already run go-to-market from Claude. Operator gives your agent the full tool catalogue and a governance layer that says no on your behalf.
The agency
Five to fifty client profiles, each with its own consent, its own caps and its own approval gate — plus a read-only audit view you can actually show the client.
Questions
The things people ask before they buy
Do I have to keep Chrome open?
Do you store my LinkedIn password?
Can my account still be restricted?
Is there a free tier?
Where does my data live?
Which AI clients can connect?
Do you send outreach email for me?
Can I export or delete everything?
Does it work in Danish?
Start with the audience you already have
7 days, no card, and no free tier to disappear into. Install the extension, wire up one post, and find out whether the loop actually produces conversations before you pay for anything.
Chrome required. Prices in EUR, billed by Profectify LLC.