# appdesigns App Store screenshots (remote · appdesigns.click)

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

- Trust score: 77/100 (medium)
- Change this week: −4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

> **Recent critical change**: Authorization (2026-10-14). See the changelog below before you install this server.

## Components

- remote · `appdesigns.click`: 77/100 (this document), [markdown](https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp.md), [page](https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp)

## Channel facts

- Endpoint: `https://appdesigns.click/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (finish_project).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5887 tokens (~327/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the appdesigns App Store screenshots MCP server?

appdesigns App Store screenshots is a hosted endpoint at https://appdesigns.click/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http click-appdesigns-screenshots 'https://appdesigns.click/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "click-appdesigns-screenshots": {
      "url": "https://appdesigns.click/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "click-appdesigns-screenshots": {
      "type": "http",
      "url": "https://appdesigns.click/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.click-appdesigns-screenshots]
url = "https://appdesigns.click/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "click-appdesigns-screenshots": {
      "type": "remote",
      "url": "https://appdesigns.click/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add click-appdesigns-screenshots --url 'https://appdesigns.click/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  click-appdesigns-screenshots:
    url: "https://appdesigns.click/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "click-appdesigns-screenshots": {
      "Transport": "http",
      "Url": "https://appdesigns.click/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add click-appdesigns-screenshots -t streamable-http -u 'https://appdesigns.click/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "click-appdesigns-screenshots": {
      "type": "http",
      "url": "https://appdesigns.click/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “edit_asset”, which the server declares destructive
- [security] New tool “replace_screenshots”, which the server declares destructive
- [security] Tool “create_project” rewrote its description, which is the text the model reads
- [security] Tool “make_screenshot_set” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1680 → 5887
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “create_design”
- [functional] New tool “export_asset”
- [functional] New tool “get_asset”
- [functional] New tool “get_design_guide”
- [functional] New tool “get_export”
- [functional] New tool “list_projects”
- [functional] New tool “save_to_account”
- [functional] New tool “search_library”
- [functional] New tool “translate_asset”
- [functional] New tool “update_design”
- [functional] New tool “update_project”
- [cosmetic] “create_project” added an optional parameter “fold”
- [cosmetic] “create_project” added an optional parameter “orientation”
- [cosmetic] “create_project” added an optional parameter “project_id”
- [cosmetic] “create_project” added an optional parameter “same_project_as”
- [cosmetic] “make_screenshot_set” added an optional parameter “orientation”
- [cosmetic] “create_project” reworded the description of “canvas_size”
- [cosmetic] “make_screenshot_set” reworded the description of “canvas_size”

### 2026-10-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 75, −7)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_project” rewrote its description, which is the text the model reads
- [security] Tool “get_workflow” rewrote its description, which is the text the model reads
- [security] Tool “list_devices” rewrote its description, which is the text the model reads
- [security] Tool “finish_project” is now declared destructive
- [functional regression] Schema quality: 239 → 336
- [functional] New tool “make_screenshot_set”

### 2026-10-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 53. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 81, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “create_project” reworded the description of “canvas_size”

### 2026-10-04 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (18)

### `get_workflow` (~183 tokens)

Get the screenshot 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 user's consent, the exact capture commands (simulator or emulator, status bar, deep links), the caption rules, and the upload and hand-off steps. Not for a chat without a terminal, where the screenshots come as attachments instead. Read-only; changes nothing.

Input parameters:

- `platform` (string, required): How the app is built: ios (Swift or Objective-C), android (Kotlin or Java), expo, react-native, flutter, or web (a web app or PWA).
- `store` (string): Which store the screenshots are for.

### `list_devices` (~85 tokens)

List device frames

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. Read-only.

Input parameters:

- `store` (string): Which store the screenshots are for.

### `create_project` (~647 tokens)

Create a screenshot 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 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 1 hour (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.

Input parameters:

- `background_color` (string): #RRGGBB. Use the app's brand or accent colour if you can find it in the code. Leave it out for a neutral light background.
- `canvas_size` (string): A canvas size from list_devices, as WIDTHxHEIGHT, portrait or landscape (2868x1320 for a landscape iPhone set). Leave it out and finish_project takes the store size the screenshots are (a landscape c…
- `device` (string): A device id from list_devices. Defaults to iphone-17-pro-max for the App Store and pixel-11-pro for Google Play.
- `fold` (string): iPhone Duo only: inner-open (Unfolded, the open inner display), outer-closed (Cover, the folded cover display) or outer-open (Open back, the open phone from behind, showing its cover display). The ed…
- `frame_color` (string): A colour id of that device from list_devices. Leave it out to pick one that stands out from the background.
- `orientation` (string): Which way up the set is, when canvas_size does not say: landscape for an app that runs in landscape (most games), and the phone is drawn on its side. Leave it out to follow the screenshots.
- `project_id` (string): A project_id from list_projects (the user signed in): the new asset is saved into that saved project of theirs. Use it, not same_project_as, to add to something the user already saved.
- `project_name` (string, required): The app's name. It becomes the project name in the user's appdesigns library.
- `same_project_as` (string): The project_handle or design_handle of an earlier asset from this conversation (screenshots, a header...). The user's save then files this one in the same project, once they have saved that one.
- `screens` (array, required): One entry per screenshot, in the order the store should show them. The first sells the app.
- `store` (string): Which store the set is for.

### `finish_project` (~83 tokens)

Finish a screenshot 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.

Input parameters:

- `project_handle` (string, required): The project_handle create_project returned.

### `update_project` (~209 tokens)

Change a screenshot 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 opens the new version. For anything more (the phone's place, size or fold, text styles, pieces, another canvas), use edit_asset with this project_handle as handle, no sign-in needed; once it has changed the set, keep using edit_asset. A set the user already saved changes with edit_asset by asset_id.

Input parameters:

- `background_color` (string): #RRGGBB.
- `device` (string): A device id from list_devices that suits the set's canvas.
- `frame_color` (string): A colour id of the device from list_devices.
- `project_handle` (string, required): The project_handle create_project returned.
- `screens` (array): Only the screens and captions that change.

### `make_screenshot_set` (~546 tokens)

Make a screenshot set from attached screenshots

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 with the screen name and headline you write, at the store's exact size, and open_url opens the set as an editable project in the appdesigns editor. Takes 1 to 6 PNG or JPEG screenshots (at most 6 MB each, all the same way up; landscape ones make a landscape App Store set) in store order, with one screens entry per screenshot in the same order. Each must be a raw capture of the app as the device shows it. Do not use it for images that already have a device frame, a background or marketing text (the user needs to attach the raw screenshots instead), to invent app screens that do not exist, or when nothing is attached (the user needs to attach screenshots first). The screenshots are stored privately so open_url can load them; it works for 72 hours or until the user saves the set to their account. Nothing is public and no account is needed to make the set.

Input parameters:

- `background_color` (string): #RRGGBB, for example the app's brand colour as seen in the screenshots. Leave it out for a neutral light background.
- `canvas_size` (string): A canvas size from list_devices, as WIDTHxHEIGHT. Leave it out for the store default, or the store size the screenshots are; landscape screenshots make a landscape App Store set.
- `device` (string): A device id from list_devices. Defaults to iphone-17-pro-max for the App Store and pixel-11-pro for Google Play.
- `frame_color` (string): A colour id of that device from list_devices. Leave it out to pick one that stands out from the background.
- `orientation` (string): Which way up the set is, when canvas_size does not say: landscape for an app that runs in landscape (most games), and the phone is drawn on its side. Leave it out to follow the screenshots.
- `project_name` (string, required): The app's name. It becomes the project name in the user's appdesigns library.
- `screens` (array, required): One entry per attached screenshot, in the same order as screenshots. The first sells the app.
- `screenshots` (array, required): The screenshots the user attached, in store order, one per screens entry.
- `store` (string): Which store the set is for: app_store for iPhone or iPad screenshots, play for Android.

### `search_library` (~187 tokens)

Search the appdesigns 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 takes (create_design and edit_asset), and one image showing them in order, left to right then down. With no match it lists the categories. Read-only.

Input parameters:

- `category` (string): Keep one category, such as sf-symbols, emoji, 3d, decorative, seasonal, badges or shapes.
- `limit` (integer): How many to return, best first.
- `query` (string, required): Words for what the piece shows, such as "heart", "sparkle", "3d cube", "apple pay", "christmas".

### `get_design_guide` (~182 tokens)

Get the 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 appdesigns recipe for that asset as markdown: its size and what crops or covers it, the layer format create_design takes (phone frames included), the moves, the quality bar and the hand-off to the user. Read-only; changes nothing.

Input parameters:

- `asset` (string): The asset, as create_design names it: header, search_result, event_card, event_page, x_post, linkedin_post, link_preview, instagram_square, instagram_portrait, instagram_tall, product_hunt, wide_imag…

### `create_design` (~656 tokens)

Create a listing art 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 Product Hunt image, a 16:9 image, Google Play's feature graphic). Takes 1 to 4 variants (directions for the user to choose from), each a background and layers: art you draw as SVG, library pieces, the app's icon, text, and phone frames showing the app (an iPhone, the iPhone Duo open from behind and from the front...), with moves and a loop on listing art. Checks everything and returns a preview image of each variant, warnings, a design_handle for update_design, and open_url, which opens the design in the appdesigns editor, where the user keeps a direction, tweaks any layer, saves it and exports it. Nothing is public and no account is needed. The design waits 72 hours to be opened and saved.

Input parameters:

- `animated` (boolean): false for a still image (the user asked for one): the moves are kept with motion turned off, so the Motion toggle brings them back.
- `app_store_url` (string): The app's App Store link, if it is on the App Store: the editor's preview phone then shows its real name and icon, app_icon layers use its icon, and a phone layer can show one of its App Store screen…
- `asset` (string): Listing art: header (3840x1646), search_result (3840x2560), event_card (3840x2160) or event_page (2160x3840). Stills: x_post (1600x900), linkedin_post (1200x627), link_preview (1200x630), instagram_s…
- `project_id` (string): A project_id from list_projects (the user signed in): the new asset is saved into that saved project of theirs. Use it, not same_project_as, to add to something the user already saved.
- `project_name` (string, required): The app's name. It becomes the project name in the user's appdesigns library.
- `same_project_as` (string): The project_handle or design_handle of an earlier asset from this conversation (screenshots, a header...). The user's save then files this one in the same project, once they have saved that one.
- `screenshots_from` (string): The project_handle of a screenshot set you made with create_project in this conversation (finished, not yet saved): a phone layer's screenshot n then shows that set's n-th capture, instead of an App…
- `variants` (array, required): The directions, each a whole design. The first is the one you would pick.

### `update_design` (~149 tokens)

Change a listing art 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 create_design gave then opens the new version. A design changed with edit_asset keeps changing there, and one the user already saved changes in the editor (or with edit_asset by asset_id once they sign you in).

Input parameters:

- `changes` (array, required): Applied in order. Positions count from 0 at the bottom.
- `design_handle` (string, required): The design_handle create_design returned.

### `list_projects` (~189 tokens)

List the user's appdesigns 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) and what each project still needs. Needs the user signed in to appdesigns; a call without it fails asking for sign-in, and then the user signs in (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves). Read-only.

Input parameters:

- `query` (string): Only projects or assets whose name contains this, ignoring case.

### `get_asset` (~301 tokens)

Read one 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, a position as a share of the canvas and its style) and its loop if it is animated, plus warnings about what may look off, and a preview image of each screen. Also returns the revision edit_asset needs. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in. Read-only.

Input parameters:

- `asset_id` (string): The asset_id list_projects returned.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…
- `previews` (array): Which screens to preview, from 1. Default: all of them.

### `edit_asset` (~417 tokens)

Change an 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 layers, move or resize the phone or change its model, colour and fold, change the background or the loop, turn the whole set landscape or portrait or give it another size of the same asset (set_canvas), rename, duplicate, reorder or remove screens. Send only what changes, with the revision get_asset returned; the asset changes at once (like an edit in the editor) and the reply has the new revision, previews of the changed screens and warnings. A set or design changed this way keeps changing here: update_project and update_design no longer apply to it. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in.

Input parameters:

- `asset_id` (string): The asset_id list_projects returned.
- `changes` (array, required): Applied in order, all or none. Layer positions count from 0 at the bottom of the screen's layers list, the phone included.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…
- `revision` (string, required): The revision get_asset (or the last edit_asset) returned. If the asset changed since, nothing changes and you read it again.

### `save_to_account` (~231 tokens)

Save a new set to the user's 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 a new project named after it), with no link to open and nothing for them to press. Returns the saved asset_id and revision for edit_asset, and open_url, which opens the saved set in the editor. The draft's own link then opens the saved set. Needs the user signed in to appdesigns; a call without it fails asking for sign-in, and then the user signs in (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves).

Input parameters:

- `handle` (string, required): The project_handle create_project returned, or the design_handle create_design returned.

### `replace_screenshots` (~401 tokens)

Put new screenshots in a set

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 and screens (each a screen number, the local file and, for a phone frame layer, its id): it returns one upload command (bash and PowerShell) that sends the files straight to storage. Run it, then call again with the same asset_id or handle, replace_handle and the revision get_asset returned: the files are checked (PNG or JPEG, the shape of the phone's screen) and swapped in, and the reply has the new revision and previews. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in.

Input parameters:

- `asset_id` (string): The asset_id list_projects returned.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…
- `replace_handle` (string): Second call: the replace_handle the first call returned, once the upload command has run.
- `revision` (string): Second call: the revision get_asset (or the last edit) returned.
- `screens` (array): First call: what goes where, at most 6 files a call.

### `translate_asset` (~399 tokens)

Make a set in another language

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 copy in that language, its images copied and the original untouched, wrapping a long translation and moving the captions under it down as the editor's own Translate set does. A saved set's copy is saved into the same project (asset_id back); a copy of yours is a new set with its own handle and link, which joins the original's project when the user saves them. Returns a preview of every screen (check the line breaks) and warnings; fix any line with edit_asset. One call per language. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in.

Input parameters:

- `asset_id` (string): The asset_id list_projects returned.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…
- `language` (string, required): App Store Connect's code for the language, such as de-DE, fr-FR, ja, es-MX or pt-BR.
- `texts` (array, required): Every text layer that has words, translated. Keep names and brands as written; match the source's tone and length where the language allows.

### `export_asset` (~308 tokens)

Export an asset's files

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 Export saves: open_url opens it there and makes them (a PNG per screen, and an MP4 for a screen whose loop is on), then get_export with export_id gives a command that downloads them. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in.

Input parameters:

- `asset_id` (string): The asset_id list_projects returned.
- `format` (string): auto: an MP4 for each screen whose loop is on (an animated listing asset), a PNG for every other screen. png: stills only.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…

### `get_export` (~250 tokens)

Get an export's files

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 export expires (24 hours after export_asset); each call with the files ready makes new links and retires the earlier ones, so run the command from the latest call. Pass the handle too when you exported something you made in this conversation; then it needs no sign-in, else it needs the user signed in (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run `claude mcp login appdesigns` in a separate terminal), in Codex run `codex mcp login appdesigns`; other agents open the sign-in page themselves).

Input parameters:

- `export_id` (string, required): The export_id export_asset returned.
- `handle` (string): Instead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp#diagnostics

## Score history

- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 82
- 2026-10-12: 82
- 2026-10-10: 81
- 2026-10-04: 79
- 2026-10-03: 78
- 2026-10-02: 78
- 2026-10-01: 77
- 2026-09-30: 77
- 2026-09-29: 76
- 2026-09-28: 76
- 2026-09-27: 75
- 2026-09-26: 75

## Common questions

### What is the appdesigns App Store screenshots MCP server?

appdesigns App Store screenshots is an MCP server listed in the public MCP registry as click.appdesigns/screenshots. App Store and Google Play screenshots MCP: your agent captures the app, you edit and export. Free. This page covers its hosted endpoint (https://appdesigns.click/api/mcp).

### Is the appdesigns App Store screenshots MCP server safe to use?

appdesigns App Store screenshots scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the appdesigns App Store screenshots MCP server expose?

appdesigns App Store screenshots exposes 18 tools: get_workflow, list_devices, create_project, finish_project, update_project, and 13 more. Their descriptions and schemas cost roughly 5,423 tokens of context every time the server is loaded.

### Does the appdesigns App Store screenshots MCP server require authentication?

No. We connected to appdesigns App Store screenshots without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the appdesigns App Store screenshots MCP server still maintained?

appdesigns App Store screenshots is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://appdesigns.click/api/mcp
- Repository: https://github.com/haider-nawaz/app-store-screenshots-mcp
- Website: https://appdesigns.click/mcp
- Changelog RSS feed: https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/click-appdesigns-screenshots/api-mcp