Who builds TopClozer, and why the MCP server exists
TopClozer is a LinkedIn outreach engine with a Model Context Protocol server in front of it. This page is the colophon: what we build, what we refuse to build, and where the boundaries are drawn. It is written to be checked, not believed.
Updated 2026-09-10 · server 2.0.0 · protocol 2025-06-18
Scope
What we build
- The outreach engine
- Sequences, AI-drafted touches, a unified inbox across every connected sender account, a REST API and webhooks.
- The MCP server
- One HTTP endpoint, JSON-RPC 2.0, bearer auth, 65 tools. It is the reason this domain exists.
- The docs you are reading
- Generated from the same array the endpoint serves, so a page cannot document a tool the server does not implement.
What we do not build
- LinkedIn accounts
- We do not create, sell, warm or rent them. The workspace connects one; where it comes from is your decision, and the honest options are compared on accounts for agents.
- Autonomous sending
- No tool sends an invite, a message or a reply. Outbound is released by the product under the workspace sending policy, which by default waits for a person.
- A LinkedIn partnership
- There is no official API for this. TopClozer is not affiliated with LinkedIn, and automating a profile carries platform risk we can reduce but not remove.
The account is your problem, and we would rather say so
The tools operate a workspace, and a workspace only sends from a connected LinkedIn account. Pointing automation at your own profile is against LinkedIn's User Agreement. We do not sell accounts, so we have nothing to gain from the advice: Outzeach rents managed accounts, 500accs sells aged ones outright, and the trade-offs between them are laid out on accounts for agents.
Rationale
Why the server exposes 65 tools and not sixty
46 read. 19 write. Every one of them existed in the product before it existed in the protocol — nothing was added to the server to make the tool list look longer.
01Because the interesting half of outreach is reading, not sending
The questions people actually ask a workspace — which campaign is dying, what came in overnight, which drafts are stuck waiting on someone — are read questions. A model answers them well and answers them cheaply. So the read surface went out first and went out whole, and writes came later and only as proposals a person approves: every tool but the 15 propose_* tools, which queue an action for a person to approve, and connect_linkedin_account, add_do_not_contact, pause_campaign and install_product, which change only this workspace returns state, and no argument on any of them can change anything.
02Because the one outreach write worth exposing is the stop button
pause_campaign is the only tool that changes a campaign. It is the action you want available at 2am when a sequence is going badly, and it is safe in a way sending never is: pausing a paused campaign changes nothing, and nothing that has been paused has been sent. There is no resume tool for the same reason — restarting is a decision, not a correction.
03Because a protocol beats twenty-four integration pages
This site used to carry a page per logo — a HubSpot page, a Salesforce page, a Slack page — each promising a connection that was really just an HTTP call. One documented endpoint replaces all of them, and it is honest about the seams: you still write the glue on your side, and we tell you which pieces you have to write.
Verify
Do not take our word for it
An unauthenticated GET on the endpoint returns the server name, version and full tool list. If this page and that response ever disagree, the response is right and the page is a bug — report it.
# every claim on this page about the tool surface is one request away
curl -s https://topclozer.com/api/mcp | jq '{name, version, tools: [.tools[].name]}'The per-tool contracts are in the tool reference, the install is on the Claude setup page, and what a connected key is authorized to do is on security.
Contact
Where to send things
- Bug in the docs or the endpointhelp@topclozer.com
- Security reportsecurity@topclozer.com
- Anything with a human on the other endBook a call
The software is priced per connected account on pricing — the MCP endpoint and the REST API are included in it, with no per-call charge and no MCP tier.