Skip to main content
AI agents, MCP, and App Store Connect Level: Beginner 15 min read

FlightDeck Architecture: Local Loopback MCP Server and Direct Apple API

Understand FlightDeck's security and communication architecture: local Streamable HTTP MCP loopback, macOS Keychain encryption, direct Apple REST API integration, and the native Approval Center.

Published: 2026-11-01 • Last Updated: 2026-11-01 • Author: Kip Lawrence
Key MCP Tools: apps_list

Overview: How FlightDeck Bridges AI Assistants to Apple

Modern AI coding assistants (such as Cursor, Claude Code, Google Antigravity, Windsurf, and Roo Code) excel at writing code, generating assets, and diagnosing build errors. However, they lack native access to Apple's App Store Connect REST API. Connecting an AI model to Apple traditionally posed severe security risks: developers were forced to either paste private .p8 keys into cloud prompts or trust third-party proxy services with administrative control over their developer accounts.

FlightDeck resolves this problem by implementing a local-first, zero-relay architecture. FlightDeck runs natively on your Mac as an interactive desktop application. It embeds a local Model Context Protocol (MCP) server bound exclusively to your loopback network interface (127.0.0.1:51122), secures credentials in the macOS Keychain, and connects directly to Apple's official API endpoints over HTTPS.

TEXT
┌─────────────────────────┐             ┌─────────────────────────┐
│   AI Coding Assistant   │             │   FlightDeck Desktop    │
│ (Cursor, Claude, etc.)  │             │   macOS Application     │
└────────────┬────────────┘             └────────────┬────────────┘
             │                                       │
             │ 1. Local JSON-RPC / Streamable HTTP   │
             │    http://127.0.0.1:51122/mcp         │
             ▼                                       ▼
┌─────────────────────────┐             ┌─────────────────────────┐
│ FlightDeck Local Server │ ──────────► │ Desktop Approval Center │
│ (Embedded Daemon)       │ ◄────────── │ (Human Signoff UI)      │
└────────────┬────────────┘             └────────────┬────────────┘
             │                                       │
             │ 2. Read Credentials                   │ 3. Sign Short-Lived JWT
             ▼                                       ▼
┌─────────────────────────┐             ┌─────────────────────────┐
│     macOS Keychain      │             │  Direct HTTPS to Apple  │
│ (SecItemAdd / Bridge)   │             │ api.appstoreconnect...  │
└─────────────────────────┘             └─────────────────────────┘
Note

Data Transmission Boundaries: When your AI assistant executes a task through FlightDeck, API requests travel directly between your Mac and Apple (api.appstoreconnect.apple.com). FlightDeck does not operate any intermediary proxy servers, cloud databases, or relay nodes. Conversation text between you and your AI assistant is governed by your assistant's provider (e.g., Anthropic, OpenAI, or Google), not FlightDeck.


The Eight Architectural Components

FlightDeck's operation relies on eight interconnected components working on your local Mac:

1. The AI Coding Assistant

Your development environment (Cursor, Claude Code CLI, Google Antigravity, Windsurf, or Roo Code). The assistant receives your natural-language requests (such as "Show me our recent TestFlight builds" or "Update the French description for version 1.1"), translates them into semantic MCP tool calls, and formats the returned data into actionable chat responses.

2. The MCP Client Transport

The communication pipeline between the IDE and FlightDeck. FlightDeck implements the standard Streamable HTTP transport (POST /mcp). The client establishes a local HTTP connection to loopback address 127.0.0.1 on port 51122 (or your configured custom port). If password protection is enabled, the client includes an HTTP Bearer token in the Authorization request header.

3. The Local FlightDeck MCP Server

An embedded server process running inside the native macOS FlightDeck application. It listens for JSON-RPC 2.0 messages, performs tool discovery, validates request arguments, enforces safety classifications, and coordinates with the desktop interface.

4. Desktop Settings and Local Authentication

The control plane within FlightDeck Desktop. It manages:

  • Port Selection: Binds by default to 51122, with full support for custom unprivileged ports (1024–65535).
  • Local Loopback Security: By default, loopback requests on 127.0.0.1 proceed without authentication (Authentication: None (local loopback only)). For multi-user workstations or defense-in-depth, developers can enable a persistent MCP password in Desktop Settings, stored securely in the macOS Keychain under reference asc:mcp:http_password. When enabled, incoming HTTP requests must supply matching Authorization: Bearer <token> headers before payloads are buffered.
  • Active Connection Profile: Determines which Apple Developer team credentials are used.

5. The macOS Keychain

Apple's native, encrypted operating system credential store (quest.kip.flightdeck.keys). Your App Store Connect .p8 private key is imported into the Keychain using kSecClassGenericPassword with kSecAttrAccessibleAfterFirstUnlock. Secrets are protected by macOS data protection and user login authorization. FlightDeck's native helper streams private key material strictly over standard input (stdin) and receives it over standard output (stdout), ensuring secrets are never placed into command-line arguments (argv) where they could be inspected by ps aux.

6. Direct Apple App Store Connect API Connection

