Model Context Protocol

Share iOS & Android builds from your AI assistant

The IPALinked MCP tool connects Cursor, Claude, Codex, Copilot, Windsurf and Zed to IPALinked. Share an .ipa or .apk in plain language and get an install link your testers and developers open to install the app on their real devices. Free, no account, no token.

?
Quick answer

To share a build from your AI editor: add the IPALinked MCP tool (npx -y ipalinked-mcp) to Cursor, Claude, Codex, Copilot, Windsurf or Zed, then say “share MyApp.ipa on IPALinked.” You get back an install link (with a QR code) that your testers and developers open to install the app on their real devices — free, no account, links expire in 7 days.

What it is

The IPALinked MCP tool plugs IPALinked into your AI coding assistant using the Model Context Protocol — the open standard that lets tools like Cursor, Claude and Copilot take real actions, not just chat. Once it's added, your assistant can upload a build to IPALinked and hand you back an install link, or read a build's details, entirely from natural-language requests.

That link is the whole point: you send it to your testers, clients or fellow developers, and they open it on a real iPhone, iPad or Android device to install the app directly — no App Store, no Play Store. Signed iOS builds install over the air straight from Safari. It stays anonymous and free, just like the website: no signup, 500MB limit, links auto-expire after 7 days.

Works with your editor

Pick your tool for the exact config and where it goes. Every option runs the same free package — you only need Node 18+.


        

Tip: since you're already in an AI editor, you can skip the file entirely — just paste Add the ipalinked-mcp tool to my MCP config into the chat and your assistant will set it up for you. Then restart the editor.

Try these prompts

Talk to your assistant naturally — it picks the right action.

“Share ./build/MyApp.ipa on IPALinked and give me the install link”Uploads the IPA and returns a link testers open to install on their iPhone/iPad
“Share MyApp.apk with a password”Returns a password-protected install link for your Android testers
“Analyze ./MyApp.ipa — is it ad-hoc or enterprise, and when does it expire?”Reads the build locally; nothing is uploaded
“Get an install link for this build to send my client”Returns a link + QR your client opens to install on a real device

What it can do

You don't need to memorize these — just prompt naturally.

Share a build

Upload an iOS (.ipa) or Android (.apk) build and get an install link your testers and developers open to install it on real devices. Optional password.

Analyze a build

Read a build's details locally — bundle/package id, version, SDK/OS, iOS provisioning type & expiry. Nothing is uploaded.

How it works

When you ask to share a build, the tool reads the file from your machine and uploads it to IPALinked over HTTPS, then returns the install link and expiry. When you ask to analyze, it inspects the build locally — unzipping the .ipa/.apk and reading its manifest — and reports the details without sending the file anywhere. It runs on demand through npx, so there's nothing to install permanently and nothing to keep updated.

npx -y ipalinked-mcp

Free forever · no account or token · anonymous · 500MB · install links expire in 7 days. For a signed iOS build to install over the air, it must be ad-hoc (with the device UDID) or enterprise-signed.

Learn more

Guides that go deeper on MCP and sharing builds for real-device testing.