What it is
A cold message to a stranger and a forwarded introduction from someone they trust are not the same outreach, and only one of them is worth the account risk. This turns the sending account's own connection list into the shortest path to a target company: read the network once, triage it on the only field LinkedIn gives you, spend profile calls on the few candidates that survive, and write the ask to the connector rather than to the prospect.
Who it is for
- Anyone whose next meeting is likelier to come from one honest introduction than from fifty invitations — founders, partners, agency owners, and salespeople selling into accounts where a stranger gets ignored.
Capabilities
Each of these is one atomic thing the product can do, and each names what performs it. A capability fulfilled by a tool maps onto a tool the MCP endpoint serves today — follow the link and you can read the exact request it makes and what comes back.
List the sending account's network
MCP toolMedium riskFirst-degree connections of the connected sender account, up to two hundred per call. It is that account's network, not the network of whoever is signed into the app — which is exactly the distinction that matters when the sender is a dedicated account.
Your LinkedIn session · list_linkedin_connections
Read what someone has posted
MCP toolMedium riskUp to twenty recent posts by one member, newest first, with reposts flagged. An empty array — not an error — is the normal answer for a senior buyer who does not post, and a workflow has to handle that as a case rather than as a failure.
Your LinkedIn session · get_linkedin_posts
Read one profile in depth
MCP toolMedium riskOne call returns identity, current role and the date it started, follower count, the premium flag and the latest post. Every enrichment field is best-effort: a profile that hides its activity still returns its identity, with the post fields simply absent.
Your LinkedIn session · get_linkedin_profile
Find people matching an ICP
MCP toolMedium riskRuns an ICP description through a connected account's LinkedIn search and returns up to 50 profiles per call. Profiles LinkedIn masks as "LinkedIn Member" because they are out of network are dropped rather than returned with a blank name. Typed Sales Navigator filters are used only when the account has a Navigator seat; otherwise every criterion is folded into one keyword string.
Your LinkedIn session · search_linkedin_people
See which LinkedIn identity is available
MCP toolLow riskThe accounts this workspace can act as, each with status, warm-up stage, how much of today's invite and message budget is spent, and a health score. Reads our own database, so it costs nothing against the LinkedIn rate limit and is the cheapest first call an agent can make.
Read only · list_sender_accounts
Check the remaining LinkedIn budget
MCP toolLow riskHow many LinkedIn tool calls this workspace has made this month, broken down by tool, plus the rate limit in force. The call an agent makes to pace itself instead of discovering the limit by hitting it.
Read only · get_usage
Write the ask to the connector, not to the target
AI skillLow riskAn introduction request is written for the person being asked to spend their reputation, which makes it a different artifact from an opener: it names what you want, why them, and gives them a forwardable paragraph so saying yes costs one click. It also states plainly when the honest answer is not to ask — a connection whose headline is the only evidence of the relationship is not a warm path.
Human approves
Triage a connection list from headlines alone
AI skillLow risklist_connections returns a name, a headline and a public identifier — no company field and no location. This is the judgement for working with that: how to read employer and seniority out of headline text, when the headline is too ambiguous to trust, and which candidates are worth spending a profile call on. It exists because the alternative, reading every connection's profile, costs one LinkedIn call each and is how a warm-path check turns into a rate-limit wall.
Read only
Write a brief on one person
AI skillLow riskCompresses a profile and its posts into a one-screen brief in which every claim names the call that produced it. Anything the tools did not return is written as "not visible" rather than inferred, because an invented detail in a first message is worse than a missing one.
Read only
Find a warm path in
AI skillLow riskIntersects the sending account's first-degree connections with a target's company to tell you whether there is an introduction to ask for. It answers from the sender's network only; it cannot see anybody else's connections.
Read only
From a target company to an introduction you can send
WorkflowMedium riskRead the sending account's connections once, triage them against the target by headline, spend profile calls only on the candidates that survive, check what the connector has been posting about, and produce one intro request per real path — plus an explicit "no warm path here" when that is the answer. One connections call for the whole session, then a handful per candidate.
Human approves
Read a LinkedIn company page
Planned — not available yetMedium riskNot built yet. No tool reads a company page, so headcount, follower count and the company's own description are not available to any product here. Company research is done from the people a search returns, which is a sample, not a roster.
Your LinkedIn session
Write a researched lead into a CRM
Planned — not available yetLow riskNot built yet. Research comes out as files you own. There is no CRM write path, so the last step is still a copy-paste or an import.
Official API
2 capabilities are marked planned: nothing fulfils them today. They are listed because the roadmap should be visible, and they do not run when you install this.
A worked example
Lifted from the kit’s own EXAMPLES.md — list_sender_accounts — whose network is this. Real request and response shapes from the endpoint. Field names are exact; values are illustrative and marked where they are.
{}{
"accounts": [
{
"id": "snd_02",
"name": "Marcus Feld",
"status": "active",
"connected": true,
"warmupStage": 4,
"dailyInviteLimit": 24,
"dailyInviteSent": 11,
"dailyMsgLimit": 40,
"dailyMsgSent": 6,
"health": { "score": 92, "level": "good" }
}
],
"default": "snd_02"
}What is included
- A triage rubric for connection lists, which arrive with a headline and nothing else
- The warm-path run: one connections call for the whole session, then a handful per candidate
- An introduction request written for the person being asked, with a forwardable paragraph
- The refusal case, written down: when the honest answer is that this is not a warm path
The files
| File | What it holds |
|---|---|
| README.md | What it is, what it needs, what it cannot do, and what is in the directory. |
| INSTALL.md | The exact commands for Claude Code, Claude Desktop, Cursor and VS Code, plus a call that proves the connection before you trust it. |
| AGENT.md | The agent definition to paste into your client's project instructions: role, tool budget, rules, and where it stops. |
| SKILL.md | The judgement written down — the rubric, what counts as evidence, and what to write when the evidence is not there. |
| WORKFLOW.md | The run step by step, with the exact tool calls, the cost of each, and the human gate it ends at. |
| PROMPTS.md | Prompts to paste, each one naming the tools it will spend. |
| EXAMPLES.md | Real request and response shapes from the endpoint, with illustrative values and the field names that are not. |
| TROUBLESHOOTING.md | The errors this endpoint actually returns, quoted verbatim, and what each one means. |
| .env.example | The values the install asks for, in one place. Nothing in the kit reads it by itself. |
What it cannot do
Printed before you pay, not after you ask for a refund.
- It reads the SENDING account's connections, not yours. On a managed account those are different networks, and the introduction will come from that person, not from you.
- One call returns at most 200 connections and there is no paging. A larger network is seen in part, and the kit says so in the output instead of implying it read everything.
- A connection comes back as a name, a headline and a public identifier — no company field, no location. Employer is read out of headline text, or confirmed by spending a profile call.
- Nothing is sent. The intro request lands in a file for you to send yourself, from your own account, in your own words.
- No company page and no employee roster. The target list at a company is built from a people search, which is a sample.
What a run costs: 1 call for the connection list, reused all session. Then 1–2 per candidate you confirm. A target company with six plausible connectors is ≈ 9 calls. The endpoint allows a fixed number of LinkedIn calls per five minutes per workspace, which is documented per tool.
Install
No install commands published for this product. The endpoint its tools run on is documented on the Claude setup page, and the tools themselves on the tool reference.
Compatibility
| Target | Supported |
|---|---|
| Claude | Yes |
| Cursor | Yes |
| VS Code | Yes |
| Run here | No — hosted seats are a separate tier |
| Download | Yes |
What you need before it runs
- A TopClozer workspace API key
- A connected LinkedIn account whose network is the one you actually want to mine
- An MCP-capable client
LinkedIn plan: A free LinkedIn account is enough, and Sales Navigator changes nothing here: this reads the connections the account already has, which no plan extends.
Security and risk
Medium risk. Acts through your own session or writes with a human approving each action. Restriction is unlikely but not impossible.
Human approves. Drafts the action; nothing irreversible happens until a person presses send.
The live MCP endpoint is read-only by design, and the outreach engine keeps every irreversible action behind a human approval gate. None of that is LinkedIn endorsing any of this, and nobody can promise your account will not be restricted — least of all a vendor selling you automation. What we store and who can read it is a separate page, and it is the one that answers that question.
Provider: TopClozer — a verified seller: we wrote it, we maintain it, and the support request comes to us.
Pricing
$49 — A skill plus MCP wiring, workflows and the files they read. The whole ladder is on the pricing page.
No payment processor is connected to this site, so nothing here can charge a card — and a button that looked like it could would be the lie this catalogue exists to avoid. What happens instead: the order button writes a real pending purchase against your workspace and hands you its reference, a person invoices you, and marking that order paid is what puts the files in your library. Slower than a card, and every step of it is real.
Version history
v1.0.02026-09-20
First release. Headline triage rubric, the one-call warm-path run, the introduction request format and the explicit no-path case.
Reviews
Nothing here. A review appears on this page only when it is attached to a verified purchase of this product, and none has been published. An empty section is the correct state for a catalogue this young — the alternative is the kind of testimonial that means nothing to the person reading it.
Related products
Company Research Kit
Map an account from its people, because nothing here reads a company page.
Capabilities
$49
LinkedIn SDR Kit
From an ICP to approved first messages, with a stop where the send button would be.
Capabilities
$49
Prospect Research Kit
One screen on one person, with every claim traced to the call that returned it.
Capabilities
$49