Where it fits
Mobile developers who want screenshot sets for both app stores generated from a local tool.
- Generate an App Store screenshot set.
- Generate Google Play screenshots for Android device targets.
- Keep the API key on the local machine.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with AppScreenStudio
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Explore what the user wants, what they assume, and which approach is worth committing to before any creative work. Use before building a feature, component, plan, or other new work where a wrong direction is costly.
Shared vocabulary for designing deep modules. Use it to design or improve a module's interface, find opportunities to deepen one, decide where a seam goes, or make code easier to test and navigate with AI, or when another skill needs the deep-module vocabulary.
Produces several sharply different interface designs for the same module, with sub-agents working in parallel. Use it when someone wants to design an API, survey interface options, weigh different module shapes, or says design it twice.
No skills found
Try a different search term or clear the filters.
Run the AppScreenshotStudio stdio server
The provider ships a local stdio package, not a hosted endpoint. It runs on the user's machine, needs Node.js 18 or newer, reads the API key from the environment and opens no network ports.
- Create an API key
Create a key in AppScreenshotStudio settings and keep it in the client environment.
- Add the local server
Register the npx package as a local stdio server with the key in its environment.
claude mcp add appscreenshotstudio -- npx -y @appscreenshotstudio/mcp
This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
- The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Before you connect
- The MCP server process runs on your machine, not on a provider host.
- Data leaves only through the model provider and any MCP servers you attach.
- Review the local command, package, and files it can reach before running it.
- Stop the process or remove the client entry when you no longer need it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
AppScreenStudio documentationhttps://appscreenshotstudio.com/docs/mcp