About AppForShare
AppForShare MCP serves teams managing iOS and Android test builds and store releases. AI clients can inspect builds, install links, store readiness, release status, and reviews, as well as upload or manage builds with confirmation for changes.
Key features
- 01Upload iOS and Android builds
- 02Find builds and install links
- 03Read store readiness checks and fixes
- 04Track store releases and reviews
- 05Change channels or delete builds
Use cases
- 01Give testers app installation links
- 02Check readiness for store submission
- 03Review App Store or Google Play release progress
- 04Manage build channels or remove builds
MCP support
The MCP server gives clients tools for build uploads and queries, store readiness, release status, and reviews. It can run locally or use the hosted endpoint, which supports OAuth or a Bearer token.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://appforshare.io/api/mcpclaude mcp add --transport http io-appforshare-appforshare https://appforshare.io/api/mcp{"mcpServers":{"io-appforshare-appforshare":{"type":"http","url":"https://appforshare.io/api/mcp"}}}Open in Cursor{"servers":{"io-appforshare-appforshare":{"type":"http","url":"https://appforshare.io/api/mcp"}}}Open in VS Code{"mcpServers":{"io-appforshare-appforshare":{"type":"http","url":"https://appforshare.io/api/mcp"}}}{"mcpServers":{"io-appforshare-appforshare":{"serverUrl":"https://appforshare.io/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEappforshare-mcp
MCP server for AppForShare. Lets Claude Code, Cursor, Codex, VS Code, Gemini CLI and other MCP clients upload iOS and Android builds, find install links, read the store readiness check and follow App Store and Google Play releases and reviews.
Needs an AppForShare API token (Pro and Team), from https://appforshare.io/dashboard/settings, and Node 18 or newer.
{
"mcpServers": {
"appforshare": {
"command": "npx",
"args": ["-y", "appforshare-mcp"],
"env": { "APPFORSHARE_TOKEN": "afs_your_token" }
}
}
}
Claude Code:
claude mcp add appforshare --env APPFORSHARE_TOKEN=afs_your_token -- npx -y appforshare-mcp
No local uploads needed? Use the hosted server instead: https://appforshare.io/api/mcp, with OAuth (Claude, ChatGPT and other clients that sign in) or the header Authorization: Bearer afs_your_token. Setup for each client: https://appforshare.io/docs/mcp
Tools
| Tool | What it does |
|---|---|
upload_build | Upload a local .ipa, .apk or .aab (release notes, channel). Returns the install link and readiness result. |
list_builds, latest_build | Builds with install links, filtered by platform, app, project or channel. |
build_info | One build with every store readiness finding and its fix. |
list_projects, whoami | Projects in the account; account, plan and role of the token. |
release_status, list_reviews | App Store and Google Play release status and reviews. Read only. |
promote_build, delete_build | Change a channel or delete a build. Developer role and confirm: true required. |
Environment: APPFORSHARE_TOKEN (required), APPFORSHARE_API (default https://appforshare.io).
Agent skill
skills/appforshare is an agent skill (a folder with a SKILL.md) that tells Claude Code,
Codex and other agents that load skills when to upload, which tools and CLI flags to use, how to read the store
readiness result, and which actions need the person's confirmation. It points to the hosted OAuth server first and
to npx appforshare as the fallback. Copy the folder to ~/.claude/skills/ (Claude Code, all projects),
.claude/skills/ in a project, or ~/.agents/skills/ (Codex). Free to use; the tools it calls need Pro or Team.
MIT licence.
Registry
Listed in the official MCP Registry as io.appforshare/appforshare.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.