La Growth Machine MCP

It can reach everything you can, which is the point and the problem. Section 8.2 of the User Agreement bars bots and scraping by any means, and enforcement lands on the account rather than on the software.

The server writes to LinkedIn as you, over a route LinkedIn does not sanction. Automated messages and connection requests under a member’s own name are what the enforcement is built to catch, and the account is what it acts on.

You supply no credential by hand. On the first tool call the client opens a browser tab to sign in to La Growth Machine; the installer documents this explicitly — "Auth is handled by the MCP itself... no API key to copy, nothing to paste". LinkedIn credentials are never given to the MCP server. LinkedIn is reached through an identity already connected inside the workspace, and an identity-listing tool returns the identifier that every LinkedIn-touching write tool requires. The session that actually drives LinkedIn is the vendor's, not yours — which is why this is filed as a browser server rather than a vendor one.

No Docker, no browser to run yourself, no API key, no local server. What is actually required: Node 18 or newer and npx for the installer; the Claude Code CLI if you want the installer to register the server automatically; Python 3 for the helper scripts several skills ship; an active La Growth Machine subscription with at least one LinkedIn or email identity already connected, which is the thing that actually touches LinkedIn; an active Sales Navigator subscription for the Sales Navigator URLs to resolve; and, optionally, a HubSpot MCP server for two of the skills.

Claude Code; Claude.ai web (custom connector); Cursor; Codex; Amp; ChatGPT (per the vendor MCP page); n8n (per the vendor MCP page). Where the file goes in each Claude surface. The same block in Cursor. What a ChatGPT connector can and cannot reach.

streamable-http against the vendor endpoint.

Remote, run by the vendor. Nothing runs on your machine; the client connects over HTTP. An unauthenticated request to the endpoint returns 401, consistent with an OAuth-protected remote server.

Supported indirectly, and only with your own seat. A bundled skill turns a plain-English ideal-customer description into a Sales Navigator search URL using reference taxonomies for industries, seniority, functions, headcount, geography, company type, languages and year ranges. Its README states the prerequisite plainly: "an active Sales Navigator subscription to open the resulting URL... LinkedIn redirects to an upsell page otherwise." The audience-import tool then imports that search. The MCP server does not query a Sales Navigator API.

No Recruiter tool, no Recruiter seat integration, no InMail tool. Recruiter appears twice in the repository, both times in passing.

The account risk is real but narrower than most, for a structural reason: the MCP server holds no LinkedIn cookie or password. Every LinkedIn action runs through an identity you already connected inside La Growth Machine, and the vendor's own automation limits apply. Three tools act on LinkedIn: sending a real message or voice note, importing an audience by scraping a search or a post's likers and commenters, and refreshing a lead's LinkedIn fields. A fourth reads a public post from its URL. Automated scraping and automated messaging both conflict with the User Agreement, which prohibits software that scrapes or automates activity; restriction or permanent ban is the platform's remedy, and it falls on your personal account, not on the vendor. Two things materially lower the blast radius. First, there is no launch tool, deliberately — one skill states "There is no launch tool, on purpose." Campaigns are created and filled as drafts; a human opens the app, attaches the audience and starts the sequence. Second, the skills confirm before every state change, naming the identity that will act, before scrapes, before the first campaign write, before enrichment that spends credits, and before sending replies. No tool exists to send a connection request, post, comment, react or send an InMail directly; connection requests happen only inside a campaign a human launched. Credit spend is a separate cost risk.

The headline install is a curl-piped-into-shell bootstrap; the README and the script's own header offer a download-and-read path first. The script installs skills globally for three clients and writes the MCP entry at user scope, so it is active in every project rather than only the one it was run in. An environment variable skips the MCP registration. All the links in the skills are tagged and point back at the vendor; several skills end with a marketing call to action, which is worth knowing before wiring them into a team's default skill set. The server is closed-source and vendor-operated: leads, full inbox threads, campaign copy and CRM-adjacent data pass through it. The SQL tool executes read-only queries over the workspace's own activity logs.