Edit designs
Rewrite captions, move and hide layers, swap device frames and page backgrounds, and point a slot at a different capture. An open editor sees the change instead of overwriting it.
Store screenshots, from a chat with Claude.
Ask what changed since the last capture run, fix a caption, then ship the set to both stores.
Setup
One URL. No API keys to paste.
Add the server
One command in Claude Code, or paste the URL under Settings, Connectors in the Claude app.
Approve the connection
Claude opens ScreenStack. Pick the workspace and the access it gets, then approve.
Ask
Claude reads your projects, designs and capture runs, and edits or ships only what you ask for.
Server URL https://api.screenstack.voostack.com/mcp
claude mcp add --transport http --scope user screenstack https://api.screenstack.voostack.com/mcp/mcp{ "mcpServers": { "screenstack": { "type": "http", "url": "https://api.screenstack.voostack.com/mcp" } }}In Claude on the web or desktop: Settings, then Connectors, then Add custom connector. Paste the URL and connect.
Everything in your workspace, in plain words.
Ask about any run
Which screens changed, which slots are still empty, what the last export of each page looks like.
Write screenstack.yml
Claude drafts the file and checks it against the same rules as the CLI before you commit it.
Ship to both stores
Replace App Store Connect and Google Play screenshots, one design per locale.
Try asking
- Which designs in my ScreenStack project still have empty slots?
- Compare the last two capture runs and list screens that changed.
- Write a screenstack.yml for my Flutter app on iPhone 16 Pro Max and Pixel 9, in en-US and de-DE.
- Upload the English and German store designs to the App Store, but show me the plan first.
Claude only does what you allowed.
- You approve each connection
- Sign-in runs on ScreenStack. Claude never sees your password, and each connection reaches one workspace.
- Access you pick
- Viewing is always on. Editing designs and uploading to the stores are separate boxes you can leave unticked.
- Store keys stay with us
- App Store Connect and Google Play keys are added in project settings and stored encrypted. Claude only sees which app they reach.
- Uploads show the plan first
- Before replacing a listing, Claude shows which locales and how many screenshots change, and waits for your yes.
- Disconnect any time
- Account settings list every connected app. Disconnecting stops it on its next request.
Claude questions
What is the ScreenStack MCP server?
It connects Claude to your ScreenStack workspace over the Model Context Protocol. Claude can list projects, read designs and capture runs, edit captions, layers, device frames and capture bindings, check screenstack.yml files, and upload a design's exports to App Store Connect or Google Play.
Which Claude apps work with it?
Claude on the web, Claude Desktop and Claude Code. Any other client that supports remote MCP servers over Streamable HTTP with OAuth works too.
Can Claude upload to the App Store without asking?
No. Store uploads need their own permission when you connect, a workspace owner or admin, and a store key added in project settings. Claude first shows the plan, the locales and screenshot count that will change, and only uploads after you confirm.
Can Claude create new exports?
Not yet. Exports are rendered in the ScreenStack editor. Claude can edit a design, and once you export it from the editor, upload those exports to the stores.
How do I remove access?
Open Account, then Connected apps, and disconnect it. Its tokens stop working on the next request. You can also remove the connector in Claude.
Connect Claude in two minutes.
The MCP server is on every plan. Create a free account, then add the connector and sign in.