Local MCP server/Design

AppScreenStudio MCP server

Local MCP server

AppScreenshotStudio is a local stdio MCP server for composing App Store and Google Play screenshots. It runs on the user's machine with npx -y @appscreenshotstudio/mcp, needs Node.js 18 or newer, reads APPSCREENSHOTSTUDIO_API_KEY from the environment and opens no network ports. It supports iOS, Android and both-store canvases, with Android targets including android-phone at 1080x2340, pixel-11-pro and galaxy-s26-ultra. There is no hosted endpoint.

API key in APPSCREENSHOTSTUDIO_API_KEY Source checked Nov 13, 2026 Local install path Reviewed 2026-11-16
About

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.

Install

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.

  1. Create an API key

    Create a key in AppScreenshotStudio settings and keep it in the client environment.

  2. 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.

Troubleshooting

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.
Safety

Before you connect

Local process, your machine
  • 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.
Review path

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.

Reference

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