afterlaunch-growth vs Plyto
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. Plyto is an MCP server published by plyto.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  Plyto | |
|---|---|---|
| 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.1.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 · | Plyto |
|---|---|---|
| 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 (plyto.ai/api/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 (differs) | 4 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour 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 afterlaunch-growth
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
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.
-
Marketing analysis suite with 7 skills and 4 parallel agents — audit paid campaigns, find SEO opportunities, detect churn signals, and generate branded PDF reports. Powered by a…
-
Open-source AI skills for SEO, marketing, and business operations in Claude Code and Codex. Installs the complete pack, including code review, app delivery, and creator workflows.
-
A Model Context Protocol (MCP) server that empowers LLMs to use some of Open Srategy Partners' core writing and product marketing techniques.
-
A comprehensive registry of 28+ Go-To-Market, Technical Marketing, and Growth Automation skills. This plugin empowers Claude with specialized, pre-configured capabilities for SEO…
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.
Plyto
AI that makes and runs your Google and Facebook ads from your own account, with a CRM behind it.
How to run each
afterlaunch-growth
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Plyto As a remote MCP server
claude mcp add --transport http crm https://plyto.ai/api/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 Plyto 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: Plyto · 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.