What it is
The shortest path from an API key to something true on your screen: verify the tool list, name the account you are acting as, read the remaining budget, run one small search, read three profiles and write one brief. Then it stops and tells you what the paid kits do that it does not.
Who it is for
- Anyone deciding whether any of this works before paying for it — including someone with no LinkedIn account connected yet, who can still run the workspace half.
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.
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
Read campaign performance
MCP toolLow riskEvery campaign in the workspace with its live funnel counters — invited, connected, replied — and the two rates already rounded to whole percentages.
Read only · list_campaigns
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
Read the workspace roll-up
MCP toolLow riskSenders, campaigns, leads, invited, connected and replied, counted across the whole workspace. The cheapest way to answer "how is outreach going" without walking every campaign.
Read only · get_stats
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 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
Prove the connection works
WorkflowMedium riskCheck the tool list, name the account being acted as, read the remaining budget, run one small search, read three profiles, hand back one brief, stop. The shortest sequence that produces something real.
Your LinkedIn session
A worked example
Lifted from the kit’s own EXAMPLES.md — Discovery — no key needed. Field names are real. Values are illustrative.
curl -s https://topclozer.com/api/mcp{
"server": "topclozer-mcp",
"version": "2.0.0",
"protocolVersion": "2025-06-18",
"transport": "http",
"auth": "Authorization: Bearer <workspace API key>",
"tools": ["search_linkedin_people", "get_linkedin_profile", "…"],
"surfaces": {
"linkedin": {
"tools": ["search_linkedin_people", "get_linkedin_profile",
"get_linkedin_posts", "list_linkedin_connections"],
"note": "Reads LinkedIn through a connected sender account. Rate limited.",
"rateLimit": { "calls": 30, "windowSeconds": 300, "scope": "workspace" }
},
"workspace": {
"tools": ["list_sender_accounts", "get_usage", "list_campaigns", "…"],
"note": "Reads this workspace's own outreach data. Not rate limited."
}
},
"writes": ["pause_campaign"]
}What is included
- A first-run workflow that ends in one real brief, or in a clear reason it could not
- An agent definition small enough to read in full before you run it
- The connection-verification call and the exact responses that mean it worked
- An honest list of what the paid kits add
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.
- One search of ten and three profile reads. It is a demonstration, not a workday.
- It does not draft outreach, does not keep state between runs and does not write anything but the brief.
- It sends nothing, here or anywhere.
What a run costs: ≈4 LinkedIn calls for the whole run. Well inside one rate-limit window. The endpoint allows a fixed number of LinkedIn calls per five minutes per workspace, which is documented per tool.
Install
These are the commands from the kit’s INSTALL.md, read off disk at build time — so this page and the file you download cannot disagree. Pick the client you work in.
Claude Code
claude mcp add --transport http topclozer https://topclozer.com/api/mcp \
--header "Authorization: Bearer tcz_live_YOUR_KEY"Claude Desktop — custom connector
Settings → Connectors → Add custom connector. That dialog has no header field, so the key goes in the URL.
https://topclozer.com/api/mcp?key=tcz_live_YOUR_KEYClaude Desktop — older builds, via mcp-remote
For builds without native remote connectors, the community bridge in claude_desktop_config.json.
{
"mcpServers": {
"topclozer": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://topclozer.com/api/mcp",
"--header", "Authorization: Bearer tcz_live_YOUR_KEY"]
}
}
}Cursor
.cursor/mcp.json:
{
"mcpServers": {
"topclozer": {
"url": "https://topclozer.com/api/mcp",
"headers": { "Authorization": "Bearer tcz_live_YOUR_KEY" }
}
}
}VS Code
.vscode/mcp.json — the same server, nested under servers, with the transport named explicitly.
{
"servers": {
"topclozer": {
"type": "http",
"url": "https://topclozer.com/api/mcp",
"headers": { "Authorization": "Bearer tcz_live_YOUR_KEY" }
}
}
}Prove it before you trust it
curl -s https://topclozer.com/api/mcp \
-H "Authorization: Bearer tcz_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'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
- An MCP-capable client
- A connected LinkedIn account for the LinkedIn half. Without one, the workspace tools still answer and the agent says so instead of failing.
LinkedIn plan: A free LinkedIn account is enough, and the workspace half of the run needs no LinkedIn account at all.
Security and risk
Medium risk. Acts through your own session or writes with a human approving each action. Restriction is unlikely but not impossible.
Your LinkedIn session. Acts as you, from your connected account, under pacing limits.
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
Free — The starter agent and the hosted MCP endpoint. No card, no seat. 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. The four-call first run, the no-account path, and one honest next-step recommendation.
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
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