ExploreGeneratorTemplatesMCPPricing
Log inGet Started
Model Context Protocol

Give your AI agents a real app store screenshot library

Add AppScreens to claude.ai, Claude Desktop, or Claude Design as a custom connector — paste one URL, approve it, done. Claude Code, Cursor, and Codex connect with a personal token. Either way your assistant researches the App Store against a curated archive classified by layout pattern and ASO strategy, with full version history, instead of guessing.

Set up the MCPSee pricing

Connect by URL or personal token · 7 read-only tools · Pro feature

Stop making your agents guess at the App Store

Without the MCP

Agents doing ASO or competitive research scrape store pages, hallucinate screenshot layouts, and have no way to see how a listing looked last quarter. Every answer is a guess you have to verify by hand.

With the MCP

Agents call structured tools against a curated archive: search by category and strategy, pull historical snapshots, and fetch a specific screenshot as an image when they need to read it. Grounded answers from the real listings, no scraping.

The tools

Seven read-only tools your agent can call — six read the archive, and the last one hands a proposed screenshot set to the generator. Full reference in the MCP guide.

search_apps

Search and filter the archive by name, platform, category, layout pattern, and ASO strategy. Returns paginated app summaries.

get_app

Full details for one app, including its current screenshots and video previews with direct, fetchable image URLs.

list_tags

List the layout and ASO-strategy tags you can filter by. Tags apply to a listing, not to a single screenshot, and each app says whether its tags were read from its own screenshots or inherited from its category.

list_categories

List every app category in the archive, usable as a search filter.

get_app_history

Historical screenshot snapshots for an app (Time Machine), newest first — see how a listing evolved over time.

get_screenshot

Fetch one screenshot as an image rather than a URL, so your assistant can read its caption or judge its layout. Ask for the 400px copy when composition is all you need.

draft_screenshots

Turn a proposed screenshot set into a link that opens the generator with the captions, layouts, and brand colours already filled in. Writes the words, not the pictures — you add your own screenshots.

Built-in workflows

The connector also ships three ready-made research workflows. Pick one from your client's prompt menu, fill in the app or concept, and it runs the whole sequence — which tools, in what order, and how many screenshots are worth pulling.

competitor_teardown

concept, platform (optional)

Research how the leading apps for a product concept sell themselves in the store, and what gap that leaves. Start here when planning a new app or repositioning one.

screenshot_audit

app, against (optional)

Audit one listing shot by shot — what the first screenshot promises, how the captions ladder from there, which slots are doing no work. Pass a rival to get it judged side by side.

listing_changes

app, limit (optional)

Diff an app's past snapshots to see how its listing evolved — what it led with then, what it leads with now, and what each change suggests the team learned.

Where they show up depends on the client: one that supports MCP prompts surfaces them in its own prompt or command menu. A client that doesn't still gets all seven tools — you just phrase the request yourself, and the MCP guide spells out what to ask for.

Ask your agent

Off the workflows, plain questions route straight to the archive too:

  • Find iOS finance apps that use social proof in their screenshots.
  • Show me how Duolingo's app store screenshots changed over time.
  • What layout patterns do the top social apps use for their first screenshot?
  • Compare the ASO strategies of the top 3 meditation apps.
  • List Android productivity apps that lead with a caption-heavy layout.
  • Pull the current screenshots for Notion and describe the visual hierarchy.

Research while you design

Claude Design takes the same connector URL. Halfway through building a pitch deck or a screenshot set, you can ask what the top apps in a category actually do — and get an answer out of the archive, without leaving the design to go and look it up.

  • Which ASO strategies do the top 5 meditation apps use? Summarize them as a slide.
  • What caption length do finance apps use on their first screenshot?

Most tools hand back metadata, tags, and screenshot URLs, so lead with questions the archive's classifications can answer; reach for get_screenshotwhen you want a particular screenshot pulled in as an image and looked at. And state your target resolution as an explicit constraint in the prompt (“1284×2778, portrait”): the dimensions in the payload won't set the canvas for you, and a first draft can come back in the wrong orientation.

Set up the MCP

Two ways in. Most people want the first one.

Before you start

  • An AppScreens Pro subscription — MCP access is a Pro feature on both paths.
  • Either a Claude surface that takes custom connectors — claude.ai, Claude Desktop, Claude Design — or a client that speaks Streamable HTTP, like Claude Code, Cursor, or Codex.
1

Add AppScreens to Claude

In claude.ai, Claude Desktop, or Claude Design, open your connector settings, choose to add a custom connector, and paste https://appscreens.store/api/mcp as the server URL. Claude Code takes the same path from the terminal — pick its tab below for the command. Either way Claude sends you to an AppScreens consent screen; approve it and the seven tools appear. There is no token to copy, and you can revoke the connection from Settings at any time.

  1. In claude.ai, open your connector settings and choose to add a custom connector.
  2. Paste this URL as the connector's server URL:
  3. Sign in to AppScreens if asked, then approve the consent screen. A Pro plan is required — Free accounts stop here.
