linkedin-poster vs LigoSocial (LiGo) for LinkedIn
linkedin-poster is a plugin bundle for AI coding tools published by cnfcnf. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LigoSocial (LiGo) for LinkedIn is an MCP server published by ligosocial.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-02. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  linkedin-poster | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: f3f4fb0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 1 (last published figure) Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | linkedin-poster | LigoSocial (LiGo) for LinkedIn |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (last published figure) | No figure on GitHub |
| Forks (GitHub) (differs) | 0 (last published figure) | No figure on GitHub |
| Last release (differs) | 2026-11-01 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (ligosocial.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cnfcnf/linkedin-poster | Not stated |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
linkedin-poster
Drafts and publishes high-quality LinkedIn posts that sound like the user, not like an AI summary. Reads a reusable per-user profile (interests, audience, voice samples, archetypes, forbidden phrases) and runs a per-post loop: pick an archetype (news reaction, lesson, milestone, provocative question, story), source content, draft 2-3 variants, surface for explicit approval, publish. In Cowork it can auto-fetch voice samples from a LinkedIn profile URL, surface drafts in Dispatch for approval, and auto-type the approved post into LinkedIn at 35-68 WPM. In Claude.ai or the API it works from manually pasted samples and hands the user a copy/paste-ready draft. Anti-mimic guardrail when modeling another writer's style; never clicks Post (the human stays the publisher).
LigoSocial (LiGo) for LinkedIn
Draft LinkedIn posts in your voice, then schedule or publish them through LinkedIn's official API.
How to run each
linkedin-poster As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install linkedin-poster@claude-communityLigoSocial (LiGo) for LinkedIn As a remote MCP server
claude mcp add --transport http ligosocial https://ligosocial.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only LigoSocial (LiGo) for LinkedIn has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: linkedin-poster · What it can do: LigoSocial (LiGo) for LinkedIn · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.