ScreensDesign

ScreensDesign MCP

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.

Website · Connect the MCP · Browse on skills.sh · Releases

Connect the ScreensDesign MCP

Add this hosted endpoint to your MCP client using Streamable HTTP and sign in with your ScreensDesign account:

https://api.screensdesign.com/v1/mcp

MCP access is included with ScreensDesign Pro. See the setup page for supported clients and access details.

Claude Code

claude mcp add --transport http screensdesign "https://api.screensdesign.com/v1/mcp" --scope user

claude mcp login screensdesign

You can also open /mcp inside Claude Code to check the connection and authenticate.

Codex

codex mcp add screensdesign --url 'https://api.screensdesign.com/v1/mcp'

codex mcp login screensdesign

Cursor

Add this server to your Cursor MCP configuration:

{

"mcpServers": { "screensdesign": { "url": "https://api.screensdesign.com/v1/mcp" } } }

Complete the browser sign-in when prompted.

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:

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.

Run this from your project root:

npx skills@latest add screensdesign-com/screensdesign-agent-skill --skill screensdesign-data

Then connect the ScreensDesign MCP. The skill provides research instructions; the MCP provides access to the data through your ScreensDesign account.

Agent-specific, global, and versioned installation

Install for specific agents without prompts:

npx skills@latest add screensdesign-com/screensdesign-agent-skill --skill screensdesign-data -a claude-code -a codex -a cursor -y

Install across your projects:

npx skills@latest add screensdesign-com/screensdesign-agent-skill --skill screensdesign-data -g

Install the exact v1.0.8 release:

npx skills@latest add https://github.com/screensdesign-com/screensdesign-agent-skill/tree/v1.0.8/screensdesign-data

Update an installed copy:

npx skills@latest update screensdesign-data

MCP registry metadata

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.

How it works

The skill stays compact and loads focused guides for app research, market and review research, screen and flow research, app intelligence, and saved collections as needed.

The tool reference and response field guide document the research interface. Live MCP schemas take precedence when a tool changes.

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:

python3 scripts/build_release.py --write-manifest

python3 scripts/build_release.py --check --tag v1.0.8

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.

License

MIT © 2026 ScreensDesign. The ScreensDesign name and logo are brand assets; this license does not grant trademark rights.

---

Built by ScreensDesign — real app screens, recorded flows, and market intelligence for your next product decision.