appdesigns App Store screenshots MCP server
online · 100% uptimeclick.appdesigns/screenshots·v1.0.0App Store and Google Play screenshots MCP: your agent captures the app, you edit and export. Free.
0 stars
Reviews
Write oneNobody has reviewed appdesigns App Store screenshots yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
appdesigns App Store screenshots tools (4, 1 write)
write = sends, deletes, buys or postscreate_projectwrite actionFreeStarts a screenshot set: 1 to 6 screenshots in store order, each with a screen name and a headline. Returns a project_handle and one upload command (bash and PowerShell forms) that sends every screenshot straight to storage; run it once, then call finish_project with the handle. Upload and call finish_project within 3 hours (an unfinished project lapses then); a finished one waits 72 hours to be opened. Nothing is public and no account is needed; the user saves the set to their account when they open the link finish_project returns.
finish_projectFreeChecks that every screenshot of a project was uploaded and is a real PNG or JPEG, then returns the link that opens the set in the appdesigns editor, where the user saves it to their account and can edit and export it. Calling it again returns a fresh link and retires the previous one.
get_workflowFreeReturns the full appdesigns recipe for one platform and store, as markdown: how to pick the screens, how to check and populate demo data with the user's consent, the exact capture commands (simulator or emulator, status bar, deep links), the caption rules, and the upload and hand-off steps. Read-only; changes nothing.
list_devicesFreeLists the device frames, frame colours and canvas sizes appdesigns offers for one store, with the defaults create_project uses when you leave them out. The App Store gets Apple devices only; Google Play gets Android phones. Read-only.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 365ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How appdesigns App Store screenshots compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 70% of 2,174 E-commerce servers
- Tools
- 4
- the typical E-commerce server has 6
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote E-commerce server answers 100%
- Response time
- 193 ms
- faster than 69% of 1,527 E-commerce servers
What its tools let an agent do: 3 read · 1 create
Install appdesigns App Store screenshots in Claude Code, Cursor or VS Code
claude mcp add --transport http screenshots https://appdesigns.click/api/mcp
What the publisher says
From the appdesigns App Store screenshots repository's README, as published. We do not edit it. Read it on GitHub
App Store screenshots MCP (appdesigns)
A free MCP server that lets your coding agent make App Store and Google Play screenshots of your app. Claude Code, Codex, Cursor, VS Code, Gemini CLI or any MCP client with a shell reads your app, proposes the screens, asks you once before adding demo data, captures each screen at store size and opens a framed, captioned set in the appdesigns editor, where you edit it and export store-ready PNGs.
- Free. No API key, no credits, no sign-in to connect. appdesigns runs no AI model; your agent does the thinking.
- Your real app. The agent captures your actual UI from a simulator, emulator or browser. Nothing is generated.
- Editable. The result is a project in the appdesigns editor, not a flat image: change text, colours, device and layout, then export.
- Both stores. App Store at 1320 × 2868 (6.9 inch) and 13 inch iPad, Google Play at 1080 × 1920.
- Every stack. iOS, Android, Expo, React Native, Flutter and web apps.
Server: https://appdesigns.click/api/mcp (Streamable HTTP, stateless, no auth) Setup page: https://appdesigns.click/mcp Walkthrough: https://appdesigns.click/blog/app-store-screenshots-mcp
Install
Then, in your app's folder:
Make App Store screenshots for this app with appdesigns.
In Claude Code, a server added mid-session loads after a restart: quit, run claude --continue and say "continue".
How it works
for your stack and the rules for screens, demo data and captions.
- The agent calls get_workflow with your platform and store. It returns the capture commands
to capture them, and a caption per screen. It waits for your reply before touching anything, and never touches production data.
- It reads your app and plans 4 or 5 screens, best first.
- It checks in with you once: the screens, the demo data it would add, any code it would change
storage through a signed URL, never through the model), then finish_project.
- It captures each screen at store size with a clean status bar (9:41, full battery).
- It calls create_project, runs the one upload command it returns (each file goes straight to
signing in (free) saves it to your library.
- It opens the link in your browser. The set loads in the editor; export needs no account, and
Tools
The server also exposes an appstorescreenshots prompt (in Claude Code: /mcpappdesignsappstorescreenshots).
What happens to your screenshots
They are uploaded to a private staging area nobody can browse. Saving the set copies them into your own private project and deletes the staged files; an unsaved set is deleted after 72 hours. Nothing becomes public unless you submit a set to the appdesigns gallery yourself.
What is in this repository
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
appdesigns App Store screenshots: common questions
- Is appdesigns App Store screenshots MCP server safe?
- Mostly: it is graded B (80/100). Read the appdesigns App Store screenshots safety report
- How do I install appdesigns App Store screenshots?
- It runs remotely at appdesigns.click. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does appdesigns App Store screenshots need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is appdesigns App Store screenshots maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v1.0.0.
- Is appdesigns App Store screenshots up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of appdesigns App Store screenshots?
- Servers from other publishers that do the same job: AsoBeast MCP server, Storeshots MCP server and Storelift MCP server.
- How does appdesigns App Store screenshots compare with other E-commerce MCP servers?
- safety score 80/100 (higher than 70% of 2,174 E-commerce servers); tools 4 (the typical E-commerce server has 6); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to appdesigns App Store screenshots
Same job from other publishers: the closest match first, then the best rated.
- AsoBeastApp Store and Google Play ASO: keyword rankings, competitors, reviews, audits and an action queue.not reviewedGrowingA
- StoreshotsRender store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes.not reviewedGrowingA
StoreliftApp Store & Google Play keyword ranks, rivals, reviews and AI visibility. Free plan included.not reviewedGrowingA
ApifyExtract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡not reviewedEstablishedA- Mneme MemoryCross-session memory for AI coding agents via six tools; local-first SQLite store.not reviewedEstablishedA
