Connect to AppScreens

Add AppScreens to Claude, Codex, ChatGPT or Cursor, or create an API key for REST.

AppScreens MCP server URL
https://api.appscreens.com/mcp

Most AI agents connect with one URL and a browser sign-in. Choose your client, add the server, approve access, then send a first prompt that only reads your account to check that everything works.

Set up your client

Choose the app you use and follow its steps below. Keep this page open so you can copy the URL or command, then test the connection in a new chat.

Choose your client

Terminal

claude mcp add --transport http --scope user appscreens 'https://api.appscreens.com/mcp'

Connect Claude Code

  1. 1Run the command in your terminal to add AppScreens for all your projects.
  2. 2Open Claude Code, type /mcp, select appscreens and choose Authenticate.
  3. 3Sign in to AppScreens in your browser and approve access. Return to Claude Code.
Official Claude Code guide

Check the connection

Run /mcp and check that appscreens is connected, then send the first prompt.

Check my AppScreens connection: show my account capabilities and usage, then list my projects. Don’t change anything yet.

Make your first set

Once the connection check works, ask for what you want in your own words. Your agent reads your app or listing, then asks about any stores, devices or languages it can’t work out.

To start from a design, use the prompt builder below. Pick a published listing to follow or take the style from, or pick a template. Add your devices and languages so your agent has fewer questions.

You can also choose Create with Agent on any template or Inspiration listing. In Claude Code, type / and pick an AppScreens prompt, such as plan_store_screenshots.

Try asking

Help me make App Store and Google Play screenshots for my app with AppScreens. Ask me what you need.

Browse Templates Browse Inspiration

Check your skills

The steps above end with a connection check. Skills are a separate check: use the AppScreens plugin where your client supports it to get the connection and skills together, or install the skill pack yourself. Paste this in a new chat.

Try asking

Check whether the AppScreens screenshot-reference-match skill is installed in this client. Open it and explain how it checks an early render and when it asks for review. If you can only read appscreens://workflow/reference-match, say that the MCP guide is available and the installed skill is unverified. Keep this check read-only.

All AppScreens skills Skill ZIP for Claude

Which client should I use?

Use a coding client, such as Claude Code, Codex or Cursor, when your app captures are in a local repository. Use a chat client, such as Claude Desktop or ChatGPT, when you would rather attach the captures yourself.

To match a reference design, choose a model that can see images. For new illustrations or backgrounds, a client with image generation can make the missing artwork.

Sign-in, API keys and access

MCP clients sign in with OAuth: the client opens AppScreens in your browser so you can review and approve access. See and revoke every connection in Account > MCP Access.

Use an API key only for REST, CI, scripts or a client that cannot sign in. Create one in Account > API Access, give it a clear name and an expiry, and keep it in an environment variable such as APPSCREENS_API_KEY. The key is shown once.

Signing up, signing in and checkout always happen in your browser. Never give an agent your password, payment details or an API key in chat.

  • All access does everything an agent can: projects, previews and exports, plus store screenshot uploads and listing text.
  • Projects only creates and edits apps and projects, uploads screenshots, and renders previews and exports, without reaching your store listings.
  • Read only inspects projects, templates and exports without changing anything.
  • Limit a connection to one project when the task only needs that project.

Use the REST API

For CI, scripts and your own apps, create a “Projects only” key in Account > API Access and store it as an environment variable or CI secret named APPSCREENS_API_KEY. This request only reads your account, so it’s a safe first check.

  • Send the key as Authorization: Bearer, never in a URL or a project file.
  • A “Read only” key can’t change anything. Use a “Projects only” key for the screenshot workflow.
  • The workflow guides end with a complete CI script that exports and downloads a project.

Check your key

curl --fail-with-body -sS https://api.appscreens.com/v1/capabilities \
  -H "Authorization: Bearer $APPSCREENS_API_KEY"

Automate releases

Create the screenshot project your agent will work with

Design your screenshots once in AppScreens. Then let your agent or your scripts update captions, translations and exports for every release.

Connect your agent