Short.io vs LinkedIn Campaign Manager
Short.io is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). LinkedIn Campaign Manager is an MCP server published by ZLeventer. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  Short.io | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Downloads/month (npm): 102 Downloads/week (npm): 8 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 | Short.io | LinkedIn Campaign Manager |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (ai-assistant.short.io/mcp) | On your machine (linkedin-campaign-manager-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/zleventer/linkedin-campaign-manager-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | no remote endpoint we check |
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
Short.io
Access to Short.io's link shortener and analytics tools.
LinkedIn Campaign Manager
MCP server for LinkedIn Ads — 19 read-only tools for campaigns, performance, and Lead Gen Forms.
How to run each
Short.io As a remote MCP server
claude mcp add --transport http short-io https://ai-assistant.short.io/mcpRequires: SHORT_IO_API_KEY (secret)
LinkedIn Campaign Manager As a local MCP server: npm package
claude mcp add --env "LINKEDIN_CLIENT_ID=<YOUR_LINKEDIN_CLIENT_ID>" --env "LINKEDIN_CLIENT_SECRET=<YOUR_LINKEDIN_CLIENT_SECRET>" --env "LINKEDIN_TOKEN_PATH=<YOUR_LINKEDIN_TOKEN_PATH>" --transport stdio linkedin-campaign-manager-mcp -- npx -y linkedin-campaign-manager-mcpRequires: LINKEDIN_CLIENT_ID (secret), LINKEDIN_CLIENT_SECRET (secret), LINKEDIN_TOKEN_PATH
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Short.io 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
Only Short.io asks for
SHORT_IO_API_KEY (secret)
Only LinkedIn Campaign Manager asks for
LINKEDIN_API_VERSIONLINKEDIN_CLIENT_ID (secret)LINKEDIN_CLIENT_SECRET (secret)LINKEDIN_DEFAULT_AD_ACCOUNTLINKEDIN_TOKEN_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Short.io · What it can do: LinkedIn Campaign Manager · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.