afterlaunch-growth vs AdWeave — Meta Ads MCP Server
afterlaunch-growth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
afterlaunch-growth is a plugin bundle for AI coding tools published by AfterLaunch. No marketplace we read lists it any more. AdWeave — Meta Ads MCP Server is an MCP server published by adweave.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 | ||
|---|---|---|
| Community marketplace afterlaunch/mcp | Removed on 2026-10-17 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | afterlaunch-growthno longer listed · | AdWeave — Meta Ads MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (afterlaunch.io/api/mcp) | Remote server (mcp.adweave.ai/meta-ads-mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/afterlaunch/mcp | Not stated |
| Changes in the last 7 days | 0 | 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, requires a key |
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 afterlaunch-growth
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
47 marketing skills across 8 pods: Content, SEO & AEO, CRO, Channels, Growth, Intelligence, Sales enablement, and X/Twitter growth. 62 Python tools, 89 reference docs.
-
AI marketing skills for e-commerce brands: reports, campaign management, and creative generation.
-
AI marketing copilot: brand intelligence, campaigns, content, CRM, SEO, and skills for Claude.
-
SEO, copywriting, positioning, CRO and growth.
-
An entire marketing department as one Claude skill. 14 modules: audits scored 0-100, an 18-tactic hook engine, copy graded before you see it, ad diagnosis, GEO, email, launches…
-
This skill transforms Claude into a Marketing Technology (MarTech) specialist. Use it to get expert advice on building and optimizing your MarTech stack, selecting the right…
What each says it does
afterlaunch-growth
Run growth marketing, SEO and AI answer-engine visibility for a product through AfterLaunch over MCP. Reads a ranked backlog of prepared, ready-to-ship growth moves.
AdWeave — Meta Ads MCP Server
Meta Ads MCP server with 47 tools for campaigns, creatives, audiences, and insights.
How to run each
afterlaunch-growth
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
AdWeave — Meta Ads MCP Server As a remote MCP server
claude mcp add --transport http meta-ads-mcp https://mcp.adweave.ai/meta-ads-mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AdWeave — Meta Ads 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
Neither one's marketplaces publish the settings it asks for.
What it can do: afterlaunch-growth · What it can do: AdWeave — Meta Ads 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.