Which plan do I need?

Pro or Team. The MCP server uses the same API token as the CLI and GitHub Action, made under Dashboard, Settings, API tokens.

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 token give access to everything in my account?

It works in the account it was made in (your own, or the team you were in), with your role there. Revoke it under Settings at any time and it stops at once.

AppForShare Get a token

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 Code, Cursor, Codex, VS Code, Gemini CLI and other MCP clients. Pro and Team.

Server URL: https://appforshare.io/api/mcp

Auth: Authorization: Bearer afs_..., an API token from Settings

npm: npx -y appforshare-mcp with APPFORSHARE_TOKEN set

Claude Code

One command. The server is added for your user, so it works in every project.

claude mcp add --transport http appforshare https://appforshare.io/api/mcp \
  --header "Authorization: Bearer afs_your_token"

Cursor

Add it to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in one project.

{
  "mcpServers": {
    "appforshare": {
      "url": "https://appforshare.io/api/mcp",
      "headers": { "Authorization": "Bearer afs_your_token" }
    }
  }
}

VS Code (GitHub Copilot)

Add it to .vscode/mcp.json, or run "MCP: Add Server" from the command palette.

{
  "servers": {
    "appforshare": {
      "type": "http",
      "url": "https://appforshare.io/api/mcp",
      "headers": { "Authorization": "Bearer afs_your_token" }
    }
  }
}

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 or .apk from your disk. 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 or .apk from your computer, with release notes and a channel. Returns the install link and the store readiness result. npm package 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 and every store readiness finding, each with a fix.
list_projects: Projects in the account with their ids.
whoami: The account, plan and role the token works in.
release_status: App Store versions and review state, recent TestFlight builds, Google Play tracks and rollout, and recent changes. Read only.
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.
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.

Questions

Which plan do I need?: Pro or Team. The MCP server uses the same API token as the CLI and GitHub Action, made under Dashboard, Settings, API tokens.
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 token give access to everything in my account?: It works in the account it was made in (your own, or the team you were in), with your role there. Revoke it under Settings at any time and it stops at once.

Prefer plain commands? The same token works with the CLI, GitHub Action and Fastlane plugin.