AppScreens has one service with two interfaces. Your AI agent uses MCP to work on screenshot projects in a conversation. Your scripts and CI use the REST API for the same operations. Both work on the same saved projects, with the same checks, limits and version history as the editor.
Start in three steps
Add https://api.appscreens.com/mcp to your AI agent and sign in with your AppScreens account. Ask it to check your capabilities, then try a change on a test project and review the preview.
MCP or REST?
Use MCP when an AI agent should do the work: inspect your app, propose captions, update a project and show you a preview. Claude Code, Claude Desktop, Codex, Cursor and other MCP clients connect to https://api.appscreens.com/mcp and sign in through your browser. No API key is needed.
Use REST when your own code should do the work, such as a release script or a CI job. Send requests to https://api.appscreens.com/v1 with an API key from Account > API Access.
Both act for the same AppScreens account, share its allowances and can only use the features enabled for it.
What you can do
Your agent reads your code and local files with its own tools. AppScreens never browses your computer; it only receives the files your agent uploads. Your agent can write captions, run the project’s built-in translation or apply reviewed translations.
- Create a project from a template, or work on one you already designed.
- Upload your app screenshots and match them to pages, devices and languages with the same rules as the editor.
- Update captions and translations, then render a preview to review.
- Export full-resolution screenshots and download the ZIP files.
- Where enabled, update store listing text and deliver approved screenshots to App Store Connect or Google Play.
You stay in control
You can keep the project open in AppScreens while your agent works. Each change it saves appears in the editor. If you have unsaved changes, AppScreens keeps them and warns you before you save over the agent’s work.
Every change creates a new revision that you can restore from version history. A write based on an older revision is rejected, so an agent cannot overwrite newer edits by mistake.
A finished render is not an approval. Review the preview before you export, and approve any store delivery separately.
