Shotfleet

What shotfleet MCP server does

The shotfleet MCP server exposes three operations from the installed shotfleet command-line tool: check, doctor, and run. It is intended for AI coding agents working with localized mobile-app screenshots for the App Store and Google Play.

check examines a screenshot folder and returns a short summary. Its checks include whether each image shows the expected language, whether screenshots have been duplicated across languages, whether required images are missing, and whether store size and count rules are met. The command writes check.json and index.html to a report folder, but does not alter the screenshots.

doctor reports whether Maestro, Xcode, and the Android SDK are ready. It identifies missing prerequisites without changing the machine.

run reads a shotfleet.toml configuration, captures screenshots for each language, and checks the resulting files. It boots iOS simulators and Android emulators and installs and runs the configured app, so it is suitable for trusted projects where the agent is allowed to perform those actions.

How it works

The shotfleet MCP server runs locally over stdio through the command shotfleet mcp. The MCP client sends tool calls to the process, and the process delegates the work to the locally installed shotfleet program. The repository supplies agent skills and configuration guidance; it does not contain the closed-source shotfleet application itself.

By default, run does not execute commands supplied through configuration. A call must pass hooks: true before configured hooks can run. Without that option, run also refuses configurations containing a capture build, iOS simctl, or Android shell settings. This guard is relevant when the configuration includes build or device commands.

Setup and configuration

Install shotfleet on macOS before starting the MCP process:

curl -fsSL https://shotfleet.com/install.sh | sh

Then register the stdio command with an MCP client. For Claude Code, the documented command is:

claude mcp add shotfleet -- shotfleet mcp

Other MCP clients should use shotfleet mcp as their stdio server command. The process will not start successfully if shotfleet is absent. The repository also provides optional skills for core usage, report review, and CI setup, but those skills are separate from the MCP protocol connection.

License activation happens outside the agent configuration with shotfleet activate <your key>. Do not place the key in an MCP setting, agent configuration, chat, or repository. For CI, the documented secret name is SHOTFLEET_KEY.

Tools and capabilities

The shotfleet MCP server offers:

• check for language, duplication, missing-file, and store-rule validation.
• doctor for checking Maestro, Xcode, and Android SDK readiness.
• run for multilingual simulator and emulator capture followed by validation.
• JSON and HTML report output from screenshot checks.
• Support for captures driven by a shotfleet.toml file.

The repository’s skills also explain command usage, exit codes, JSON output, troubleshooting, review of check reports, and CI integration.

Limitations and notes

The repository is MIT licensed, while the shotfleet application is paid and closed source. check is free, and run is free for up to two languages; use of run beyond two languages and export requires a shotfleet license.

The server depends on a Mac with shotfleet installed. run can take minutes because it boots simulators and emulators. Since it installs and runs the configured app, only use it with projects and configurations you trust. Although check does not modify screenshots, it does write report files.