Inspiration
What it does
How we built it
Challenges we ran into
Accomplishments that we're proud of
What we learned
What's next for ShipASO
Inspiration
App Store Optimization is a high-leverage workflow with a sharp boundary: an agent can do the research and drafting, but a person should retain the approval decision.
What it does
ShipASO watches app listings, keywords, and competitors. When a change matters, it prepares a proposal: title, subtitle, keywords, and promotional text at their exact character limits. On a run page, WebMCP tools let an agent read the queue, explain why a proposal exists, draft an alternative that preserves the brand, and stage it for review.
The agent never gets an approval, publish, ship, or push tool. Staging changes what a person will review; it leaves the run awaiting approval.
How it uses WebMCP
ShipASO declares 14 page-scoped WebMCP tools. The browser reads the live tool list after registration, so the interface distinguishes a declared manifest from tools the browser actually received. Read and draft tools are available where they make sense; run-specific tools appear only on a run detail page.
The boundary is also enforced on the server. Approval requires a single-use challenge issued when a run is opened and consumed with the approval update. That prevents replay and makes bulk approval follow the same per-run protection.
What we learned
Tool descriptions are not a security boundary. WebMCP makes the page's intended contract legible to agents, but server-side enforcement is still required for consequential actions. We deliberately built both: helpful tools for analysis and drafting, and a separate human decision point.
Built with
TypeScript, React, Cloudflare Workers, D1, WebMCP, App Store Connect integrations, and a standard-library Python ASO engine.
Log in or sign up for Devpost to join the conversation.