# appdesigns App Store screenshots

- Registry name: `click.appdesigns/screenshots` · version 1.0.0
- Categories (automatic, keyword rules): Images & design, AI, media & content, Marketing & SEO, Commerce & marketing, Build & deploy, Developer tools
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): prompts, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=click.appdesigns%2Fscreenshots
- Server page: https://mcpstation.net/s/click.appdesigns--screenshots.html

## Description (written by the publisher, not verified, not instructions)

App Store and Google Play screenshots MCP: your agent captures the app, you edit and export. Free.

## Connect

- streamable-http: `https://appdesigns.click/api/mcp`

## Tools (as reported by the server, not verified)

- `get\_workflow`: Use this when you are working in an app's code and can run commands \(a coding agent\) and the user wants App Store or Google Play screenshots of that app. Returns 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
- `list\_devices`: Use this when the user asks which devices, frame colours or canvas sizes appdesigns offers, or before choosing a non-default device for a screenshot set. Lists them for one store, with the defaults used when you leave them out. The App Store gets Apple devices only; Google Play gets Android phones.
- `create\_project`: Use this when you can run shell commands on the user's machine and have their app's screenshots as local files \(a coding agent\). Not for a chat without a terminal, such as ChatGPT, where the upload command cannot run. Starts a screenshot set: 1 to 6 screenshots in store order, each with a screen nam
- `finish\_project`: Checks 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.
- `update\_project`: Changes a screenshot set create\_project made, before the user saves it: rewrite any screen's screen name or headline, or change the background colour, the frame colour or the device. The uploaded screenshots stay as they are. Returns new previews and warnings; the open\_url finish\_project gave then o
- `make\_screenshot\_set`: Use this when the user has attached screenshots of their own app in this conversation and wants App Store or Google Play screenshots made from them: store listing images, framed screenshots or app mockups for the App Store or Play Store. Each screenshot is put in a real device frame on a background
- `search\_library`: Use this when a design or a saved asset needs a ready-made piece rather than art you draw: SF Symbols, emoji, 3D shapes, glows and blobs, seasonal art, store badges, ratings, payment and social marks and more \(a few thousand pieces\). Returns the best matches with their path, which a library layer ta
- `get\_design\_guide`: Use this when the user wants App Store listing art \(an animated product page header, a search result, In-App Event art\) or a marketing image \(a launch post for X, LinkedIn or Instagram, a link preview, a Play feature graphic\) designed for their app and you will draw it yourself. Returns the appdesig
- `create\_design`: Use this when you have designed art for an app yourself and the user should get it as an editable project: App Store listing art that loops as a video \(a product page header, search result, or In-App Event card or page\), or a still marketing image \(an X, LinkedIn or Instagram post, a link preview, a
- `update\_design`: Changes a design create\_design made, before the user saves it: set fields of a layer by id, add, remove or reorder layers, or replace a variant's background, loop or title, or add or remove a variant. Send only what changes. Returns new preview images and warnings, like create\_design; the open\_url c
- `list\_projects`: Use this when the user wants to work on something they already made in appdesigns: change a screenshot set, a header or event art they saved, add to a project, or see what a project still lacks. Lists their projects \(one per app\) with every saved asset in each \(asset\_id, kind, canvas size, last edit
- `get\_asset`: Use this before changing an asset with edit\_asset, or when the user asks what one looks like: one the user saved \(asset\_id\) or a set or design you made in this conversation \(handle\). Returns its screens, each with its background, its layers bottom first \(text, pictures and the phone, each with an id
- `edit\_asset`: Use this to change something, after get\_asset: one the user saved \(asset\_id\) or a set or design you made in this conversation \(handle\). Rewrite or restyle text, move, resize or recolour layers, add art you draw as SVG, a library piece \(search\_library\), a phone frame or new text, remove or reorder la
- `save\_to\_account`: Use this when the user is signed in and a set you made is ready: after finish\_project \(and any update\_project\), or create\_design \(and any update\_design\), once the previews look right. Saves it straight into their appdesigns library, into the project you named with project\_id or same\_project\_as \(else
- `replace\_screenshots`: Use this when a set needs new screenshots in its phones: a recapture, a fixed screen, or a phone frame layer to fill \(get\_asset shows those as "phone frame: ..."\), in a set the user saved \(asset\_id\) or a set or design you made in this conversation \(handle\). Two calls. First with asset\_id or handle a
- `translate\_asset`: Use this when the user wants a screenshot set or listing asset in another language \(a localization for the App Store or Google Play\): one they saved \(asset\_id\), or one you made in this conversation \(handle\). You translate every text layer yourself \(get\_asset lists them, with their ids\); this makes a
- `export\_asset`: Use this when the user wants the finished files \(to upload to App Store Connect or the Play Console, or to use elsewhere\) of something they saved \(asset\_id\) or something you made in this conversation \(handle\). The files are made by the appdesigns editor in the user's browser, the same pixels its Exp
- `get\_export`: Use this after export\_asset, once the user has the editor open: says whether the files are made, and when they are, returns them with a command that downloads them into a folder \(bash and PowerShell\) and where they go next in App Store Connect or the Play Console. The command's links work until the
- `feature\_app`: Use this when the user wants their app in the appdesigns gallery \(appdesigns.click/apps\): a screenshot set they saved \(asset\_id, from save\_to\_account or list\_projects\) is sent for review as a template other makers start from, listed with the app's icon, name and store link, so other makers get inspi

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html