flutter-ios-bridge-mcp
An MCP server that lets AI assistants build, sign, test, and ship Flutter iOS apps from Windows/Linux without a local Mac.
Check which backends are configured and audit/fix iOS project issues such as Info.plist, bundle ID, deployment target, Podfile, icons, and entitlements.
Generate and manage GitHub Actions iOS workflows, trigger builds, wait for runs, fetch logs/artifacts, cancel runs, and upload signing secrets.
Set up and inspect iOS code signing and manage App Store Connect resources like bundle IDs, capabilities, devices, certificates, profiles, and TestFlight builds/groups.
Use an optional remote Mac over SSH to sync, build, run apps on the iOS Simulator, take screenshots, read logs, open deep links, execute commands, and fetch files.
Use an optional USB-connected iPhone from Windows/Linux to list devices/apps, install/uninstall IPAs, get device info, and capture syslog.
Use built-in prompts like
ship_to_testflightandfix_ios_buildfor guided workflows.
Integrates with App Store Connect to manage certificates, provisioning profiles, bundle IDs, capabilities, devices, and TestFlight builds and distribution.
Generates and triggers GitHub Actions workflows on macOS runners, waits for runs, retrieves logs and artifacts, and sets signing secrets for iOS CI builds.
Provides iOS project tooling to audit and fix configuration, build and run on simulators, install apps on USB-connected iPhones, and read device syslogs.
Allows using a remote Mac over SSH to sync projects, build, run iOS Simulator apps, capture screenshots, retrieve logs, open deep links, and execute commands.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@flutter-ios-bridge-mcp Ship my Flutter app to TestFlight from this repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
flutter-ios-bridge-mcp
Ship Flutter apps to iOS from Windows or Linux — no Mac needed.
An MCP server that gives your AI assistant (Claude Desktop, Claude Code, Cursor, VS Code Copilot, Windsurf…) the tools to build, sign, test and upload iOS apps. It connects your machine to the Apple parts of the toolchain:
Backend | What it gives you | Needs |
Project tools (always on) |
| nothing |
GitHub Actions macOS runners | Simulator | GitHub repo + token |
App Store Connect API | Certificates from a locally generated CSR (no Keychain), provisioning profiles, bundle ids, capabilities, devices, TestFlight builds & groups | Apple Developer account + API key |
Remote Mac over SSH (optional) | Sync → build → run on the iOS Simulator → screenshots returned to the AI → logs, deep links | any Mac you can SSH into |
USB iPhone (optional) | List devices, install IPAs, read syslog from Windows/Linux |
|
Read the story behind it: No Mac? You can still ship your Flutter app to iOS. A full working example: flutter-ios-bridge-demo.
Install
pipx install flutter-ios-bridge-mcp # from PyPI
pipx install git+https://github.com/guru-prasath-j/flutter-ios-bridge-mcp.git # latest from GitHub
# optional: USB iPhone support
pipx inject flutter-ios-bridge-mcp pymobiledevice3Then:
flutter-ios-bridge-mcp init # writes a commented config.toml (or use env vars)
flutter-ios-bridge-mcp status # shows what is configured
flutter-ios-bridge-mcp doctor path/to/flutter_app # iOS audit, no AI neededRelated MCP server: appstore-connect-mcp
Connect it to your MCP client
Claude Desktop (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/.config/Claude/… on Linux):
{
"mcpServers": {
"flutter-ios-bridge": {
"command": "flutter-ios-bridge-mcp",
"env": {
"FIB_PROJECT_PATH": "C:/Users/me/code/my_app",
"GITHUB_TOKEN": "github_pat_...",
"ASC_KEY_ID": "ABC123XYZ",
"ASC_ISSUER_ID": "00000000-0000-0000-0000-000000000000",
"ASC_PRIVATE_KEY_PATH": "C:/keys/AuthKey_ABC123XYZ.p8"
}
}
}
}Claude Code: claude mcp add flutter-ios-bridge -- flutter-ios-bridge-mcp
VS Code / Cursor (.vscode/mcp.json / .cursor/mcp.json): same command + env shape.
No pipx on PATH? Use "command": "pipx", "args": ["run", "flutter-ios-bridge-mcp"].
Configuration
Environment variables win over config.toml (%APPDATA%\flutter-ios-bridge\config.toml on Windows, ~/.config/flutter-ios-bridge/config.toml elsewhere; override with FIB_CONFIG).
Variable | Purpose |
| Default Flutter project |
| Fine-grained PAT: Actions R/W, Secrets R/W, Contents R. Falls back to |
|
|
| App Store Connect API key |
| Optional remote Mac |
Signing material created by the tool lives in ~/.flutter-ios-bridge/signing/ (private keys are chmod 600). Back it up — the certificate private key never leaves your machine except as an encrypted GitHub secret.
The zero-Mac path to TestFlight
Ask your assistant "Ship my app to TestFlight" (or use the built-in ship_to_testflight prompt). Under the hood:
ios_doctor→ fix bundle id, missing permission strings, deployment target / Podfile mismatch, icon alpha channel.ci_generate_workflow→ commit & push.github/.ci_trigger_build(build_type="unsigned-ipa")→ci_wait_for_run→ on failureci_get_logspulls the exact Xcode/CocoaPods errors.Create the app record once in App Store Connect.
signing_quick_setup(profile_kind="app-store")→ GitHub secrets.ci_trigger_build(build_type="signed-ipa", testflight=true).testflight_builds→testflight_distribute.
Testing on a real iPhone without a Mac
Ad-hoc: register the device → create signing material → build and install the IPA.
Free Apple ID: build
unsigned-ipaand sideload with Sideloadly / AltStore.Simulator: needs macOS; with a remote Mac use
mac_run_on_simulator+mac_screenshot.
Tools
Group | Tools |
status |
|
project |
|
CI |
|
signing / ASC |
|
remote Mac |
|
USB device |
|
prompts |
|
Costs and limits
GitHub-hosted macOS minutes are free on public repos; private repos consume your Actions minutes at a 10× rate. A clean Flutter iOS build takes roughly 8–20 minutes.
Publishing to TestFlight/App Store requires a paid Apple Developer Program membership.
Apple caps the number of distribution certificates;
signing_quick_setupreuses the one it created, andasc_revoke_certificatefrees a slot.Windows USB access needs Apple's driver; Linux needs
usbmuxd.
Security
Tokens and keys are read from env/config only; nothing is sent anywhere except GitHub and Apple APIs (and your own Mac over SSH).
GitHub secrets are encrypted locally with the repo's public key before upload.
The CI workflow creates a throwaway keychain per run and deletes it afterwards.
Development
python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]" && pytest
npx @modelcontextprotocol/inspector flutter-ios-bridge-mcp # poke at the toolsMIT © Guruprasath J
Available Tools
44 toolsasc_download_profileC
Download a provisioning profile (.mobileprovision) by id.
Inputs: profile_id (required), dest_path.
asc_enable_capabilityA
Enable a capability on a bundle id, e.g. PUSH_NOTIFICATIONS, ASSOCIATED_DOMAINS, APPLE_ID_AUTH (Sign in with Apple), IN_APP_PURCHASE, HEALTHKIT, NFC_TAG_READING, APP_GROUPS, ICLOUD. Recreate profiles afterwards (signing_quick_setup) so they carry the new entitlement.
Inputs: capability (required), identifier (required).
asc_listC
List App Store Connect / Developer Portal resources.
Inputs: resource (required). Returns: result
asc_register_bundle_idB
Register an explicit App ID (bundle identifier) in the Apple Developer portal.
Inputs: identifier (required), name.
asc_register_deviceA
Register an iPhone for ad-hoc/development builds. With no udid, uses the USB-connected device (needs pymobiledevice3).
Inputs: name, udid.
asc_revoke_certificateA
Revoke a signing certificate (frees a slot when Apple's certificate limit is hit). Profiles using it become invalid; apps already on the App Store are unaffected.
Inputs: certificate_id (required).
bridge_statusB
Show which backends (GitHub CI, App Store Connect, remote Mac, USB device) are configured and what is missing.
Inputs: project_path.
ci_cancel_runC
Cancel a running workflow run.
Inputs: run_id (required), repo, project_path.
ci_download_artifactsA
Download and unzip a run's build outputs (IPA / simulator .app.zip). Default destination: /build/ios-bridge/<run_id>/.
Inputs: run_id (required), repo, dest_dir, project_path.
ci_generate_workflowB
Write .github/workflows/flutter-ios-bridge.yml (+ a signing helper script) into the repo. The workflow builds on a GitHub macOS runner: simulator .app, unsigned IPA, or signed IPA with optional TestFlight upload. By default pins the same Flutter version you have installed locally.
Inputs: runner, overwrite, project_path, flutter_version, +1 more.
ci_get_logsB
Fetch the job logs of a run and extract the Xcode/CocoaPods/Flutter error lines plus the log tail.
Inputs: run_id (required), repo, tail_lines, only_failed, +1 more.
ci_list_runsC
List recent runs of the iOS workflow.
Inputs: repo, limit, project_path. Returns: result
ci_set_signing_secretsA
Upload signing material to the repo's GitHub Actions secrets (encrypted client-side): IOS_P12_BASE64, IOS_P12_PASSWORD, IOS_PROFILE_BASE64 and, if include_asc_key, ASC_KEY_ID / ASC_ISSUER_ID / ASC_PRIVATE_KEY for TestFlight uploads. Works with a .p12 exported from anywhere, not only signing_quick_setup.
Inputs: p12_path (required), p12_password (required), mobileprovision_path (required), repo, +2 more.
ci_trigger_buildA
Start an iOS build on GitHub Actions. Builds what is pushed to ref (default branch). Returns the run id.
signed-ipa needs signing secrets (signing_quick_setup); testflight=true also needs ASC secrets.
Inputs: ref, repo, build_name, build_type, +4 more.
ci_wait_for_runA
Wait (up to timeout_seconds) for a run to finish; returns status and per-step results. Call repeatedly for long builds (a clean iOS build usually takes 8–20 minutes).
Inputs: run_id (required), repo, poll_seconds, project_path, +1 more.
device_infoC
Model, iOS version and UDID of a connected device.
Inputs: udid.
device_install_appA
Install a signed .ipa (ad-hoc or development profile that includes this device) on a connected iPhone.
Inputs: ipa_path (required), udid.
device_listA
List iPhones/iPads connected over USB/Wi-Fi to this Windows/Linux machine.
Inputs: no named parameters. Returns: result
device_list_appsC
List user-installed apps on the connected device.
Inputs: udid. Returns: result
device_syslogA
Capture the device syslog for N seconds (max 120), optionally filtered by text or process name. Launch the app on the phone while this runs to catch crash reasons.
Inputs: udid, match, process, seconds.
device_uninstall_appC
Uninstall an app from the connected device.
Inputs: bundle_id (required), udid.
ios_doctorA
Audit the ios/ side of a Flutter project without Xcode: bundle id, Info.plist usage strings required by the plugins in pubspec.yaml, deployment target vs Podfile, App Store icon (size/alpha), launch screen, privacy manifest, Firebase config, entitlements. Returns issues sorted by severity with fixes.
Inputs: project_path.
ios_get_build_settingsA
Read key Xcode build settings from project.pbxproj (bundle ids, deployment target, team, signing style...) plus the Podfile platform.
Inputs: project_path.
ios_get_info_plistB
Read ios/Runner/Info.plist (optionally only the given keys).
Inputs: keys, project_path.
ios_remove_info_plist_keyA
Delete a key from ios/Runner/Info.plist.
Inputs: key (required), project_path.
ios_set_bundle_identifierC
Change the iOS bundle identifier (Runner and RunnerTests) in project.pbxproj.
Inputs: bundle_id (required), project_path.
ios_set_deployment_targetB
Set the minimum iOS version consistently in project.pbxproj, Podfile and AppFrameworkInfo.plist.
Inputs: version, project_path.
ios_set_info_plist_valueB
Set a key in ios/Runner/Info.plist. value_type: auto|string|bool|int|real|array|dict|json. Example: key='NSCameraUsageDescription', value='Used to scan documents'.
Inputs: key (required), value (required), value_type, project_path.
mac_boot_simulatorB
Boot a simulator (default: an already-booted one or the newest iPhone).
Inputs: device_name_or_udid.
mac_buildA
Build the project on the remote Mac (syncs first by default). Returns ok + the tail of the build output.
Inputs: mode, extra_args, sync_first, project_path.
mac_doctorA
Check the remote Mac: macOS, Xcode, Flutter, CocoaPods and installed simulator runtimes.
Inputs: no named parameters.
mac_execC
Run a shell command on the remote Mac (login shell). in_project=true runs it inside the synced project dir,
e.g. cd ios && pod install --repo-update or flutter test.
Inputs: command (required), in_project, project_path, timeout_seconds.
mac_fetch_fileB
Download a file from the remote Mac (relative paths resolve inside the synced project), e.g. build/ios/ipa/app.ipa.
Inputs: local_dest (required), remote_path (required), project_path.
mac_install_simulator_appB
Install a zipped simulator .app (e.g. from ci_download_artifacts) on the remote Mac's simulator and launch it.
Inputs: app_zip_path (required), bundle_id, device_name_or_udid.
mac_list_simulatorsB
List iOS simulators on the remote Mac.
Inputs: only_booted. Returns: result
mac_open_urlC
Open a URL / deep link / universal link in the simulator.
Inputs: url (required), device_name_or_udid.
mac_run_on_simulatorC
Sync, build for the simulator, install and launch the app on the remote Mac's iOS Simulator.
Inputs: rebuild, sync_first, project_path, device_name_or_udid.
mac_screenshotB
Take a screenshot of the iOS Simulator on the remote Mac and return it as an image.
Inputs: device_name_or_udid.
mac_simulator_logsC
Recent unified-log lines from the app running in the simulator (Flutter print/debugPrint show up here).
Inputs: grep, process, seconds, device_name_or_udid.
mac_sync_projectA
Upload the Flutter project to the remote Mac (skips build/, .dart_tool/, Pods/, .git). clean=true wipes the remote copy first.
Inputs: clean, project_path.
signing_inspectA
Inspect a .mobileprovision (name, team, bundle id, kind, devices, expiry, certs) or a .p12 (needs password).
Inputs: path (required), p12_password.
signing_quick_setupA
One-shot iOS code signing from Windows/Linux: registers the bundle id, creates (or reuses) an Apple certificate from a locally generated CSR, creates a provisioning profile, saves .p12/.mobileprovision under ~/.flutter-ios-bridge/signing, and (push_to_github) uploads them as GitHub secrets for signed CI builds. bundle_id defaults to the project's. ad-hoc/development include all registered devices.
Inputs: repo, app_name, bundle_id, p12_password, +5 more.
testflight_buildsC
List recent TestFlight/App Store builds for the app with their processing state.
Inputs: limit, bundle_id, project_path.
testflight_distributeC
Answer export compliance for a processed build (uses_non_exempt_encryption; None = leave as is) and add it to TestFlight beta groups (ids from testflight_builds).
Inputs: build_id (required), beta_group_ids, uses_non_exempt_encryption.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 44 tools
Despite the size, every tool is scoped to a distinct backend/resource/action: project config, CI, signing, ASC/TestFlight, remote Mac, or USB device. The prefix plus explicit target (e.g. mac_build vs ci_trigger_build) makes misselection unlikely.
Tools consistently use lowercase snake_case with backend prefixes and mostly verb_object forms. A few noun-style names (`bridge_status`, `ios_doctor`, `testflight_builds`) break the strict verb_noun pattern, but the convention is otherwise predictable.
44 tools is well above the 25+ threshold and creates a large discovery burden for an agent. The multi-backend scope explains the count, but splitting into smaller per-backend servers would make the surface far more manageable.
The surface covers the full Flutter iOS bridge lifecycle: audit/config, CI workflow, signing/ASC resources, TestFlight distribution, remote Mac build/run, and USB device operations. Minor gaps exist, such as no direct provisioning-profile deletion and no App Store Connect app-creation step, but core workflows have no dead ends.
Maintenance
Related MCP Connectors
Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
Ship apps for iPhone, iPad, Mac, Apple TV, Vision Pro and Android to the App Store and Google Play
Rent and manage dedicated Apple Silicon Macs for iOS builds and CI/CD from your AI agent.
Related MCP Servers
- AlicenseAqualityCmaintenanceBuild, sign, and publish iOS and Android apps through AI agents. Integrates Codemagic CI/CD, App Store Connect, and Google Play in one server.6313 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated management of iOS apps, builds, TestFlight beta testing, and user access control through Apple's App Store Connect API.20 npmMIT
- AlicenseAqualityCmaintenanceEnables coding agents to build, test, archive, and run iOS apps on a remote Mac fleet from any environment, with XcodeBuildMCP-compatible tools and live simulator access.1157 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables TestFlight deployment and App Store Connect build lookup for iOS projects, including project registration, rsync/ssh deployment, and retrieving build numbers.MIT