Connector URL
https://appscreens.store/api/mcp

✓ Check it worked: Start a new chat, open the tools menu, and confirm AppScreens is listed with 7 tools.

Most tools return image URLs rather than images — Claude cites and links them. get_screenshot is the exception: it returns one screenshot as image data, and Claude reads it.

No token to copy — you approve the connection inside Claude, and you can revoke it in Settings whenever you like. AppScreens Pro is required to approve it.

2

Or use a personal token for other developer tools

Cursor, Codex, and other MCP clients authenticate with a personal token instead. Open Settings → MCP server and click Generate token. It starts with ascr_ and is shown once — copy it immediately. There is one token per account, so Rotate replaces it everywhere: anything still sending the old value starts failing until you paste the new one in.

  1. Add this to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
mcp.json

Replace <YOUR_TOKEN> with your personal token before running this. Generate one in Settings (Pro required) — it is shown once, when you create it.

{
  "mcpServers": {
    "appscreens": {
      "url": "https://appscreens.store/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

✓ Check it worked: Reload Cursor, then check Settings → MCP — appscreens should show as connected with 7 tools.

3

Ask your first question

Find iOS finance apps that use social proof in their screenshots.

If everything is wired up, your agent calls search_apps and answers with real apps and screenshot URLs from the archive — no scraping, no guessing.

Stuck?“The MCP connector is a Pro feature” on the approval screen is a 402 — the account you signed in with is still on Free; upgrade and add the connector again. On the token path, a 401 means the token is missing, mistyped, or revoked — rotate it in Settings, and a 403means that account isn't Pro yet. For everything else, see the troubleshooting guide.

FAQ

Frequently asked
questions.

What is the AppScreens MCP?+
It's a Model Context Protocol (MCP) server that lets Claude query the AppScreens archive directly — searching apps, reading screenshot URLs, and browsing version history — instead of guessing or scraping the App Store.
Which clients can connect?+
claude.ai, Claude Desktop, and Claude Design add AppScreens as a custom connector: paste https://appscreens.store/api/mcp into the connector dialog and approve it. Claude Code, Cursor, Codex, and any other client that speaks Streamable HTTP connect with a personal token generated in Settings.
Do I have to know how to prompt it?+
No. The connector ships three built-in workflows — competitor_teardown, screenshot_audit, and listing_changes — that your client lists in its prompt menu. Pick one, fill in the app or concept, and it runs the whole sequence: which tools in what order, how many screenshots are worth pulling, and the comparisons that would be misleading. Plain questions work too; the workflows just make the good version the default.
Do I need a Pro plan?+
Yes, for both paths. Approving the connector as a Free account stops at the consent screen with a 402, and a personal token can only be generated on Pro. Browsing the archive on the website stays free.
Can my agent see the screenshots?+
For one screenshot at a time, yes: get_screenshot returns the image itself rather than a link, so an assistant that renders images can read the caption on it. The other tools return absolute, publicly fetchable image URLs — cheap to pass around, but they are links, and Claude will cite rather than open them. Ask for a specific screenshot when you need it looked at.
Do the tags describe an individual app?+
Only when the payload says so. Layout and ASO-strategy tags apply to a listing, not a single screenshot, and every app carries a tagSource: 'per_app' tags were read from that app's own screenshots and can be reported as findings, while 'category' tags are a per-category default shared by every app in the category — useful as a filter, never a fact about one app.
Is it read-only?+
Yes. Every tool is read-only — agents can search and read the archive but cannot modify any data. draft_screenshots looks like an exception and is not: it builds a link from what you gave it and stores nothing.
Can Claude make the screenshots for me?+
It writes them, you render them. draft_screenshots turns a proposed set into a link that opens the generator with the captions, layouts, and brand colours in place — then you drop in your own app screenshots and export. The images stay yours on purpose: the archive holds other companies' screenshots, and those do not belong in your listing.
How do I disconnect?+
In Settings under the MCP server section. Connected apps lists everything you approved as a connector, each with a Disconnect button; Revoke removes your personal token; Revoke all stops both at once, immediately.
Where is my token?+
Generate, rotate, or revoke your personal MCP token in Settings under the MCP server section (Pro required). Your token is shown once when created — copy it then, and rotate if you lose it. Connector users never need one.

Point your agents at the archive

Paste one URL into Claude and approve it — or drop a token into your dev tooling — and two minutes from now your assistant researches the App Store with you.

Set up the MCPSee pricing