Exact store output
The screenshot endpoint returns a base64 PNG at the selected store target, including supported iPhone, iPad, Play phone, tablet, and feature-graphic specifications.
Storeboard API and MCP server
Your store-asset pipeline, available to code and agents.
Use the REST API from a script or CI job, or connect the Storeboard MCP server to an AI agent. Both interfaces use the same generation pipeline, exact store sizes, real UI compositing, headline QA, credits, and account limits as the web app.
Low-quality drafts use no credits. Sign up free to try the workflow.
Storeboard
API and MCP
Two automation interfaces
REST API/api/v1
MCP server/api/mcp
AuthenticationBearer key
One project keeps the direction, files, and store details together.
How it works
From source to finished asset in three clear steps.
- 01
Create an API key
Create a key in the Storeboard dashboard and send it as a Bearer token. Keys are shown once, inherit your account permissions, and can be revoked anytime.
- 02
Analyze, then generate
Start from a website URL, description, or reference image. Reuse the returned style brief to generate exact-size screenshots, a Play feature graphic, and coordinated listing copy.
- 03
Call it from code or an agent
Use JSON endpoints from your own service, or give an MCP-compatible client tools for specs, credits, app analysis, screenshot generation, and listing copy.
One production pipeline
Automation gets the same safeguards as the app.
The public API and MCP tools call the same internal generation functions as the Storeboard interface. That keeps dimensions, credit charging, refunds, usage limits, and final-image QA consistent across every entry point.
Real UI compositing
Send an appScreen image and Storeboard places the real interface into a deterministic device frame instead of asking the image model to repaint it.
Five MCP tools
Connected agents can list specs, check credits, analyze an app, generate a screenshot or feature graphic, and write store listing copy.
The same credit rules
Low-quality drafts remain free. Final images and listing copy use the same credits, rate limits, failure refunds, and account balance as the web app.
Frequently asked questions
The practical details.
What is the difference between the API and MCP server?
The REST API is designed for scripts, services, and CI workflows that send JSON requests. The MCP server exposes the same core capabilities as tools that an MCP-compatible AI client can call.
What can I generate through the API?
The current API can analyze an app, list supported asset specifications, generate screenshots and Play feature graphics, write App Store and Google Play listing copy, and report account credits and limits.
Which tools does the MCP server provide?
The MCP server provides list_specs, get_credits, analyze_app, generate_screenshot, and generate_listing over streamable HTTP.
Can API and MCP generations preserve my real app UI?
Yes. Pass a real app screen to screenshot generation and Storeboard composites it into the final marketing image after the AI creates the background and headline treatment.
Keep building
More ways to finish the listing.
App Store screenshots
Generate cohesive App Store and Google Play screenshot sets at the exact sizes each store expects.
Explore featureListing copy and ASO
Write App Store and Google Play listing copy with hard character limits and competitor-informed keyword suggestions.
Explore featureTeams and agencies
Keep shared projects, pooled monthly credits, team invites, and read-only client previews in one studio.
Explore featureStart with a free draft
Connect Storeboard to the workflow you already use.
Create a key, try a free draft, and generate the rest of the listing from code or an agent.
Read the API and MCP docs