Skip to main content
Besides the 168 curated operations, every operation in Apple’s App Store Connect OpenAPI spec is available as a generated operation: one per path and method, 1,303 in spec 4.5.1 (GET 826, POST 180, PATCH 162, DELETE 135). Xcode Cloud, Game Center, App Clips, custom product pages, in-app events, offer codes, price schedules, webhooks, and everything else in the spec is reachable by name, with validated arguments. Use a curated operation when one exists: it hides JSON:API and resolves bundle ids. Use a generated one for everything else.

Names

appstore_api_ + the snake_case operationId from Apple’s spec: The group is the first path segment (apps, betaGroups, ciProducts…). Anything but GET is a write.

Find, describe, call

1

Search

MCP: appstore_search_operations with query, group, method, limit. Every word must match the name, path, group, or summary.
2

Describe

MCP: appstore_describe_operation. Returns every path and query parameter with its type, enum values, and maximum, and for writes the request body (attributes and relationships, required ones flagged) with a minimal example.
3

Call

MCP: appstore_call_operation with name and args.
More CLI examples:

Arguments

Arguments are validated before any request: enum values, required parameters, page-size maximums, unknown names (with the list of valid ones), and the body’s resource type. Responses that are not JSON (report files, CSV exports) come back as text.

Over MCP

Writes

Over REST

See REST API.