vibe-aso vs Applyra
vibe-aso is a plugin bundle for AI coding tools published by Kronop. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Applyra is an MCP server published by applyra.io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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 |  Applyra | |
|---|---|---|
| Community marketplace kronop/vibe-aso | Listed Version: 0.1.0 Forks (GitHub): 47 Stars (GitHub): 467 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.8.0 Downloads/month (npm): 1 643 Downloads/week (npm): 133 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.8.0 Downloads/month (npm): 1 643 Downloads/week (npm): 133 Forks (GitHub): 0 Stars (GitHub): 0 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 | vibe-aso | Applyra |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 467 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 47 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/kronop/vibe-aso | github.com/applyra-io/mcp-server |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-26 | 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. 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
vibe-aso
You vibe-coded the app — now vibe the ASO. Keyword research, 50-locale App Store metadata, localized screenshots, worldwide pricing, in-app localization, and a verified submission checklist, end to end from Claude Code.
Applyra
App Store Optimization data for AI agents: keyword ranks, scores, competitors, charts
How to run each
vibe-aso As a Claude Code plugin
/plugin marketplace add kronop/vibe-aso
/plugin install vibe-aso@vibe-aso-marketplaceApplyra As a remote MCP server
claude mcp add --transport http applyra https://www.applyra.io/api/mcpRequires: APPLYRA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Applyra 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 vibe-aso publish no settings it asks for, so we do not compare settings.
What it can do: vibe-aso · What it can do: Applyra · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.