Docs
MCP server for AI coding tools
Ask your coding assistant to "share this build with the testers", "what is the install link of the newest Android beta" or "is version 2.4 still in App Review", and it answers from your AppForShare account. The server speaks the Model Context Protocol, so it works in Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex, Gemini CLI and other MCP clients. Pro and Team.
Server URL: https://appforshare.io/api/mcp
Auth: sign in from your AI tool (OAuth), or Authorization: Bearer afs_... with an API token from Settings
npm: npx -y appforshare-mcp with APPFORSHARE_TOKEN set
Claude (web and desktop)
Settings, Connectors, Add custom connector. Paste the server URL and press Connect. AppForShare opens: sign in, pick a workspace and press Allow.
https://appforshare.io/api/mcpChatGPT
On chatgpt.com open Settings, Apps and Connectors, Advanced settings and turn on Developer mode (paid plans; on Business and Enterprise an admin may need to allow it). Go back, press Create, name it AppForShare, paste the server URL, keep Authentication on OAuth, tick that you trust the app and press Create. AppForShare opens: sign in, pick a workspace and press Allow. In a chat, pick AppForShare from the tools menu.
https://appforshare.io/api/mcpClaude Code
One command, added for your user so it works in every project. Then run /mcp, pick appforshare and sign in when the browser opens. To use an API token instead, add --header "Authorization: Bearer afs_your_token".
claude mcp add --transport http --scope user appforshare https://appforshare.io/api/mcpCursor
Add it to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in one project. Cursor shows a Connect button that opens the AppForShare sign in. A "headers" entry with an API token works too.
{
"mcpServers": {
"appforshare": {
"url": "https://appforshare.io/api/mcp"
}
}
}VS Code (GitHub Copilot)
Add it to .vscode/mcp.json, or run "MCP: Add Server" from the command palette. VS Code asks to sign in to AppForShare the first time a tool runs.
{
"servers": {
"appforshare": {
"type": "http",
"url": "https://appforshare.io/api/mcp"
}
}
}Codex CLI
Add it to ~/.codex/config.toml. This uses the npm package, which also adds upload_build.
[mcp_servers.appforshare]
command = "npx"
args = ["-y", "appforshare-mcp"]
env = { APPFORSHARE_TOKEN = "afs_your_token" }Gemini CLI
Add it to ~/.gemini/settings.json.
{
"mcpServers": {
"appforshare": {
"httpUrl": "https://appforshare.io/api/mcp",
"headers": { "Authorization": "Bearer afs_your_token" }
}
}
}Any client, with local uploads
The appforshare-mcp npm package runs on your computer over stdio. It passes every tool through to AppForShare and adds upload_build, which reads an .ipa, .apk or .aab from your disk, and check_local_build, which checks one there without uploading it. Needs Node 18 or newer.
{
"mcpServers": {
"appforshare": {
"command": "npx",
"args": ["-y", "appforshare-mcp"],
"env": { "APPFORSHARE_TOKEN": "afs_your_token" }
}
}
}Tools
- upload_build
- Upload an .ipa, .apk or .aab from your computer, with release notes and a channel. Returns the install link and the store readiness result. npm package only.
- check_local_build
- Check an .ipa, .apk or .aab on your computer without uploading it: the store readiness check, why a phone would refuse it and the security scan counts (the findings with a Pro or Team token). The file never leaves your computer. npm package only. Read only.
- create_upload_linkChanges data
- For chat assistants that cannot read your files: a one time link you open in any browser to drop an .ipa, .apk or .aab. It works once, for 30 minutes, without signing in, and the build goes into the workspace you connected. Pro and Team, Developer role.
- upload_from_urlChanges data
- Upload a build from a public https link, such as a GitHub release asset or a signed CI artifact link. The size is checked first; http, private and local addresses are refused, also after a redirect. Pro and Team, Developer role.
- check_upload
- The result of create_upload_link or upload_from_url: waiting, uploading, processing, ready with the install link and store readiness, or failed with the reason. Only in the workspace that started it. Read only.
- list_builds
- Recent builds with install link, version, size, installs, readiness status and channels. Filter by platform, app, project or channel.
- latest_build
- The newest build that matches, for example the newest Android build in the beta channel.
- build_info
- One build with its release notes, every store readiness finding with a fix, and the verified publisher line its install page shows (Pro and Team).
- get_security_scan
- Security scan of one build: hardcoded keys (masked), Android and iOS findings and library versions with a known advisory, each with a level, an OWASP MASVS category and a fix. Findings and hints, not a penetration test. Read only. Pro and Team.
- get_install_badge
- Download button for a README or docs page: Markdown and HTML of the Install test build badge, dark and light, for a build or a channel. A channel badge shows the version of its newest build. Read only. Free and up for builds, Pro and Team for channels.
- build_install_issues
- Why testers' phones may refuse a build: App Store signed or unsigned, profile expired or ending soon, no devices in the profile, Developer Mode, enterprise trust, the .aab test key, and the minimum iOS or Android version. Pass a tester's UDID to check whether the build includes that device. Read only.
- build_installs
- Who installed a build, newest first (up to 200): device, OS version, model, country and the tester when known, with totals by device and country. Read only.
- email_build_linkChanges data
- Email a build's install link to up to 5 addresses, one plain mail each with no tracking. An address that already got this build is skipped. Not for private projects (add testers there). Pro and Team, Developer role, confirm: true.
- set_channel_addressChanges data
- Give a channel its own address, for example /c/acme-beta. The old address redirects for 30 days and the in-app update check on it keeps working. Pro and Team, Developer role, confirm: true.
- test_plan
- The AI test plan of a build: tasks ordered by risk with steps, why each one is there and which ones the team ticked. generate: true writes a new one (1 AI action, Developer role).
- export_test_plan
- The AI test plan of a build as a file other tools run: format firebase gives Firebase App Testing agent test cases (Android only, in preview), maestro a Maestro starter flow with a screenshot and an assertWithAI check per task. Needs a plan first. Read only. Pro and Team.
- github_build_run
- GitHub Actions builds AppForShare started, newest first. With a run id: that run and, for a failed one, the AI explanation of the likely cause and the fix steps, written from the failed job's log with secrets taken out. explain: true makes one when there is none (1 AI action, Developer role). It never changes code or the repository. Pro and Team.
- list_feedback
- Feedback testers sent from install pages and the in-app feedback link, and on Team the TestFlight screenshot and crash feedback read from App Store Connect, newest first: the message, source, device, OS, build and how many screenshots or recordings came with it, with a dashboard link to open them. Filter by build, status, blockers or source (page, app, testflight).
- list_testers
- Testers of the workspace with their projects and groups, optionally only those of one project or one group. Team.
- list_tester_groups
- Tester groups with member counts and the projects each group can install. Team.
- add_testersChanges data
- Add email addresses as testers, optionally to a project and to tester groups; new testers get an invite unless notify is false. Team, Developer role, confirm: true.
- remove_testersChanges data
- With a project: take away the access given by hand there (access through a group stays). Without: remove the testers from the workspace. Team, Developer role, confirm: true.
- share_build_with_testersChanges data
- Give tester groups and testers the project of an uploaded build and email them its install link. Team, Developer role, confirm: true.
- task_from_feedbackChanges data
- Add a task from a feedback report to its project's board, linked to the build. Team, Developer role, confirm: true.
- recent_activity
- What happened in the workspace, newest first, with who did it. Optional project and kind. Team.
- send_feedback_to_trackerChanges data
- Make a Linear or Jira issue from a feedback report, with its screenshots. Needs a connected tracker, confirm: true and the Developer role.
- reply_to_feedbackChanges data
- Reply to a feedback report: the tester gets one email in the language of their install page and can answer once there. Only reports with a tester email. Team, Developer role, confirm: true.
- resolve_feedback
- Mark a feedback report resolved, or open it again. Needs confirm: true and the Developer role.
- list_projects
- Projects in the account with their ids.
- whoami
- The account, plan and role the connection works in.
- find_app_steps
- Where to click in AppForShare for a task: the page, the exact button names and short steps, and whether your plan and team role allow it. Read only.
- release_status
- App Store versions and review state, recent TestFlight builds, Google Play tracks and rollout, and recent changes. Read only.
- release_defaults
- Saved release defaults of the shared store apps: What's New per language, App Store phased release, Google Play track and rollout. Read only. Pro and Team.
- set_release_defaultsChanges data
- Save the release defaults of one store app. Only saved in AppForShare, never sent to a store. Pro and Team, Developer role, confirm: true.
- rollout_plan
- Scheduled Google Play rollout plans of an app: steps, which are done, the next step time, and why a plan is paused or halted. Read only: plans are set, paused and stopped by a person. Team.
- store_upload_status
- Whether a build can go to TestFlight or a Google Play track and why not, and every send so far with the store answer. Read only: a person sends the build from the build page or the CLI. Pro and Team.
- list_reviews
- App Store and Google Play reviews that need a reply, or all of them. Read only: replies are posted by a person in the dashboard.
- promote_buildChanges data
- Put a build into a channel so its stable link opens it. Developer role, and the assistant must pass confirm: true.
- release_checklist
- The release checklist of a build with its ticks, named approvals, open release blockers and whether the gated channel takes it. Read only: an AI tool never gives an approval. Team.
- release_overview
- The release page of a version: builds, readiness, channels, checklist and approvals, store review and rollout, Android vitals (crash and ANR rate per version code, Team, read only), and a timeline. Without a version it lists the versions. Team; Pro without the checklist and vitals.
- tick_release_stepChanges data
- Tick or untick one release checklist step on a build. Developer role, and the assistant must pass confirm: true.
- list_build_links
- The extra share links of a build with their label, URL, installs, password yes or no, stop date, install cap and state. Read only.
- add_build_linkChanges data
- Add another share link to a build, for example one per client, with its own label, password, start time, stop date and install cap. Pro (3 per build) and Team (20), Developer role, confirm: true.
- remove_build_linkChanges data
- Turn off one extra share link; the build and its other links keep working. Developer role, confirm: true.
- list_access_codes
- The per tester access codes of a build page or an extra link: label, devices used of the allowed count and state (active, all devices used, revoked). The codes themselves are never shown again. Team. Read only.
- create_access_codeChanges data
- Make a one off access code for a build page or an extra link, with a label and a device count (1 to 50). A tester types it instead of the shared password. The code comes back once. Team, Owner or Admin, confirm: true.
- revoke_access_codeChanges data
- Turn off one access code; installs made with it stay, and the password and other codes keep working. Owner or Admin, confirm: true.
- retire_buildChanges data
- Retire a broken test build: its link takes no installs and sends testers to the newest build, channels skip it, the update check reports it. Optional note; undo brings it back. Pro and Team, Developer role, confirm: true.
- set_link_controlsChanges data
- Pause or resume a build's install link, set a start time (testers see when it opens), a stop date or an install limit. Developer role, and the assistant must pass confirm: true.
- set_testflight_linkChanges data
- Add or remove the TestFlight public link of a channel, so iPhone visitors go to TestFlight and Android visitors get the APK. Developer role, and the assistant must pass confirm: true.
- channel_followers
- How many people follow a channel by email: confirmed and pending counts, the plan cap and masked addresses. Read only; removing a follower stays in the dashboard and the CLI. Pro and Team.
- delete_buildChanges data
- Delete a build; it can be restored from the dashboard for 7 days. Developer role, and the assistant must pass confirm: true.
- restore_buildChanges data
- Bring back a build deleted in the last 7 days; without a build it lists what can be restored. Developer role, and the assistant must pass confirm: true.
- resign_buildChanges data
- Re-sign an iOS build with a new provisioning profile from the connected Apple account; the result is a new build and the original stays as it was. Without confirm it only checks the profiles, certificate and devices. Developer role, and the assistant must pass confirm: true. Pro and Team.
- list_webhooks
- Webhooks of the workspace with their events, failures and last error, and the recent deliveries of one. Never a webhook URL or secret: webhooks are added in the dashboard. Read only. Owner or Admin.
Agent skill
The AppForShare skill is a folder with a SKILL.md file that tells Claude Code, Codex and other agents that load skills when to upload a build, which tools and CLI flags to use, how to read the store readiness result (ready, review, blocked), how channels, extra share links and retire work, and which actions need your yes first: anything that sends mail or changes who can install. It uses the hosted server above (sign in, no token to paste) and falls back to npx appforshare. The skill is free; the tools it calls need Pro or Team.
Claude Code
Copy the folder to ~/.claude/skills/ for all projects, or to .claude/skills/ in one project.
git clone --depth 1 https://github.com/appforshare/appforshare-mcp
mkdir -p ~/.claude/skills
cp -r appforshare-mcp/skills/appforshare ~/.claude/skills/Codex
Codex reads skills from ~/.agents/skills/, or .agents/skills/ in a repository.
mkdir -p ~/.agents/skills
cp -r appforshare-mcp/skills/appforshare ~/.agents/skills/Other agents that load SKILL.md files: copy the same folder to their skills folder. Source: github.com/appforshare/appforshare-mcp.
Questions
- Which plan do I need?
- Pro or Team. You can sign in from your AI tool (OAuth), or use the same API token as the CLI and GitHub Action, made under Dashboard, Settings, API tokens. The tester tools need Team.
- Can I use it next to the Firebase MCP server?
- Yes. MCP clients take several servers at once, so an assistant can use Firebase's tools for your Firebase project and these for your AppForShare builds, testers and feedback.
- What happens when I sign in from an AI tool?
- AppForShare shows which app is asking, you pick the workspace it may use and press Allow. The app gets an access token that lasts an hour and renews itself; it never sees your password. Disconnect it under Settings, Connected apps and it stops at once.
- Can the assistant submit my app or change my store listing?
- No. Store tools in the MCP server only read release status and reviews. Sending for App Store review, listing changes and review replies stay in the dashboard, where a person presses the button.
- What stops an assistant from deleting builds?
- Deleting and moving builds between channels need the Developer role and an explicit confirm: true in the call, which assistants are told to set only after you agree. Most clients also ask you before running any tool. A deleted build can be restored for 7 days.
- Does the app or token get access to everything in my account?
- No. It works in one workspace (the one you picked when signing in, or the one the token was made in), with your role there. A Viewer can only read. A read only token sees only the read only tools, and an upload token adds the upload tools. Revoke a token or disconnect an app under Settings at any time and it stops at once.
- How do I upload from Claude or ChatGPT in the browser?
- Ask for an upload link. The assistant calls create_upload_link and gives you a link that works once, for 30 minutes. Open it on any device, drop the .ipa, .apk or .aab, and the assistant reads the install link with check_upload. If the build is already online at a public https address, such as a release asset, it can use upload_from_url instead.
- Can an assistant make tokens or webhooks?
- No. No tool makes API tokens or adds webhooks, so those secrets stay out of chats. An assistant can list webhooks and their deliveries without the URLs.
Prefer plain commands? The same token works with the CLI, GitHub Action and Fastlane plugin.