Pre-Flight Release Readiness Audit
Check if an upcoming release version satisfies all App Store Connect submission requirements and guideline prerequisites.
A tested library of copy-paste prompts and operational patterns to command your AI coding agent (Claude Desktop, Cursor, Antigravity IDE) to manage App Store Connect directly from your editor.
Before commanding an AI agent, understand how FlightDeck ensures security, privacy, and full developer control over your App Store presence:
FlightDeck binds strictly to local loopback (http://127.0.0.1:51122/mcp by default). No third-party proxy, relay, or cloud database sits between your Mac and Apple.
Private .p8 API keys reside in the secure macOS Keychain. FlightDeck signs ES256 JWTs locally with 15-minute expirations.
FlightDeck maintains zero shadow database. All reads query live Apple resources, and mutations target live Apple endpoints directly.
With AI Approval: ON (default), mutations create a staged change set. You inspect structured visual cards and field-level diffs in macOS before authorizing execution.
No matching prompts found
Try searching for a different keyword or resetting your category filter.
Connect your Mac, App Store Connect, and your AI assistant in five straightforward steps. FlightDeck runs an embedded Model Context Protocol (MCP) server listening strictly on local loopback (default: http://127.0.0.1:51122/mcp) over Streamable HTTP transport.
Download FlightDeck from the Mac App Store (macOS 12.0+). In Apple’s developer portal (Users and Access → Integrations → App Store Connect API), generate an API key:
Generated under Team Keys by an Account Holder or Admin. Grants access across apps in your organization.
.p8 fileGenerated under Individual Keys tied to your personal developer account across teams.
.p8 file (no Issuer ID needed)
In FlightDeck, click Add Account. Your credentials are saved securely into your encrypted macOS Keychain (kSecClassGenericPassword). FlightDeck never operates an intermediary cloud database; API requests travel directly between your Mac and Apple over HTTPS. See our API Keys Guide and Team vs Individual Keys Guide.
In FlightDeck Desktop, open the MCP Server settings screen and click Start Server.
FlightDeck binds to local loopback over Streamable HTTP transport:
http://127.0.0.1:51122/mcp
Important: 51122 is the shipping default port. If you configured a custom port in FlightDeck settings, always use the exact port and endpoint URL displayed in your running FlightDeck Desktop window.
Click Copy Setup Prompt in the MCP Server view. This generates a tailored prompt containing your active endpoint URL, port, and security settings to paste into your AI assistant.
Configure FlightDeck in your preferred AI coding tool. Select your client below for exact configuration syntax:
Configure in ~/.cursor/mcp.json or Cursor Settings → Features → MCP → Add New MCP Server:
{
"mcpServers": {
"flightdeck": {
"url": "http://127.0.0.1:51122/mcp"
}
}
}
Register directly from Terminal using explicit HTTP transport:
claude mcp add --transport http flightdeck http://127.0.0.1:51122/mcp
Add --scope user to make it available across all directories.
Add to global configuration in ~/.gemini/config/mcp_config.json (or project .gemini/config/mcp_config.json):
{
"mcpServers": {
"flightdeck": {
"url": "http://127.0.0.1:51122/mcp"
}
}
}
Windsurf: in ~/.codeium/windsurf/mcp_config.json using "serverUrl":
{"mcpServers": {"flightdeck": {"serverUrl": "http://127.0.0.1:51122/mcp"}}}
Roo Code: in cline_mcp_settings.json with "type": "streamable-http" (legacy SSE is rejected):
{"mcpServers": {"flightdeck": {"type": "streamable-http", "url": "http://127.0.0.1:51122/mcp"}}}
If you enable Require Password in FlightDeck’s MCP Server settings, the generated setup prompt will contain an HTTP Bearer authentication token. Treat this token as confidential:
.p8 private keys or authentication tokens into AI chats, shared Discord/Slack channels, or public issue trackers.127.0.0.1) and uses the active port configured in FlightDeck Desktop.Open your AI assistant (Cursor Composer, Claude Code, Antigravity Chat, or Windsurf Cascade) and paste this initial smoke-test prompt:
Read queries execute immediately with zero approval needed. But what happens when an AI assistant wants to update release notes, add TestFlight testers, or submit a build?
With AI Approval: ON (default for every capability), mutating operations do NOT execute directly against Apple. Instead, FlightDeck intercepts the mutation and creates a staged proposal in the native macOS Approval Center.
In the Approval Center, you inspect structured visual cards showing the target app, version, proposed operation, and before-and-after field diffs. You can:
Note: Approving a mutation authorizes FlightDeck to send it to Apple; Apple independently validates business rules and schema invariants. For details, see our Approval Center & Human Governance Guide and Execution vs Staging Rules Guide.
Automate pre-flight submission readiness audits, version creation, build linking, prerequisite attestations, guideline verification, rejection triage, and submission to Apple App Review.
Check if an upcoming release version satisfies all App Store Connect submission requirements and guideline prerequisites.
Create a new version draft in App Store Connect for an upcoming release.
Find eligible processed builds and associate the chosen build with the release version.
Clear mandatory Apple submission blockers, such as encryption declarations (ITSAppUsesNonExemptEncryption), third-party content rights, or EU trader status.
Audit metadata, binary entitlements, and privacy declarations against Apple's official App Store Review Guidelines.
Assemble review items, run preflight validation, and submit the final release package to Apple App Review.
Analyze rejection notes from Apple App Review, map them to official guidelines, and generate an immediate fix plan.
Pull back a version currently waiting for review or in review to fix critical regressions.
Audit release notes across global locales, translate "What's New" text, synchronize disk metadata (Fastlane/Git), optimize keyword densities, and manage global app subtitles.
Review release notes across all active languages to find missing translations or formatting discrepancies.
Generate or update localized "What's New" release notes across multiple languages from a Git changelog or summary draft.
Sync on-disk metadata files (e.g. fastlane/metadata/ or locales/*.json) with live App Store Connect records.
Inspect current keywords, subtitles, and promotional text, and stage optimized strings for better App Store discoverability.
Manage global app identity attributes governed at the app info level.
Direct the local compiler, upload binaries via FlightDeck, transform Git changelogs into "What to Test" notes, monitor processing pipelines, and manage beta groups.
Direct the local compiler to archive and export the app, validate the binary against Apple requirements, and stream it to App Store Connect via FlightDeck.
Extract recent Git commits since the last release tag and publish them as TestFlight beta notes.
Monitor newly uploaded .ipa or .pkg binaries as Apple processes them.
Promote a processed build into a TestFlight beta group for immediate testing.
Set up a targeted feedback group for specific QA testers or beta cohorts.
Stop beta testing for a build containing a critical issue or regression.
Audit current screenshot coverage across display targets, stage batch uploads from local directories, and bridge simulator automation directly into App Store Connect.
Inspect current screenshots across all display types and locales to detect missing device sizes.
Stage a batch upload of local screenshot image files to App Store Connect.
Bridge local simulator screenshot automation (Fastlane Snapshot, Maestro, or custom scripts) directly into App Store Connect.
Schedule tier changes, verify international country storefront availability, and upload required App Review proof screenshots for in-app subscriptions.
Query the active price tier and schedule a future price change.
Inspect which international App Store storefronts the app is distributed in.
Upload required review proof screenshots for auto-renewable subscriptions before submitting to Apple.
Inspect pending change sets staged by your agent, discard draft proposals safely, or trigger sequential execution after human review in FlightDeck.
Approval Center Controls & Request Changes Workflow:
By default, FlightDeck enforces AI Approval: ON for all mutation capabilities. When an agent proposes a write action (such as modifying localized metadata, updating pricing, or submitting a version), FlightDeck stages the request as an immutable Change Set with a cryptographic SHA-256 fingerprint. Staged changes cannot be edited in place.
If a staged proposal requires adjustments, click Request Changes in FlightDeck and provide your guidance. FlightDeck returns this feedback directly to the AI agent across MCP. The agent can then interpret your instructions and submit a revised change set for review.
Review everything an AI agent has staged before committing any changes to Apple.
Discard unintended changes proposed by an agent before they touch App Store Connect.
Execute a verified batch of operations after human review in FlightDeck.
The complete, hands-off release workflow from compiler export to App Store Review submission, safely staged for one-click human approval.
Orchestrates compilation, binary upload, version creation, changelog sync, build linking, export compliance, readiness checks, and review submission in a single prompt.
Follow these three foundational best practices when writing prompts for Claude, Cursor, or Antigravity IDE.
When managing multiple apps or versions, include the exact App Name, Bundle ID, or Apple App ID (e.g. id: "6470000000") in your prompt so the agent immediately picks the correct resource.
Ask the agent to inspect the current state first (e.g., "Check our existing German release notes, and then update them..."). This ensures accurate diffs and prevents unintentional overwrites.
You never have to trust an AI agent blind. Keep AI Approval: ON in FlightDeck, let your agent stage multi-locale changes, and inspect the structured visual cards and diffs in the native macOS Approval Center before authorizing execution.
Looking to connect an AI client or configure your App Store Connect credentials? See our complete Quickstart & Agent MCP Setup Guide at the top of this documentation page.
Usage & Rate Limits: FlightDeck imposes zero request caps, metering fees, or operational quotas. App Store Connect API interactions are governed solely by Apple’s standard API rate limits and the subscription or token costs of your AI provider.