Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ASC_MODENoreadonly, write or full. If set, it pins the mode for that client; the settings page warns when it detects this
ASC_KEY_IDNoKey ID
ASC_ISSUER_IDNoIssuer ID
ASC_CONFIG_DIRNoUse a different settings folder
ASC_PRIVATE_KEYNoPEM contents of the .p8 private key (\n escapes are fine)
ASC_PRIVATE_KEY_PATHNoPath to the .p8 private key file
ASC_MAX_RESPONSE_CHARSNoLargest response returned inline60000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
asc_check_connectionA

Verify the API key works and show the server's mode (readonly/write/full), spec version and rate-limit status. Run this first when setting up or when calls fail with auth errors.

asc_list_appsA

List the apps in the App Store Connect account with their ids, names, bundle ids and SKUs. App ids are needed by most other tools.

asc_app_overviewA

One-call status of an app: its details, the latest App Store versions with their review/release state, and the most recent builds with processing state.

asc_list_buildsB

List an app's builds, newest first, with build number, marketing version, platform, processing state and expiry.

asc_list_customer_reviewsA

List an app's App Store customer reviews with rating, title, body, territory and any developer response. Use unansweredOnly to find reviews that still need a reply.

asc_list_beta_groupsB

List an app's TestFlight beta groups (internal and external) with their ids and public link settings.

asc_list_version_localizationsA

List the per-locale App Store metadata of a version: description, keywords, what's new, promotional text, marketing and support URLs. Get version ids from asc_app_overview.

asc_download_sales_reportA

Download a Sales and Trends report (sales, subscriptions, subscription events, installs, ...) and return it as parsed rows. The vendor number is under Payments and Financial Reports in App Store Connect. Reports are usually available a day after the reporting date.

asc_download_finance_reportA

Download a monthly financial report (proceeds by region) and return it as parsed rows. Region codes include US, EU, JP, AU, CA, GB, WW (all regions, FINANCE_DETAIL only), ZZ (consolidated).

asc_list_resource_groupsA

List every resource group (tag) in the App Store Connect API with its operation count, e.g. Apps, Builds, BetaGroups, Subscriptions, GameCenterLeaderboards. Use it to browse the API when you don't know what to search for; then call asc_search_operations with a tag.

asc_search_operationsA

Search all 1,300+ App Store Connect API operations by keywords (e.g. 'customer reviews', 'testflight testers', 'subscription prices', 'xcode cloud builds'). Returns operationIds to pass to asc_describe_operation and asc_call_operation. Prefer a curated asc_* tool when one fits the task.

asc_describe_operationA

Show everything needed to call one operation: path params, query params (filters, sort, include, limit), sparse fieldsets (fields[type] -> attribute names), and the full JSON request-body schema for creates and updates. Call this before asc_call_operation for any operation you haven't used yet.

asc_call_operationA

Execute any App Store Connect API operation by operationId. Inputs are validated against Apple's OpenAPI spec before sending. Query keys use Apple's exact names, e.g. {"filter[app]": "123", "sort": "-uploadedDate", "fields[builds]": ["version","processingState"], "include": "preReleaseVersion", "limit": 50}. Bodies use JSON:API form: {"data": {"type": "...", "attributes": {...}, "relationships": {...}}}. Responses are compacted (resource links removed); follow nextUrl with asc_fetch_url or pass fetchAll. Creates and updates need the write access mode and deletes need full; a blocked call explains how the user can enable them.

asc_fetch_urlA

GET a full api.appstoreconnect.apple.com URL, such as a nextUrl from a previous response or a relationship's related link. Only Apple's API host is allowed.

asc_open_settingsA

Open the local settings page in the user's browser, where they add or replace their API key, choose the access mode (read-only, write, full) and add this server to Claude Code, Claude Desktop or Cursor. Use it when credentials are missing or rejected, or when the user wants writes enabled. Only the user can change settings there.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 15 tools

Disambiguation5/5

Each tool has a clearly distinct role: curated list/overview/report tools target specific resources, while the generic search/describe/call/fetch pipeline is explicitly layered. Descriptions clarify when to use curated tools versus generic API access, and no two tools appear to do the same thing.

Naming Consistency4/5

All tools share the asc_ prefix and snake_case, and nearly all follow a verb_noun pattern (list_apps, download_sales_report, search_operations). The only deviation is asc_app_overview, which is noun-based rather than verb-based, a minor inconsistency.

Tool Count5/5

15 tools is well-scoped for a broad App Store Connect integration: 8 curated tools cover common read workflows, and 7 generic/setup tools provide safe access to the full 1,300+ operation API without exploding the surface. Each tool earns its place, with no obvious redundancy.

Completeness5/5

The curated tools cover key read paths (apps, versions, builds, reviews, beta groups, reports), and asc_search_operations/describe_operation/call_operation provide full CRUD and lifecycle access across the entire App Store Connect API. Auth, pagination, and settings are also addressed, leaving no structural dead ends.

Maintenance

ActivityNo data
ResponsivenessNo issues