Research mobile apps, onboarding, paywalls, and competitors with real screens, flows, and reviews.
com.screensdesign/screensdesign Model Context Protocol (MCP) Server
The com.screensdesign/screensdesign MCP server is described as focused on research for mobile apps. It targets onboarding, paywalls, and competitors by using real screens, complete flows, and available reviews to support analysis.
🛠️ Key Features
Research mobile apps
Onboarding research with real screens and flows
Paywalls research with real screens and flows
Competitor research with real screens, flows, and reviews
🚀 Use Cases
Study onboarding patterns in existing mobile apps
Evaluate paywall screen sequences and user journeys
Compare competitors using documented screens, flows, and reviews
⚡ Developer Benefits
Provides grounded context from real app screens and flows
Includes review data alongside visual flow information
⚠️ Limitations
The available description does not specify exposed tools, data access methods, or toolCount
Give your AI agent real app screens, complete flows, and market context to work from.
The ScreensDesign MCP is a hosted server for researching mobile apps, comparing onboarding and paywalls, exploring App Store reviews, and finding visual references. Connect it to your MCP client to bring real screens, recorded flows, and market context into your research.
This public repository contains setup documentation, registry metadata, and the optional screensdesign-data companion skill. The hosted server implementation and ScreensDesign data are operated separately.
Authentication uses browser OAuth. If the tools do not appear after setup, refresh the MCP connection or start a new conversation. See connection troubleshooting for more detail.
What the MCP does
The server provides tools for researching apps, screens, flows, reviews, and saved collections:
Research task
What you get
Discover apps and competitors
Apps matched by product, category, positioning, or recorded UI, with revenue and download estimates where available.
Study onboarding and paywalls
Recorded screens, chronological replays, and stored flows that show how a journey unfolds.
Find UI references
Relevant screens across apps, focused searches within an app, and visual matches to a reference image.
Explore the broader app market
Competitor discovery, public app listings, and App Store reviews for researching recurring complaints and positioning.
Research App Store creatives
Marketing screenshots searched separately from recorded in-app screens.
Continue saved research
Your saved app collections and developer portfolios brought into the conversation.
The optional screensdesign-data skill guides agents to check replay context before making claims about screen order and link findings to the supplied app, screen, or flow sources. It distinguishes observed UI from inference and treats revenue and downloads as performance signals, not proof of conversion.
Try it
With the MCP connected, ask your agent:
Compare onboarding in three high-revenue habit trackers. Show the recorded screens in order and where each paywall appears.
Find apps similar to my sleep app idea. Compare their positioning and summarize recurring complaints in their public App Store reviews.
Find paywalls that show an annual subscription as a price per day. Link to the actual screens.
Find app screens visually similar to this screenshot. Explain which layout and navigation patterns are shared.
Compare the App Store screenshot messaging of three meditation apps. Which benefits does each lead with?
Open my saved app collection and compare the onboarding patterns across its apps.
Optional companion skill
The MCP works without installing a skill. For agents that support skills, screensdesign-data adds guidance on choosing research tools, checking evidence, and citing sources.
server.json describes the hosted ScreensDesign MCP server for the official MCP Registry under com.screensdesign/screensdesign. It includes the public repository, remote endpoint, display name, icon, and setup link. Registry metadata version 1.0.1 is maintained separately from the data-skill release.
Changes to this file must be published to the official MCP Registry with mcp-publisher publish after authenticating for the com.screensdesign namespace. Pushing a Git branch does not update the registry. Verify the repository field and version in the latest registry record after publishing.
The endpoint uses browser OAuth; complete sign-in in your MCP client. This repository contains the companion skill and registry metadata. The hosted server implementation and ScreensDesign data are operated separately.
The current data-skill release is 1.0.8. When connected, the agent checks its installed version once per conversation through get_screensdesign_skill to learn whether it is current or needs an update.
For maintainers: release process
Each release uses a semantic Git tag matching the version declared in screensdesign-data/SKILL.md. For the current release:
The release manifest records immutable content and ZIP hashes. Pushing the matching tag validates the package and creates a GitHub Release with the ZIP and manifest. The hosted MCP vendors that exact package for authenticated clients to read or download through MCP resources.
