linkedin-agent vs Google Workspace (gsuite-sdk)
linkedin-agent is a plugin bundle for AI coding tools published by Jake Schincariol. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Google Workspace (gsuite-sdk) is an MCP server published by PabloAlaniz. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. 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 |  Google Workspace (gsuite-sdk) | |
|---|---|---|
| Community marketplace jakeschincariol/linkedin-agent-skill | Listed Version: 1.0.0 Forks (GitHub): 410 Stars (GitHub): 2 616 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.9.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 408 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.9.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 408 Forks (GitHub): 0 Stars (GitHub): 0 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-agent | Google Workspace (gsuite-sdk) |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 616 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 410 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gsuite-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/jakeschincariol/linkedin-agent-skill | github.com/pabloalaniz/google-suite |
| Changes in the last 7 days (differs) | 2 | 5 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
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-agent
Eleven Claude skills that run a LinkedIn account, including a humanizer that strips the AI fingerprint and scores the draft on a five-check panel.
Google Workspace (gsuite-sdk)
Gmail, Calendar, Drive, Sheets, Tasks and Contacts for agents, with your own Google login
How to run each
linkedin-agent As a Claude Code plugin
/plugin marketplace add jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skillGoogle Workspace (gsuite-sdk) As a local MCP server: PyPI package
claude mcp add --env "GSUITE_TOKEN_DB_PATH=<YOUR_GSUITE_TOKEN_DB_PATH>" --transport stdio gsuite-sdk -- uvx gsuite-mcpRequires: GSUITE_TOKEN_DB_PATH
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of linkedin-agent publish no settings it asks for, so we do not compare settings.
What it can do: linkedin-agent · What it can do: Google Workspace (gsuite-sdk) · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.