@appscreenshotstudio/mcp 0.8.3 → 0.8.5

package/README.md

@@ -151,7 +151,10 @@ Export to high-resolution PNGs. Returns download URLs.
 |---|---|---|---|
 | `project_id` | string | Yes | Project to render |
 
-**Free.**
+**No credit cost, and it needs an active paid plan.** Rendering is unlocked by
+the first payment, so on a trial this returns 402 `PAYMENT_REQUIRED`. That
+applies to the inline previews an agent shows mid-loop as well as to the final
+export.
 
 ### `get-project`
 
@@ -239,7 +242,7 @@ The AI generates professional screenshots using:
 2. **Generate**: Agent calls `generate-screenshots` with `codebase_context` for app-specific designs
 3. **Iterate**: Agent calls `edit-screenshots` to refine (codebase context carries over automatically)
 4. **Upload**: Agent calls `upload-screenshots` with local file paths to fill device mockups
-5. **Export**: Agent calls `render-screenshots` or click "Download All" in the web app
+5. **Export**: Agent calls `render-screenshots` (needs a paid plan) or click "Download All" in the web app
 
 ## Security
 

package/dist/index.js

@@ -348,8 +348,15 @@ Costs 5 credits per generation.`,
                     hasScreens
                         ? '1. Your attached screenshots were placed into the device frames (upload-screenshots can swap any card later)'
                         : '1. Use upload-screenshots to add your app screenshots into the device frames',
-                    '2. Use render-screenshots to export final PNGs',
-                    '3. Or open the project URL in a browser to preview and adjust',
+                    // edit-screenshots was missing from this list until 2026-09-14, and the
+                    // omission has a measurable cost: with no in-band pointer to the refine
+                    // path, the cheapest visible way to change a design is to call generate
+                    // again, which bills 5 credits and starts a NEW project every time. User
+                    // 5b0a496d called generate 4x and edit 0x on one brief, spending 20 of 25
+                    // trial credits on four near-identical projects.
+                    '2. Use edit-screenshots to refine THIS project (change copy, colours, layout). Prefer it over calling generate again: generate always starts a new project and re-bills.',
+                    '3. Use render-screenshots to export final PNGs (needs a paid plan; trials can build and iterate but not export)',
+                    '4. Or open the project URL in a browser to preview and adjust',
                     '',
                     imageErrors.length ? `Image read warnings:\n${imageErrors.join('\n')}` : '',
                     chatData.suggestions?.length
@@ -493,7 +500,7 @@ server.registerTool('render-screenshots', {
         idempotentHint: true,
         openWorldHint: false,
     },
-    description: 'Export a screenshot project to high-resolution PNG files at exact App Store dimensions. Returns download URLs for each card; URLs stay valid for 7 days, so save the PNGs to disk promptly (re-rendering is free if a URL has expired). Free (no credit cost). Pass device_ids to get the same canvas at several device sizes in one call, re-laid-out for each, instead of building a second project: an App Store submission wants the 6.9-inch iPhone and, when the app supports iPad, the 13-inch iPad, and Google Play is a separate listing. Rendering blocks until the PNGs are ready: expect roughly 20-40s per iPhone set and 60-120s per iPad set (the larger canvas renders slower), and those add up per device, so allow up to ~2 minutes each before treating it as failed. Note: device mockups will show empty frames unless app screenshots have been uploaded via upload-screenshots first.',
+    description: 'Export a screenshot project to high-resolution PNG files at exact App Store dimensions. Returns download URLs for each card; URLs stay valid for 7 days, so save the PNGs to disk promptly (re-rendering is free if a URL has expired). Costs no credits, but export is unlocked by the first payment: on a trial this returns 402 PAYMENT_REQUIRED, so check the plan before promising a user their PNGs. Pass device_ids to get the same canvas at several device sizes in one call, re-laid-out for each, instead of building a second project: an App Store submission wants the 6.9-inch iPhone and, when the app supports iPad, the 13-inch iPad, and Google Play is a separate listing. Rendering blocks until the PNGs are ready: expect roughly 20-40s per iPhone set and 60-120s per iPad set (the larger canvas renders slower), and those add up per device, so allow up to ~2 minutes each before treating it as failed. Note: device mockups will show empty frames unless app screenshots have been uploaded via upload-screenshots first.',
     inputSchema: z.object({
         project_id: z.string().describe('Project ID to render'),
         device_ids: z

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appscreenshotstudio/mcp",
-  "version": "0.8.3",
+  "version": "0.8.5",
   "mcpName": "com.appscreenshotstudio/mcp",
   "description": "MCP server for generating App Store screenshots via AppScreenshotStudio",
   "type": "module",

package/skills/appscreenshotstudio/SKILL.md

@@ -86,7 +86,9 @@ If screenshots were attached in Step 3 they are already in the frames. This step
 
 This is conversational refinement, so iterate right here in the chat. Don't send the user away to look at links.
 
-1. **Show.** Call `render-screenshots` (free) after generating. It returns inline image previews, so the screenshots display directly in the conversation. Show them.
+**Rendering is unlocked by the first payment.** It costs no credits, and it does need an active paid plan: on a trial account every `render-screenshots` call returns 402 `PAYMENT_REQUIRED`. That gates the previews in this loop, not just the export in Step 6, so the whole show → refine → re-show rhythm below is a paid-plan rhythm. When you get a 402: say plainly that rendering needs a paid plan, share the project URL so the user can see the set in the builder, and keep refining from their description in chat. Do not retry the call, and do not spend more credits generating alternates the user still cannot see.
+
+1. **Show.** Call `render-screenshots` after generating (no credit cost). It returns inline image previews, so the screenshots display directly in the conversation. Show them.
 2. **Refine.** Let the user react in plain language and apply changes with `edit-screenshots`:
    - "Want any headlines or colors changed?"
    - "Should I add a social proof card with ratings?"
@@ -97,7 +99,7 @@ Hand off to the builder only when it genuinely helps: share the project URL and
 
 ### Step 6: Export
 
-`render-screenshots` is also the export: it returns download URLs for the final PNGs at exact App Store dimensions, and it is free. Give the user those URLs and note they stay valid for 7 days, so download promptly (re-rendering later is free if a URL has expired). The builder project URL is the alternative when they want to compare the full set visually or hand-tweak before downloading.
+`render-screenshots` is also the export: it returns download URLs for the final PNGs at exact App Store dimensions, and it costs no credits. It needs the same active paid plan as Step 5, so on a trial this is where the user meets the paywall if they have not already. Give the user those URLs and note they stay valid for 7 days, so download promptly (re-rendering later is free if a URL has expired). The builder project URL is the alternative when they want to compare the full set visually or hand-tweak before downloading.
 
 ## Headline Rules
 
@@ -118,7 +120,7 @@ Headlines must pass the "one second test": readable at thumbnail size.
 | edit-screenshots | 5 credits |
 | generate-background | 6 credits |
 | upload-screenshots | free |
-| render-screenshots | free |
+| render-screenshots | free, and needs an active paid plan (402 on a trial) |
 | prepare-screenshot-brief | free |
 | list-devices | free |
 | get-project | free |