Show HN: AppMetaHub – Update App Store Metadata from Claude Code via MCP | Hacker News Reader

Show HN: AppMetaHub – Update App Store Metadata from Claude Code via MCP

appmetahub.com

1 pointvladosce3 comments

I built a web dashboard for editing App Store Connect metadata across all 37 locales. One dashboard, word-level diffs, one-click push to ASC.

The part I think HN will find interesting: it ships with a full MCP server (30 tools). Claude Code, Cursor, or any MCP client can read your metadata, edit keywords across all locales, and push to App Store Connect - without leaving your IDE. One prompt can update 37 locales.

The pain: every iOS release I'd spend 3-4 hours tab-switching in App Store Connect. One locale at a time. No history, no diffs, no undo.

Free for 1 app (no credit card, no trial expiration). Indie plan is $10/mo annual for 5 apps + MCP server + all locales.

Open articleView on HN

The MCP angle is genuinely clever — turning metadata management into something Claude can batch-process across locales is a real time unlock.

Curious how you're handling the prompt-to-push workflow in practice. Like, are people writing their own prompts from scratch, or are you shipping example prompts that say "optimize keywords for [target audience] across all locales"? That last mile of "but what do I actually type" trips up a lot of otherwise solid MCP integrations.

Also — the 3-4 hour pain point is real and I've felt it. But I'd bet your strongest conversion argument isn't time saved, it's mistakes avoided. Wrong locale, wrong character count, accidentally overwriting a localization a contractor did 6 months ago. The diff/history story might be undersold in your current framing.

What's your current distribution strategy? Indie iOS devs are a notoriously tight word-of-mouth community if you can crack the right subreddits and discords.

Thanks, really solid feedback.

On prompts — in the web dashboard we have AI with deep ASO knowledge baked in, so the suggestions are already tuned for App Store best practices. With the MCP server it depends more on your input, but that's also the flexibility — you can prompt however you want. Shipping example prompts and recipes for common MCP workflows is next on the list.

On mistakes avoided vs time saved — you put a bug in my head with that one. I've personally pushed wrong locales and only caught it days later. The diff/history story is definitely undersold. Going to A/B test the landing page with that framing and see if it converts better.

Distribution — honestly early days. Show HN, Reddit, Twitter so far. Would love to hear which subreddits or discords you'd recommend if you have any in mind.

A/B testing is great, but early stages have to trust your gut/experience on it until you can get some more feedback through the testing.

For distribution: r/iOSProgramming and r/indiegaming are worth a shot, but the real gold is usually the smaller discords. RevenueCat's community has a solid indie dev contingent. Same with some of the Superwall and Adapty Slack groups — people actively talking monetization and store optimization, which is your exact user.

One tactic that works: share the "wrong locale, caught it days later" story authentically. Not as marketing copy — just as a post. That'll land harder than any feature announcement IMO.

Reply on news.ycombinator.com