abm-dev vs gtm-api: LinkedIn MCP Server
abm-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
abm-dev is a plugin bundle for AI coding tools published by abm.dev. No marketplace we read lists it any more. 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-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  gtm-api: LinkedIn MCP Server | |
|---|---|---|
| Community marketplace abm-dev-git/abm-mcp | Removed on 2026-10-16 Version: 0.1.0-47ab19d9 Forks (GitHub): 1 Stars (GitHub): 1 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 | abm-devno longer listed · | gtm-api: LinkedIn MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 91 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.abm.dev/mcp) | 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) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/abm-dev-git/abm-mcp | github.com/gtm-api/linkedin-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of abm-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Prospect, enrich leads, and bulk-load outreach sequences with Apollo.io. Includes 3 powerful skills: enrich-lead, prospect, and sequence-load for complete sales automation.
-
Saleshandy prospecting and enrichment for Claude Code — natural-language ICP search and one-shot lead enrichment, wired through the Saleshandy MCP server.
-
Prospect, enrich leads, and load outreach sequences with Apollo.io — one-click MCP server integration for Claude Code and Cowork.
-
Prospect, enrich leads, load outreach sequences, and query sales analytics with Apollo.io — one-click MCP server integration for Claude Code and Cowork.
-
Search people and companies, enrich leads, run sequences.
-
Apollo.io MCP server for prospecting, enrichment, CRM, sequences, and outreach workflows
What each says it does
abm-dev
Enrich B2B people & companies with cited multi-source data (verified work emails, LinkedIn, firmographics, AI research), search/source people at target accounts, and write results back to your CRM. Bundles the abm.dev skill and the MCP connector — zero-paste install.
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
abm-dev
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 abm-dev publish no settings it asks for, so we do not compare settings.
What it can do: abm-dev · What it can do: gtm-api: LinkedIn MCP Server · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.