No user-submitted related servers found.
Scored across 20 tools
Each tool has a clearly distinct purpose, ranging from read-only discovery (e.g., list_apps, get_bundle_id_state) to planning and applying changes. Even similar planning tools (e.g., plan_metadata_changes, plan_screenshot_changes) specify different domains. No two tools appear to overlap in a way that would cause misselection.
All tool names follow a consistent verb_noun pattern, with verbs like get, list, plan, apply, submit, and check. Read-only tools use get/list/check/inspect/export/validate, while mutation intent is clear with plan/apply/submit. The naming is uniform and predictable.
20 tools is at the upper end of the ideal range but still justified given the breadth of App Store Connect domains (apps, provisioning, metadata, screenshots, commerce, signing, submission). Slightly heavy but each tool serves a distinct purpose in the workflow.
The tool surface covers read, plan, and apply steps for common App Store workflows, including provisioning, metadata, screenshots, signing, and submission. Minor gaps exist (e.g., no tool for managing users or analytics), and some destructive actions are intentionally separate or require manual steps, but the core lifecycle is well covered.