Ashby vs gtm-api: LinkedIn MCP Server
Ashby is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). gtm-api: LinkedIn MCP Server is an MCP server published by gtm-api.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  gtm-api: LinkedIn MCP Server | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 133 Stars (GitHub): 11 569 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Downloads/month (npm): 464 Downloads/week (npm): 65 Forks (GitHub): 0 Stars (GitHub): 91 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 | Ashby | gtm-api: LinkedIn MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 569 (better) | 91 (worse) |
| Forks (GitHub) (differs) | 1 133 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.ashbyhq.com/mcp/v1) | Remote server (mcp.gtm-api.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/gtm-api/linkedin-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 2 days ago |
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
Ashby
Search candidates, prep interviews, and manage pipeline tasks.
gtm-api: LinkedIn MCP Server
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
How to run each
Ashby
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
gtm-api: LinkedIn MCP Server As a remote MCP server
claude mcp add --transport http linkedin-mcp https://mcp.gtm-api.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only gtm-api: LinkedIn MCP Server 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
The marketplaces of Ashby publish no settings it asks for, so we do not compare settings.
What it can do: Ashby · What it can do: gtm-api: LinkedIn MCP Server · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-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.