Overview: Multi-Client AI Support for App Store Connect
The ecosystem of AI development environments has expanded rapidly beyond simple chat interfaces. Modern AI-first IDEs and extensions—such as Google Antigravity IDE, Codeium Windsurf, and the Roo Code extension for VS Code—bring deep agentic reasoning directly into your active workspace.
To enable these environments to interact safely with Apple App Store Connect, FlightDeck implements the open Model Context Protocol (MCP) specification. By configuring FlightDeck as a local MCP server within your preferred editor, your assistant can discover your app catalog, inspect build processing states, audit pre-flight release readiness, and stage metadata changes without leaving your code editor.
This guide provides verified configuration instructions for Google Antigravity IDE, Windsurf, and Roo Code, explains FlightDeck's local security model, and demonstrates how to verify your connection using natural-language smoke-test prompts.
Universal Architecture: How FlightDeck Connects
FlightDeck operates as a native macOS application and local loopback server. When active, it runs an embedded MCP server:
┌────────────────────────────────────────────────────────────────────────┐
│ Local macOS Machine │
│ │
│ ┌─────────────────────┐ │
│ │ AI IDE / Agent │ │
│ │ • Antigravity IDE │ │
│ │ • Windsurf │ │
│ │ • Roo Code │ │
│ └──────────┬──────────┘ │
│ │ Streamable HTTP (JSON-RPC 2.0) │
│ ▼ http://127.0.0.1:51122/mcp │
│ ┌───────────────────────────────────────────────┐ │
│ │ FlightDeck MCP Server │ │
│ │ • Port 51122 (Loopback Only) │ │
│ │ • Reads credentials from macOS Keychain │ │
│ │ • Desktop Approval Center for mutating tools │ │
│ └──────────────────────┬────────────────────────┘ │
│ │ Secure HTTPS │
└──────────────────────────┼─────────────────────────────────────────────┘
▼
┌─────────────────────────┐
│ App Store Connect API │
└─────────────────────────┘
Protocol Specifications
- Transport: Streamable HTTP (JSON-RPC 2.0 over HTTP).
- Default Endpoint:
http://127.0.0.1:51122/mcp(loopback only; port configurable in FlightDeck). - Network Scope: Strict loopback (
127.0.0.1). The server does not bind to external network interfaces, preventing external network access. - Credential Storage: Private keys (
.p8) and API credentials never leave your local machine; they are secured in your macOS Keychain and used to sign short-lived JWT tokens locally in memory. - Human Governance: Read-only inspection tools execute immediately. Any mutating action (such as modifying metadata, attaching builds to beta groups, or submitting a version) is staged in the native FlightDeck Desktop Approval Center for human confirmation.
The fastest and most reliable way to configure any client is to open the FlightDeck Desktop application, navigate to MCP Server, and click Copy Setup Prompt. FlightDeck automatically generates a complete prompt tailored to your active port, endpoint, and token configuration. Note that if you have enabled HTTP Bearer Token authentication, the setup prompt will contain your Bearer token; treat the copied prompt as sensitive credential material and do not publish it to shared chat channels or public repositories.
Configuration Recipes by Environment
1. Google Antigravity IDE
Google Antigravity IDE natively supports the modern Streamable HTTP transport for MCP servers, configured globally or per workspace.
Configuration Steps:
- Ensure FlightDeck is running on your Mac and the MCP Server status is Running.
- Open your Antigravity global MCP configuration file: ``
text ~/.gemini/antigravity/mcp_config.json`` (Alternatively, in Antigravity, navigate to Additional Options (...) > MCP Servers). - Add the
flightdeckserver definition using theurlkey:
{
"mcpServers": {
"flightdeck": {
"url": "http://127.0.0.1:51122/mcp"
}
}
}
If you enabled Require HTTP Bearer Token in FlightDeck, include the Authorization header:
{
"mcpServers": {
"flightdeck": {
"url": "http://127.0.0.1:51122/mcp",
"headers": {
"Authorization": "Bearer YOUR_FLIGHTDECK_TOKEN"
}
}
}
}
- Save the file. Antigravity connects to FlightDeck via Streamable HTTP and indexes its tool inventory.
2. Codeium Windsurf
Windsurf's Cascade assistant connects to HTTP MCP servers configured in Windsurf's settings.
Configuration Steps:
- Ensure FlightDeck is running.
- Open Windsurf's global MCP settings file: ``
text ~/.codeium/windsurf/mcp_config.json`` (Alternatively, open the Cascade panel and click the MCP icon in the top header, or go to Windsurf Settings > Tools > Add Server). - Add the
flightdeckserver configuration using Windsurf'sserverUrlproperty:
{
"mcpServers": {
"flightdeck": {
"serverUrl": "http://127.0.0.1:51122/mcp"
}
}
}
If Bearer token authentication is enabled in FlightDeck:
{
"mcpServers": {
"flightdeck": {
"serverUrl": "http://127.0.0.1:51122/mcp",
"headers": {
"Authorization": "Bearer YOUR_FLIGHTDECK_TOKEN"
}
}
}
}
- Refresh Cascade or reload the Windsurf window (Cmd+Shift+P -> Developer: Reload Window). FlightDeck's tools will appear in Cascade's available tool list.
3. Roo Code (VS Code Extension)
Roo Code provides a dedicated visual MCP management interface inside VS Code alongside global and project-level JSON configuration.
Configuration via UI:
- Open the Roo Code side panel in VS Code.
- Click the MCP Servers icon (plug icon) in the header.
- Click Add Server, select Streamable HTTP as the transport type, and enter
http://127.0.0.1:51122/mcp.
Configuration via JSON:
Open your Roo Code configuration file (cline_mcp_settings.json):
{
"mcpServers": {
"flightdeck": {
"type": "streamable-http",
"url": "http://127.0.0.1:51122/mcp"
}
}
}
Roo Code requires "type": "streamable-http". Do not configure FlightDeck with legacy "type": "sse", as FlightDeck uses the modern Streamable HTTP MCP transport specification.
Smoke Testing Your Connection
Once configured in your chosen editor, verify that your AI assistant can communicate with FlightDeck by running a safe, read-only smoke test.
Smoke-Test Verification Prompt
In your IDE's agent chat window (Antigravity Chat, Windsurf Cascade, or Roo Code prompt), enter:
Use FlightDeck to list the apps in my App Store Connect account and verify our connection. Do not make any changes.
Expected Behavior
- The AI model identifies FlightDeck's read-only application query capability.
- FlightDeck queries Apple's App Store Connect API using the credentials sealed in your macOS Keychain.
- The assistant presents a formatted list of your registered applications:
Connected to App Store Connect via FlightDeck MCP.
Registered Applications:
- FlightDeck Developer Console (com.vibe.flightdeck) — Primary Locale: en-US
Connection is authenticated and operational.
Because this query is read-only, it executes immediately without requiring human confirmation in FlightDeck.
How the Approval Center Safeguards Your App Store State
When an AI assistant needs to perform a state change—such as updating localized metadata, creating a TestFlight group, or selecting a release build—FlightDeck intercepts the request before it reaches Apple:
[Agent requests mutating tool]
│
▼
[FlightDeck stages operation locally]
│
▼
[Desktop Approval Center surfaces proposal card]
│
┌──────┴──────┐
▼ ▼
[Approve] [Reject]
│ │
▼ ▼
Sent to Apple Aborted with explanation to agent
This ensures that even if an AI model misinterprets instructions, your live App Store metadata and releases remain protected under your direct human supervision.
Troubleshooting Common Setup Issues
1. "Connection Refused" (ECONNREFUSED 127.0.0.1:51122)
- Cause: FlightDeck Desktop is not running or the MCP server toggle was stopped.
- Fix: Launch FlightDeck, go to the MCP Server tab, and toggle the server to Running.
- Verification: Check whether the local port is actively bound: ``
bash lsof -i :51122``
2. Port Conflict
- Cause: Another local service on your Mac is occupying port 51122.
- Fix: In FlightDeck, click Change Port to select an alternate port (e.g.,
51123), and update the port in your client's configuration file.
3. Agent Does Not See FlightDeck Tools
- Cause: The IDE configuration file was modified while the editor was running, or contains JSON syntax errors.
- Fix: Validate the JSON syntax in your client's configuration file. Completely restart your IDE to force a reload of the MCP client registry.
4. HTTP 401 Unauthorized
- Cause: FlightDeck has Bearer token authentication enabled, but the client configuration lacks the Authorization header.
- Fix: In FlightDeck's MCP Server screen, copy your active Bearer token and add the
"headers": { "Authorization": "Bearer <TOKEN>" }property to your client configuration.