AppForShareCreate a free account

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
Hosted at appforshare.io/api/mcp, or run locally with npx appforshare-mcp.

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

  1. 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.

  2. 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.

  3. 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

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