Overview: Navigating FlightDeck's MCP Capabilities
The Model Context Protocol (MCP) allows AI coding assistants to interact with tools exposed by local applications. FlightDeck embeds a specialized MCP server that bridges assistants like Cursor, Claude Code, Google Antigravity, Windsurf, and Roo Code directly to Apple's App Store Connect REST API.
Rather than exposing low-level, fragmented REST endpoints, FlightDeck provides curated semantic tools designed around realistic developer workflows: checking build states, managing TestFlight groups, preparing localized metadata, planning screenshot sets, running pre-flight audits, and submitting releases.
┌───────────────────────────────────────────────────────────────┐
│ FlightDeck Semantic MCP Tools Architecture │
├───────────────────────────────┬───────────────────────────────┤
│ App Store Connect Operations │ FlightDeck Governance & │
│ (Apple API Interaction) │ Staging Engine Tools │
├───────────────────────────────┼───────────────────────────────┤
│ • App Inventory & Metadata │ • Staging & Change Sets │
│ • Builds & Chunked Uploads │ • Approval Center Feedback │
│ • TestFlight & Beta Groups │ • Visual Diff Projections │
│ • Screenshots & Display Sets │ • Operation Logs & Audit Trail│
│ • Review Drafts & Submissions │ • Safety Rule Validation │
│ • Pricing & Subscriptions │ • Dry-Run Simulation Engine │
└───────────────────────────────┴───────────────────────────────┘
Understanding Semantic Tool Counts and Configurations: FlightDeck's MCP tool catalog is organized into 10 functional domains. In the standard shipping desktop application with default settings, FlightDeck advertises 68 semantic tools covering all core App Store Connect operations and essential local staging governance. When development workflow features are enabled (workflowsEnabled = true), an additional 16 workflow automation and execution tools are exposed, bringing the full registry to 84 semantic tools. In specialized automated test harnesses, subsets (such as 48 tools) may be instantiated for isolated testing. Regardless of the environment configuration, all tools adhere to the same unified safety model and Approval Center governance.
Safety Classification: Reads vs. Staged Mutations
Every tool in FlightDeck belongs to a strict safety tier:
- Read-Only Tools (
READ_ONLY): Safe informational queries. They inspect portal data, fetch build logs, or validate readiness. These execute immediately without pausing for developer confirmation. - Mutating Tools (
SAFE_WRITE/DESTRUCTIVE): Operations that alter portal state (e.g., updating keywords, creating beta groups, or submitting for review). Mutations are staged as visual cards in FlightDeck's macOS Approval Center. They are never sent to Apple until you explicitly click Approve Mutation.
Domain 1: App Discovery and Inventory
Tools that identify and inspect applications associated with your Apple Developer account.
- Primary Tools:
apps_list,app_store_version_get. - Safety Classification: Read-Only.
- Approval Required: None.
- Operational Details:
apps_listdiscovers and lists active apps in your App Store Connect account (returning IDs, bundle identifiers, and localized names), whileapp_store_version_getinspects specific version records. For direct single-app inspection, FlightDeck's Universal Operation Dispatcher exposes Apple'sapps_getendpoint (GET /v1/apps/{id}) viaflightdeck_api_catalog. - Manual Web Portal Boundary: Initial App ID and App Record creation must be performed in the Apple Developer portal. Once an app record exists, FlightDeck discovers and manages it.
- Example Natural-Language Prompt:
Using FlightDeck, list the active apps in my App Store Connect account and show their bundle identifiers, platforms, and primary locales. Do not make any changes.
Domain 2: Storefront Versions and Localized Metadata
Tools that manage App Store version records, release notes, descriptions, and keywords across all 39 Apple-supported storefront languages.
- Primary Tools:
app_store_versions_list,app_store_version_get,app_store_version_create,app_store_version_localizations_list,app_store_version_localization_get,app_store_version_localization_update. - Safety Classification: Read-Only for listing/getting; Staged Mutation for creating versions and updating copy.
- Approval Required: Updating keywords, description, marketing URL, or release notes stages a visual diff card in the Approval Center showing exact character counts and before-and-after values.
- Example Natural-Language Prompt:
Using FlightDeck, check the editable version draft for my app. Update the 'What's New' release notes for the English (US) and Japanese localizations based on our latest git commit history. Stage the change for my review.
Domain 3: Binary Ingestion and Build Lifecycle
Tools that inspect uploaded .ipa and .pkg binaries, track Apple ingestion processing states, and manage build metadata.
- Primary Tools:
builds_list,build_get,build_beta_details_get,build_upload_preview,build_upload_start,build_upload_status,flightdeck_operation_stage. - Safety Classification: Read-Only for monitoring; Staged Mutation for uploading binaries or modifying build details.
- Approval Required: Modifying encryption compliance (
ITSAppUsesNonExemptEncryption) or retracting/expiring builds requires explicit approval. - Operational Details: Inspecting build processing and beta attributes is handled via
builds_list,build_get, andbuild_beta_details_get. Staged mutations modifying build attributes (such as encryption compliance flags or auto-notify settings) are dispatched viaflightdeck_operation_stagetargeting Apple'sbuildBetaDetails_updateInstanceendpoint (PATCH /v1/buildBetaDetails/{id}). - Manual Web Portal Boundary: Compiling Swift/Objective-C/Flutter source code and signing the binary requires local build tools (
xcodebuild,flutter build ipa). FlightDeck automates pre-upload validation, chunked upload, and ingestion monitoring. - Example Natural-Language Prompt:
Using FlightDeck, check the processing status of recent builds for [App Name]. If any build is stuck in processing, compare its state to previous builds and explain what stage it is in. Do not expire any builds.
Domain 4: TestFlight and Beta Distribution
Tools that manage internal and external beta testing groups, add builds to groups, and invite or revoke testers.
- Primary Tools:
beta_groups_list,beta_group_create,beta_group_delete,build_add_to_beta_group,build_remove_from_beta_group,flightdeck_operation_stage. - Safety Classification: Read-Only for group listing; Staged Mutation for group creation, tester modifications, and build attachments.
- Approval Required: Creating external groups or attaching builds stages an approval card displaying the target group, build version, and tester impact.
- Operational Details: Managing beta groups and attaching or detaching builds is supported by dedicated semantic tools (
beta_groups_list,beta_group_create,beta_group_delete,build_add_to_beta_group,build_remove_from_beta_group). Managing individual group tester memberships (betaGroups_betaTesters_createToManyRelationship,betaGroups_betaTesters_deleteToManyRelationship) or updating localized build test notes (betaBuildLocalizations_updateInstance) is staged viaflightdeck_operation_stage. - Example Natural-Language Prompt:
Using FlightDeck, find our latest processed TestFlight build for [App Name] and add it to our 'Internal QA' beta testing group. Provide 'What to Test' notes describing our bug fixes. Stage the action for approval.
Domain 5: Storefront Screenshots and Display Assets
Tools that audit screenshot dimensions, plan upload sequences across device form factors, and execute asset delivery.
- Primary Tools:
app_screenshots_list,app_screenshot_upload_plan,app_screenshot_upload_execute,flightdeck_operation_stage. - Safety Classification: Read-Only for auditing; Staged Mutation for uploading, reordering, and deleting screenshots.
- Approval Required: Uploading or replacing display sets requires signoff in the Approval Center.
- Operational Details: Querying screenshot sets and planning/executing multipart chunked uploads are handled by dedicated tools (
app_screenshots_list,app_screenshot_upload_plan,app_screenshot_upload_execute). Deleting existing screenshot assets (appScreenshots_deleteInstance) or reordering display sets (appScreenshotSets_appScreenshots_replaceToManyRelationship) is staged viaflightdeck_operation_stage. - Capability Gaps: FlightDeck does not generate graphical artwork or render frames; developers provide image files (PNG/JPEG) that FlightDeck validates for dimensions and alpha channels before uploading.
- Example Natural-Language Prompt:
Using FlightDeck, audit the screenshot sets for our active App Store version draft. List any missing display sizes for 6.7-inch iPhone and 12.9-inch iPad Pro. Do not delete or upload anything yet.
Domain 6: App Review Submission and Cancellation
Tools that manage the App Review submission container, attach version drafts, submit for review, or cancel in-flight submissions.
- Primary Tools:
review_submissions_list,review_submission_get,review_submission_create_draft,review_submission_add_app_version,review_submission_submit,review_submission_cancel. - Safety Classification: Read-Only for status checks; High-Impact Staged Mutation for creating drafts, submitting, or canceling.
- Approval Required: Submitting to Apple or canceling an active review submission requires explicit approval with a red/amber safety warning badge.
- Example Natural-Language Prompt:
Using FlightDeck, inspect our active App Review submission draft for [App Name]. Confirm whether all required versions and review notes are attached, but do not click submit yet.
Domain 7: Pre-Flight Readiness Audits
Diagnostic tools that evaluate all storefront fields, assets, and build associations against Apple's submission rules before submitting.
- Primary Tools:
release_readiness_check,release_submission_diagnostics_get,release_build_candidates. - Safety Classification: Read-Only.
- Approval Required: None.
- Value: Catches missing URLs, missing demo credentials, unattached builds, and missing localized descriptions locally, saving 24–48 hours of Apple review turnaround.
- Example Natural-Language Prompt:
Using FlightDeck, run a comprehensive pre-flight release readiness check on our draft version for [App Name]. Identify any missing required fields, compliance blockers, or unattached builds.
Domain 8: Pricing, Territories, and In-App Purchases
Tools that inspect pricing schedules, regional territory availability, In-App Purchase products, and subscription groups.
- Primary Tools:
app_price_schedule_get,app_price_schedule_set,app_availability_get,app_availability_set,monetization_review_screenshot_upload,subscription_group_localizations_list,subscription_group_localization_get,subscription_group_localization_create,subscription_group_localization_update,flightdeck_operation_stage. - Safety Classification: Read-Only for schedules and catalog queries; Staged Mutation for schedule modifications, territory restrictions, and localization updates.
- Approval Required: Altering prices or territory distribution stages an Approval Center card highlighting currency tiers and effective dates.
- Operational Details: Reading and staging price schedules and territory availability are supported by
app_price_schedule_get,app_price_schedule_set,app_availability_get, andapp_availability_set. Subscription group localizations have dedicated semantic tools. Staging In-App Purchase product catalog updates or subscription tier structures is dispatched viaflightdeck_operation_stage, while review screenshots are uploaded viamonetization_review_screenshot_upload(and inspected withiap_review_screenshot_getorsubscription_review_screenshot_get). - Manual Web Portal Boundary: Banking details, tax forms (W-8BEN/W-9), and signing the Paid Applications Agreement must be completed in the Apple web portal.
- Example Natural-Language Prompt:
Using FlightDeck, check the current price tier and scheduled future price changes for [App Name]. Also list the subscription groups and active products. Do not modify any price tiers.
Domain 9: Governance and Staging Engine (flightdeck_*)
The internal MCP tools and local storage infrastructure that power FlightDeck's human-in-the-loop governance architecture.
- Key Capabilities:
flightdeck_operation_stage/flightdeck_change_set_stage: Queues mutations into an isolated staging buffer for human signoff.flightdeck_operation_stage_status/flightdeck_change_set_status: Inquires whether the developer clicked Approve, Request Changes, or Reject.flightdeck_operation_stage_cancel/flightdeck_change_set_cancel: Discards staged mutations without touching Apple.flightdeck_operation_execute_staged/flightdeck_change_set_execute: Applies approved changes directly to App Store Connect.- Audit Trail & Inspection: Audit logs are immutably persisted locally on disk at
~/Library/Application Support/asc_mcp/audit.jsonl(queryable via local terminal tools orasc_storage). MCP tools report in-flight staging status rather than serving as a queryable log viewer. - Safety Guarantee: These tools run locally and cannot be bypassed by an AI prompt. If a model attempts a direct REST write, FlightDeck's dispatch engine routes it into staging automatically.
Summary Reference Table
| Functional Domain | Primary MCP Tools | Default Safety Tier | Approval Required? |
|---|---|---|---|
| App Discovery | apps_list, app_store_version_get |
Read-Only | No |
| Storefront Metadata | app_store_version_localization_update |
Staged Mutation | Yes |
| Build Ingestion | builds_list, build_upload_preview |
Read-Only / Staged | Only for uploads |
| TestFlight | beta_group_create, build_add_to_beta_group |
Staged Mutation | Yes |
| Screenshots | app_screenshots_list, app_screenshot_upload_plan |
Staged Mutation | Yes |
| App Review | review_submission_create_draft, review_submission_submit |
High-Impact Mutation | Yes (Explicit Signoff) |
| Pre-Flight Audit | release_readiness_check |
Read-Only | No |
| Pricing & IAP | app_price_schedule_get, app_availability_set |
Read / Staged | Only for price/availability changes |
| Governance Engine | flightdeck_change_set_* |
Local Staging | Managed via Desktop UI |
Related Guides
- Human-in-the-Loop Governance & FlightDeck Approval Center — Detailed review of visual cards and action buttons.
- FlightDeck Architecture: Local Loopback MCP Server and Direct Apple API — How MCP tools communicate with Apple.
- Pre-Flight App Store Submission Readiness Check — Step-by-step readiness audit recipe.
- Creating and Submitting an App Review Draft via FlightDeck MCP — End-to-end review submission guide.