Blitz is a native macOS application that connects AI agents to App Store Connect for managing and submitting iOS apps. Developers use it to control parts of the iOS release process, including simulator runs, in-app purchases, screenshots, TestFlight testers, and review submissions. The catalogue includes skills, an instruction, and an MCP connection for operating Blitz.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/blitzdotdev/blitz-macWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/blitzdotdev/blitz-mac/blitz)<a href="https://agentmods.dev/mcp/blitzdotdev/blitz-mac/blitz"><img src="https://agentmods.dev/badge/mcp/blitzdotdev/blitz-mac/blitz/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/blitzdotdev/blitz-mac/blitz"><img src="https://agentmods.dev/badge/mcp/blitzdotdev/blitz-mac/blitz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
blitz scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"blitz": {
"command": "npx",
"args": [
"-y",
"@blitzdev/blitz-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines scan A 94341fa9a779
blitz is an MCP server published in the GitHub repository blitzdotdev/blitz-mac (1,760 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
asc-mcp
Every App Store Connect + StoreKit 2 endpoint. 890 tools in 13 profiles, narrow to 27. Runs locally from the @erayendes/asc-mcp npm package. Needs 5 environment variables to run.
ASC-Access
Heimdall — MCP server for the Apple App Store Connect API and App Store Server API (StoreKit 2). 890 tools across 13 profiles, generated from Apple's official OpenAPI spec, plus review triage and reply drafting that runs on your own model, and confirm-bef. Runs locally from the @erayendes/asc-mcp npm package.
app-publish
MCP server for App Store Connect & Google Play Console — iOS/Android app management. Runs locally from the app-publish-mcp npm package. Needs 4 environment variables to run.
appstore-connect
MCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more. Runs locally from the asc-mcp npm package.
appstoreconnect-mcp
App Store Connect for MCP clients: PPP pricing, subscriptions, TestFlight, reviews, reports & more. Runs locally from the @akoskomuves/appstoreconnect-mcp npm package. Needs 4 environment variables to run.
storepilot-mcp
StorePilot — one MCP server to run your entire app portfolio across Google Play and the App Store. Runs locally from the storepilot Python package. Needs 6 environment variables to run.