Blitz

What the blitz MCP server does

The blitz MCP server gives AI agents access to iOS release and testing tasks from a native macOS application. Its primary connection is to Apple App Store Connect, with additional control over the local iOS Simulator. This lets an agent work across preparation, metadata, testing, and submission rather than handling each step manually in separate tools.

Supported App Store Connect workflows include submitting an app for review, managing app versions, editing pricing and listings, creating in-app purchases and subscriptions, and associating those purchases with versions. The app can also upload screenshots for required device sizes and locales, add TestFlight testers, and manage builds.

How it works

The blitz MCP server is built into the macOS application and binds to 127.0.0.1, so the MCP endpoint is available locally rather than exposed to the network. An MCP client such as Claude Code, Codex, or Cursor communicates with the app and asks it to perform supported App Store Connect or simulator operations.

Simulator capabilities include booting and shutting down devices, sending touch and swipe input, and capturing the live screen. The project also bundles the asc-cli helper for App Store Connect operations that may not be covered by the graphical workflow. That helper shares authentication with Blitz and is available in agent sessions.

Setup and configuration

Download the macOS application from the Blitz website, or build it from source. A source build requires macOS 14 or later, Xcode 16 or later, Node.js 18 or later, and Go 1.26 or later. After cloning the repository, initialize its submodules, run the Swift build, bundle the application, and open the resulting .app file.

Signed builds use Apple Developer credentials supplied through a local .env file based on .env.example. The bundled App Store Connect helper normally comes from the pinned repository submodule. Development or CI builds can override that source with BLITZ_ASCD_SOURCE_DIR or use a compatible prebuilt helper through BLITZ_ASCD_PATH.

Tools and capabilities

The blitz MCP server provides roughly 35 MCP tools covering:

• App Store Connect submissions, versions, pricing, and listings
• In-app purchase and subscription creation
• Attaching purchases to app versions
• Screenshot uploads across device sizes and locales
• TestFlight tester and build management
• iOS Simulator startup, shutdown, touch, swipe, and screen capture
• App Store Connect CLI operations for edge cases

Limitations and notes

The blitz MCP server requires macOS because the application is native to that platform and controls local iOS development tooling. Its simulator capture is limited to the iOS Simulator window. The built-in MCP service is localhost-only and is not intended for remote network access.

Official release builds may send anonymous product telemetry. The documented events include launches, project inventory or creation activity, and MCP or App Store Connect tool usage; the release does not record project names, paths, bundle IDs, prompts, terminal contents, or App Store Connect form values. Source, forked, and debug builds keep telemetry disabled unless analytics settings are explicitly embedded. App Wall synchronization is optional and can send selected public listing metadata and submission history when enabled.