Labsco
MCP SERVER

ASO to SEO Data

by quartz-labs-dev ↗

Turn App Store and Google Play listing data into website content and back again — including translated screenshots, platform icons and validated store fields.

Mobile & App Store Release✓ Verified
Summary
One set of listing copy, kept in step across the two stores and the marketing site.

The conversion runs both ways, which is the part that matters: store data becomes site content, and site edits go back as store fields — validated against the character limits before anyone tries to upload them. The asset side is separated on purpose, with screenshot translation and resizing as two steps so you can look at the raw translations before paying to redo them.

What it is

A conversion server between app-store metadata and a web project. It moves ASO data into a site's product folders, prepares edited content for pushing back to the stores, and generates the localized assets that go with it.

What you get
  • Pulled store data converted into public/products/[slug]/ structure, and edited content prepared back into push format with a dry run available
  • Store fields validated against App Store and Google Play limits — name and subtitle 30 characters, keywords 100, description 4000
  • Keyword research prepared and persisted before optimization, with seed keywords, competitor apps and per-locale, per-platform data
  • Optimization instructions generated for a product and locale from your stored keyword research, processed in batches
  • Screenshots translated into other languages and saved as raw images, then resized separately to the source dimensions — so a re-resize does not mean re-translating
  • Phone screenshots converted to tablet ones, keeping the interface and adapting the canvas
  • Platform icons generated from a single base icon: iOS, Android adaptive, splash and Android notification — plus themed or seasonal restyling of the base icon
  • HTML blog posts written per locale under public/blogs/, each carrying a BLOG_META block
  • Registered apps searched by slug, bundle ID, package name or name, filtered to App Store or Google Play
Requirements

Node.js 18 or newer. Run it with npx -y pabal-resource-mcp over stdio; the npm package is pabal-resource-mcp, currently 1.12.0. Set dataDir in ~/.config/pabal-mcp/config.json to the absolute path of your web project — nothing resolves without it. The companion server pabal-store-api-mcp is what fetches the store data in the first place, and its init has to have run before conversion. The image tools call Gemini, so they need GEMINI_API_KEY or GOOGLE_API_KEY, or an apiKey entry in the same config file. Keyword research additionally expects the separate mcp-appstore server.

Setup effort

One command plus a key — npx -y pabal-resource-mcp, then supply credentials