App Store Connect hosted MCP

The hosted server runs the same operations as appstore-mcp, but your .p8 key stays in Appeeky. Each call uses a short-lived App Store Connect token that Appeeky signs for that call.

MCP endpoint: https://asc-api.appeeky.com/mcp

Set up

Connect App Store Connect in Appeeky

Open Settings → Data sources on appeeky.com and add your App Store Connect API key. See App Store Connect.

Copy your Appeeky API key

From the same Settings page. See Authentication.

Add the server to your MCP client

{
  "mcpServers": {
    "app-store-connect": {
      "url": "https://asc-api.appeeky.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APPEEKY_API_KEY"
      }
    }
  }
}

X-API-Key: YOUR_APPEEKY_API_KEY works in place of the Authorization header.

Start with appstore_list_apps

It returns the apps your App Store Connect key can see, with their Apple app ids. Most other tools take appId.

Allow writes

The server is read-only by default. Operations that change App Store Connect (versions, submissions, TestFlight, review responses, prices, users, signing) are hidden until you add this header:

{
  "mcpServers": {
    "app-store-connect-writes": {
      "url": "https://asc-api.appeeky.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APPEEKY_API_KEY",
        "X-ASC-Allow-Writes": "true"
      }
    }
  }
}

Without the header:

appstore_request stays available for GET only.
appstore_search_operations lists only read operations, and appstore_call_operation refuses writes.

Keep two entries: a read-only one for everyday questions, and a write-enabled one you turn on only when you want the agent to ship.

The whole API, without 1,000 tools

Besides the curated tools (appstore_list_apps, appstore_submit_version, appstore_list_customer_reviews, …), three tools reach every App Store Connect operation:

Tool	What it does
`appstore_search_operations`	Find an operation by keyword, e.g. “custom product pages”
`appstore_describe_operation`	Show its parameters and request body
`appstore_call_operation`	Run it

See Full API coverage.

What is not available hosted

Not hosted	Why	Use instead
`appstore_upload_screenshot`, `appstore_upload_preview`	Need a local file	`appstore screenshots upload`, `appstore previews upload`
`appstore_download_profile`	Writes a local file	`appstore profiles download`
`accounts` tools (`appstore_list_accounts`, `appstore_register_account`, …)	Edit local config	The Appeeky connection is the account

Asking for one through appstore_call_operation or REST returns a CLI-only error (CLI_ONLY over REST). Hosted tools have no account argument.

Prompts to try

“List my apps and show the latest build of each, with its processing state.”
“Summarize the last 500 reviews of my app and list unanswered 1- and 2-star ones.”
“What is blocking version 2.4.0 from being submitted?”
“Find the operation for in-app events and list the events of my app.”

Credits

Each tool call that reaches App Store Connect is one metered Appeeky API call. initialize, tools/list, appstore_search_capabilities, appstore_list_capabilities, appstore_search_operations, and appstore_describe_operation are free. Arguments are validated before Appeeky opens a session, so a rejected call costs nothing. See Rate Limits & Credits.

Same operations over REST

GET /v1/apps, GET /v1/ops?q=…, GET /v1/ops/{name}, and POST /v1/ops/{name} on https://asc-api.appeeky.com. See REST API.

Overview

Google Play CLI

App Store Connect CLI

Set up

Allow writes

The whole API, without 1,000 tools

What is not available hosted

Prompts to try

Credits

Same operations over REST

​Set up

​Allow writes

​The whole API, without 1,000 tools

​What is not available hosted

​Prompts to try

​Credits

​Same operations over REST

Set up

Allow writes

The whole API, without 1,000 tools

What is not available hosted

Prompts to try

Credits

Same operations over REST