Share builds and check releases without leaving your AI coding tool
Pro and Team
If you write code with an AI assistant, the last step of a change is usually "build it and send it to the testers". With the AppForShare MCP server, the assistant can do that step too: upload the .ipa or .apk it just built, return the install link and tell you what the store readiness check found.
It also answers the questions you would otherwise open three dashboards for: which build is in the beta channel, is version 2.4 still in App Review, what did the last one star reviews say.
Example
In Claude Code
- upload_buildInstall link ready
- build_infoReadiness: review, 1 finding
- release_status2.4 waiting for review
- delete_buildAsks you first
Made for
- Developers who build in Claude Code, Cursor, Codex or VS Code with Copilot
- Release managers who ask Claude about builds and App Review from the chat
- Small teams that want release questions answered in the editor
- Anyone who already uses the AppForShare CLI and wants the same from an assistant
What it ends
- Leaving the editor to upload a build and copy its link
- Opening App Store Connect to see whether review has started
- Pasting the readiness report into the chat by hand
How it works
Step 1
Add the server
Paste appforshare.io/api/mcp as a custom connector in Claude, run one command in Claude Code, or add a few lines of JSON in Cursor or VS Code. The setup page has each one.
Step 2
Sign in and approve
Your tool opens AppForShare. Pick the workspace it may use and press Allow. Scripts and tools without sign in can use an API token instead.
Step 3
Ask
For example: "upload build/app-release.apk to the beta channel and give me the link" or "what does the readiness check say about the newest iOS build".
What the assistant can and cannot do
It can upload builds (through the npm package, which reads the file from your computer), list builds and projects, find the newest build by platform, app or channel, read the store readiness check, and read release status and reviews of the apps you shared from App Store Connect and Google Play.
Moving a build into a channel and deleting a build need the Developer role and an explicit confirmation in the call. Sending a version for App Store review, editing a listing and replying to reviews are not available to the assistant: a person does those in the dashboard.
Testers, feedback and test plans
On Team the assistant can list testers and tester groups, add or remove testers and share a build with groups and people (list_testers, list_tester_groups, add_testers, remove_testers, share_build_with_testers), each change after you confirm. It can read tester feedback, mark a report resolved, send it to Linear or Jira, or make a task from it.
test_plan reads the AI test plan of a build, and export_test_plan returns it as Firebase App Testing agent YAML or a Maestro starter flow (Pro and Team).
Installs and install problems
build_install_issues answers "why can't my tester install": signing, profile end date, devices in the profile, Developer Mode, enterprise trust and the minimum OS, and with the tester's UDID whether the device is in the build. build_installs lists who installed a build. email_build_link emails the install link to up to 5 addresses and set_channel_address gives a channel its own address, each after you confirm.
Good to know
- The hosted server cannot read files on your computer, so uploads need the appforshare-mcp npm package (Node 18 or newer).
- Store tools only read. Nothing in App Store Connect or Google Play is changed from the MCP server.
- A connection works in one workspace, with your role there. Disconnect an app or revoke a token under Settings and it stops at once.
Questions
- Which AI tools work with it?
- Any client that speaks the Model Context Protocol, including Claude, Claude Code, Cursor, Codex, VS Code with GitHub Copilot and Gemini CLI.
- I already use the Firebase MCP server. Can I use both?
- Yes. MCP clients take several servers at once. The Firebase server covers Firebase projects; this one covers your AppForShare builds, testers, feedback, release checklist and store status.
- Do I have to paste a token?
- No. Tools that support MCP sign in (Claude, Claude Code, Cursor, VS Code and others) open AppForShare, you approve once and they renew access on their own. An API token is still there for scripts and tools without sign in.
- Does it use AI actions from my plan?
- No, with one exception: asking test_plan to write a new test plan uses 1 AI action, like the button on the build page. Everything else runs in your own tool; AppForShare only answers its requests.
- Which plan do I need?
- Pro or Team, the same plans that include API tokens for CI.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications