I built a LinkedIn MCP because the most popular one can get your account banned
velvetotter8 · reddit · 2026-11-03
The author surveyed every third-party LinkedIn MCP before building their own on the official API, since LinkedIn publishes none:
- The most popular (stickerdaniel/linkedin-mcp-server) drives your logged-in browser session, can't post, and its own README warns automated access can get your account restricted
- adhikasp/mcp-linkedin runs on an unofficial API and asks for your LinkedIn email and password in config
- The safe OAuth-based option requires registering your own LinkedIn developer app; Composio/Zapier charge per call with limited write actions; Apify/Bright Data are read-only scrapers
Their product ContentIn offers 11 tools (voice-matched writing, scheduling, publishing, analytics, engager lists) with one revocable key per profile. Key safety design: it never posts on its own—it shows the exact text and waits for your yes, because an assistant with publish rights plus a random web page in context is one prompt injection away from posting under your name.
The one question to ask before connecting any LinkedIn MCP: does it use the official API or your session? That decides whether your account survives.
More from coding & agent
- Open-source AI Xianyu monitor with Playwright + LLMs hits 16k GitHub stars — Usagi-org · 2026-11-03
- Developer kicks off a Worms remake built with AI coding tools — ilumine_ai · 2026-11-03
- Creator hires an AI employee 'Viktor' in Slack to fix Claude's teamwork gap — rubenhassid · 2026-11-03
- Surrogate Inference Engine Accused of License-Washing Open-Source Project NInfer — teortaxesTex · 2026-11-03
- FDE tutorial series: turning client business requirements into measurable technical specs — Affectionate_Slip654 · 2026-11-03
- Vibe coding that works: build on solid ground, not the whole stack — springrod · 2026-11-03