Skip to main content
Glama
Sign In
appstore-connect-mcp

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Write] Upload a build to App Store Connect

asc_build_upload

Uploads iOS, tvOS, visionOS, and macOS build binaries (.ipa/.pkg) to App Store Connect. Handles chunked transfer and MD5 checksum verification.

Instructions

Write. Uploads a build binary (.ipa for iOS/tvOS/visionOS, .pkg for macOS) to App Store Connect: creates the upload, sends the file in Apple's required chunks, and commits it with an MD5 checksum. Processing then continues on Apple's servers — poll asc_build_upload_status, then asc_builds_list, to see it finish and become a usable build.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>",
      "filePath": "<filePath>",
      "cfBundleShortVersionString": "<cfBundleShortVersionString>",
      "cfBundleVersion": "<cfBundleVersion>"
    },
    "name": "asc_build_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
filePathYesAbsolute local path to the .ipa or .pkg file
platformNoIOS
cfBundleVersionYesBuild number, e.g. "12"
cfBundleShortVersionStringYesMarketing version, e.g. "1.1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It explains the multi-step process (create upload, chunked send, MD5 checksum) and that processing continues on Apple's servers, which is valuable context. However, it does not mention permissions, rate limits, or potential side effects such as overwriting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core action, and every sentence adds value—covering file types, the upload mechanism, and follow-up steps. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex upload operation, the description covers the essential context: what the tool does, how it does it, and what to do next. The lack of an output schema is mitigated by explaining that processing continues on Apple's servers and directing to status tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the parameters are mostly self-explanatory. The description adds minimal parameter-level detail beyond what the schema already provides, such as file paths and versions, but does not compensate for the uncovered 20%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool uploads a build binary (.ipa/.pkg) to App Store Connect, with specific file formats and platforms listed. It distinguishes itself from sibling tools like asc_build_upload_status by describing the upload process itself and pointing to follow-up steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear workflow guidance: poll asc_build_upload_status and then asc_builds_list to monitor the upload's completion. It implies the tool is for initiating uploads, but does not explicitly state when not to use it or contrast with alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools