App Store and Google Play screenshots MCP: your agent captures the app, you edit and export. Free.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON â–¾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for appdesigns App Store screenshots, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
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
| Agent | How |
|---|---|
| Claude Code | claude mcp add --transport http --scope user appdesigns https://appdesigns.click/api/mcp, or this repo as a plugin: /plugin marketplace add haider-nawaz/app-store-screenshots-mcp then /plugin install appdesigns@appdesigns |
| Codex | codex mcp add appdesigns --url https://appdesigns.click/api/mcp |
| Cursor | One-click button on https://appdesigns.click/mcp, or add {"url": "https://appdesigns.click/api/mcp"} under mcpServers in .cursor/mcp.json |
| VS Code (Copilot) | code --add-mcp '{"name":"appdesigns","type":"http","url":"https://appdesigns.click/api/mcp"}' |
| Gemini CLI | gemini mcp add -s user -t http appdesigns https://appdesigns.click/api/mcp |
| Anything else | npx add-mcp https://appdesigns.click/api/mcp |
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
- The agent calls
get_workflowwith your platform and store. It returns the capture commands for your stack and the rules for screens, demo data and captions. - 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 to capture them, and a caption per screen. It waits for your reply before touching anything, and never touches production data.
- 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 storage through a signed URL, never through the model), thenfinish_project. - It opens the link in your browser. The set loads in the editor; export needs no account, and signing in (free) saves it to your library.
Tools
| Tool | What it does |
|---|---|
get_workflow | The full recipe for one platform and store: capture commands, screen, demo data and caption rules |
list_devices | The device frames a set can use |
create_project | Registers the screens (name, headline, file) and returns one upload command |
finish_project | Checks every uploaded file and returns the link to the set |
The server also exposes an app_store_screenshots prompt (in Claude Code:
/mcp__appdesigns__app_store_screenshots).
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
.claude-plugin/marketplace.jsonandplugins/appdesigns/: a Claude Code plugin marketplace with one plugin that connects the server and adds theapp-store-screenshotsskill.plugins/appdesigns/skills/app-store-screenshots/SKILL.md: the skill on its own, usable by any agent that reads Agent Skills (copy it to.claude/skills/,.agents/skills/or similar).server.json: the entry in the official MCP Registry asclick.appdesigns/screenshots.
The server itself is hosted at appdesigns.click; this repository holds the client-side pieces.
License
MIT
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Appdesigns App Store screenshots
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/appdesigns-app-store-screenshots)HTML Embed
<a href="https://allmcps.com/mcp/appdesigns-app-store-screenshots"><img src="https://allmcps.com/api/badge/appdesigns-app-store-screenshots?style=directory" alt="Appdesigns App Store screenshots on AllMCPs" /></a>