When an authorized operation executes, FlightDeck retrieves the private key into application memory, generates an Apple-compliant ES256 JSON Web Token (JWT), and dispatches the REST request directly to api.appstoreconnect.apple.com over HTTPS. The TLS connection is negotiated directly between your Mac's native networking stack and Apple's edge servers. The JWT has a 15-minute lifetime (well within Apple's 20-minute maximum). Private keys never leave your Mac and are never transmitted over the network.

7. The Desktop Approval Center

FlightDeck's human-in-the-loop governance interface. When an assistant attempts a mutating operation (such as adding a build to a beta group, updating storefront keywords, or submitting an app for review), FlightDeck intercepts the request. The mutation is staged as a visual card displaying exact before-and-after values and safety badges (READ_ONLY, SAFE_WRITE, DESTRUCTIVE). The developer must click Approve Mutation (or Approve All) in the desktop UI before any request is sent to Apple.

8. Apple-Side Readback Verification

Following approval and execution, the AI assistant dispatches an immediate read-only follow-up query to Apple. This confirms that Apple accepted the change, business validation passed, and the portal state matches the intended outcome.


What Data Travels Where: A Strict Boundary Analysis

Understanding security requires clarity about what information leaves your workstation:

Data Category Stored Locally Leaves Your Mac? Destination Intermediary Proxy?
Apple .p8 Private Key macOS Keychain NO Never leaves local Keychain and memory None
Key ID & Issuer ID Local App Storage YES Direct to Apple in JWT header/claims None (Direct to Apple)
MCP Persistent Password macOS Keychain & IDE Config NO Optional; loopback interface (127.0.0.1) only None
Storefront Metadata & Descriptions Staged in Memory YES Direct to Apple App Store Connect REST API None (Direct to Apple)
Compiled Binaries (.ipa / .pkg) Local Disk YES Direct to Apple Ingestion Storage (upload.itunes.apple.com) None (Direct to Apple)
AI Conversation Prompts & Code IDE / Editor YES Your chosen AI Provider (Anthropic, OpenAI, Google) Subject to your AI provider's privacy policy
Warning

Distinct Trust Boundaries: Local MCP vs. AI Model Providers: FlightDeck ensures that your .p8 private keys and Apple mutations remain strictly between your local Mac and Apple's official API servers. However, your AI assistant operates across an entirely separate trust boundary: conversation prompts, source files in context, and AI responses are transmitted over the internet to your AI provider's infrastructure (e.g. Anthropic, OpenAI, or Google) under that provider's commercial terms. To protect your Apple account, never paste .p8 private key material or Bearer passwords into chat prompts, because those strings would be sent to your AI provider's servers.


Staging vs. Execution: The Governance Model

FlightDeck divides all operations into two strict categories:

1. Read-Only Operations (Immediate Execution)

Queries that inspect state (such as apps_list, builds_list, or release_readiness_check) execute immediately. They do not alter portal state, consume quotas, or modify metadata. The assistant receives the data and continues the workflow without pausing for manual intervention.

2. Mutating Operations (Staged in Approval Center)

Operations that modify Apple state (such as beta_group_create, app_store_version_localization_update, or review_submission_submit) cannot execute autonomously. FlightDeck places the mutation into a staged state and presents the developer with four explicit actions:

  • Approve Mutation: Authorizes FlightDeck to transmit the single staged operation to Apple.
  • Approve All (N): Authorizes a multi-step sequence (e.g., updating 10 storefront localizations).
  • Request Changes: Rejects the proposed payload and feeds your typed feedback directly back to the AI assistant over MCP, allowing it to revise its proposal.
  • Reject: Discards the staged change set immediately with zero impact on Apple App Store Connect.

Edge Cases and Disconnection Behavior

What happens if the AI assistant disconnects?

If your IDE closes or the assistant terminates while operations are pending, FlightDeck Desktop remains unaffected. Staged mutations remain safely parked in the Approval Center. They will not execute automatically and can be reviewed or discarded at any time.

What happens if FlightDeck Desktop closes?

Closing the FlightDeck application terminates the loopback HTTP server. The socket on port 51122 closes immediately. Subsequent requests from AI assistants fail with ECONNREFUSED. Your .p8 private keys remain securely encrypted in the macOS Keychain.

Why do some operations require the Apple Developer web portal?

FlightDeck automates operational workflows supported by the App Store Connect REST API. Certain legal and administrative actions are strictly restricted by Apple to interactive browser sessions in the developer portal:

  • Enrolling in the Apple Developer Program ($99/year fee).
  • Accepting the legal Paid Applications Agreement and submitting tax forms (W-8BEN/W-9).
  • Transferring an application to another developer account.
  • Initial creation of an App ID and App Record.

Verifying Architecture with a Read-Only Prompt

To observe FlightDeck's architecture in action, issue this read-only exploration prompt in your AI assistant:

TEXT
Using FlightDeck, check our connection to App Store Connect, show the active profile display name, and list the accessible apps. Do not stage or execute any mutations.

What You Will Observe

  1. Your assistant issues an apps_list JSON-RPC call over 127.0.0.1:51122/mcp.
  2. No approval prompt appears because read-only tools execute without interruption.
  3. FlightDeck signs a 15-minute ES256 JWT, queries Apple directly, and returns your application list.

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store