About Storeboard
Storeboard is a hosted MCP server for agents creating App Store and Google Play assets and listing copy. It generates assets at specified dimensions and can composite supplied app screens into device frames.
Key features
- 01List asset specs and credit costs
- 02Analyze app references
- 03Generate exact-size screenshots
- 04Create Play feature graphics
- 05Draft Apple and Google Play listings
Use cases
- 01Preparing store screenshots for an app launch
- 02Creating a Play feature graphic
- 03Analyzing an app URL or reference image
- 04Writing store listing copy from screenshot headlines
MCP support
The hosted Streamable HTTP MCP server exposes tools for specifications, account credits, app analysis, screenshot and graphic generation, and listing copy.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://storeboard.dev/api/mcpclaude mcp add --transport http ophydami-storeboard https://storeboard.dev/api/mcp{"mcpServers":{"ophydami-storeboard":{"type":"http","url":"https://storeboard.dev/api/mcp"}}}Open in Cursor{"servers":{"ophydami-storeboard":{"type":"http","url":"https://storeboard.dev/api/mcp"}}}Open in VS Code{"mcpServers":{"ophydami-storeboard":{"type":"http","url":"https://storeboard.dev/api/mcp"}}}{"mcpServers":{"ophydami-storeboard":{"serverUrl":"https://storeboard.dev/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://storeboard.dev/api/mcpAuth requiredTools
Details
From the project READMEStoreboard MCP server
Connect an MCP-compatible agent to Storeboard and generate exact-size App Store and Google Play assets from the conversation.
This repository contains the public metadata and client configuration for Storeboard's hosted MCP server. The hosted endpoint is:
https://storeboard.dev/api/mcp
Storeboard uses Streamable HTTP and the same Bearer API keys, credits, account limits, generation pipeline, and QA process as the web application and REST API.
Links
Available tools
| Tool | Purpose |
|---|---|
list_specs | List supported assets, exact pixel sizes, and credit costs |
get_credits | Read the current plan, credits, and usage limits |
analyze_app | Analyze an app URL, description, or reference screenshot |
generate_screenshot | Generate an exact-size screenshot or Play feature graphic |
generate_listing | Generate Apple and Google Play listing copy |
Low-quality image drafts are free. Medium and high quality images cost credits and are checked against the requested headline. Supplying appScreen makes Storeboard composite the real app UI into a deterministic device frame.
Claude Code
Create a Storeboard API key, then run:
claude mcp add --transport http storeboard \
https://storeboard.dev/api/mcp \
--header "Authorization: Bearer sb_live_your_key"
JSON configuration
For clients that accept MCP server JSON:
{
"mcpServers": {
"storeboard": {
"type": "http",
"url": "https://storeboard.dev/api/mcp",
"headers": {
"Authorization": "Bearer sb_live_your_key"
}
}
}
}
Keep the key out of source control. If your client supports environment interpolation, use it instead of writing a key directly in the configuration file.
Example prompts
Analyze https://myapp.example and propose five App Store screenshot concepts.
List the available Storeboard specs, then create a free iPhone draft for the first concept.
Write Apple and Google Play listing copy using these screenshot headlines.
Registry metadata
server.json describes the hosted server for the official MCP Registry. smithery-config-schema.json maps a user-provided Storeboard authorization value to the upstream Authorization header for Smithery.
This metadata repository is available under the MIT License. Use of the hosted Storeboard service remains subject to Storeboard's terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.