App Store screenshots, generated by your AI agent
Screenies has a remote MCP server. Connect it to Claude Code, Claude.ai, Cursor, or any agent that speaks MCP, and the whole workflow runs from a prompt: upload your app screenshots, generate a polished set, localize it, and download files sized for App Store Connect.
Connect in one command
In Claude Code:
claude mcp add --transport http screenies https://screenies.app/mcpThen run /mcp in a session, pick screenies, and sign in.
In Claude.ai, Cursor, and other MCP clients, add this URL as a remote MCP server (claude.ai: Settings, then Connectors, then Add custom connector):
https://screenies.app/mcpOr install with one click:
Once connected, try:
Create App Store screenshots for my app with Screenies.How it works
Add the server
Paste one command into Claude Code, or add the server URL in any MCP client that supports remote servers.
Sign in once
Your agent opens a browser window. Sign in to Screenies and approve the connection. OAuth handles the rest; no API keys to manage.
Ask for screenshots
Tell your agent to create App Store screenshots. It captures what it needs, uploads, generates, and hands you download links.
Every tool in the workflow
The MCP server has full parity with the dashboard. Anything you can do at screenies.app, your agent can do through a tool call.
Set up
whoamiConfirm which account the agent is signed in to.list_appsList your workspaces, apps, and credit balances.create_appCreate a new app with its description and details.request_screenshot_uploadGet signed URLs to upload source screenshots.
Generate
generate_screenshot_setStart a full App Store screenshot set generation.get_batch_statusPoll a batch; finished slides include download URLs.regenerate_failedRetry any slides that failed.generate_logoGenerate app icon options from a creative brief.set_brand_colorsSet the brand colors used across the set.
Refine and ship
edit_headlineRewrite the headline on a single slide.reorder_setReorder slides; localized copies follow automatically.localize_setTranslate a finished set into other App Store locales.get_credit_balanceCheck remaining credits before a run.
Sign in once, revoke anytime
The server uses OAuth 2.1 with dynamic client registration. Your agent never handles your password: it opens a browser window where you sign in to Screenies and approve the connection. Every tool call is scoped to your own workspaces and apps, and credit spending goes through the same ledger as the web app.
Frequently asked questions
What is the Screenies MCP server?
It is a remote MCP (Model Context Protocol) server at https://screenies.app/mcp that exposes the full Screenies workflow as tools. Any AI agent that supports remote MCP servers, such as Claude Code, Claude.ai, or Cursor, can create an app, upload source screenshots, generate an App Store screenshot set, localize it, and download the results.
How do I connect Screenies to Claude Code?
Run: claude mcp add --transport http screenies https://screenies.app/mcp. Then run /mcp inside a session, pick screenies, and sign in with your Screenies account. Other clients accept the same URL as a remote MCP server.
Does the MCP server cost extra?
No. The MCP server is included with every Screenies account. Generation started through MCP spends the same credits as generation started in the dashboard.
Which tools does the Screenies MCP server expose?
The full workflow: list and create apps, request signed screenshot uploads, generate a screenshot set, poll batch status, regenerate failed slides, localize a completed set, edit headlines, reorder slides, generate logos, set brand colors, and check your credit balance.
Is it safe to give an agent access to my Screenies account?
The server uses OAuth 2.1. Your agent never sees your password: it opens a browser window where you sign in to Screenies and approve the connection, and you can revoke access at any time. Tools are limited to your own workspaces and apps.
Ship your screenshots without leaving the terminal
Create a Screenies account, connect the MCP server, and let your agent handle the rest. Not sure where to start? See the current screenshot sizes and Apple's requirements.
Generate your set