agc-connect-mcp
Related Servers
Alternatives to agc-connect-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search Aurora OS app store, inspect app and release information, and manage developer applications including RPM upload, metadata editing, and publication scheduling.17MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Apple App Store Connect through the official API, including apps, metadata, reviews, TestFlight, provisioning, users, and reports.MIT
- AlicenseCqualityDmaintenanceEnables publishing Android apps to Samsung Galaxy Store and Huawei AppGallery directly from AI agents, with tools for uploading binaries, updating listings, submitting apps, and verifying Samsung IAP receipts.11MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.6142 npm11MIT
- AlicenseAqualityCmaintenanceProvides AI assistants direct access to Apple's App Store Connect API, enabling them to manage apps, provisioning data, TestFlight builds, and App Store versions, including creating versions, attaching builds, and submitting for review.14MIT
TDQS
Scored across 17 tools
Most tools target distinct resources and actions, and the agc_/harmonyos_ prefixes clearly separate API catalog docs from HarmonyOS docs. The main ambiguity is agc_request as a generic fallback that conceptually overlaps with all specialized tools, and agc_upload_file vs agc_update_app_package share upload behavior, but descriptions draw clear boundaries.
The vast majority follow a consistent agc_verb_noun pattern, and the two harmonyos_ tools are internally consistent. Minor deviations like agc_auth_status (no verb) and agc_request (not verb_noun) plus the mixed prefixes keep it from a perfect score.
17 tools is slightly above the ideal 3-15 range, but the broad AppGallery Connect domain justifies the count. Each tool covers a meaningful workflow area, and the generic agc_request tool prevents the surface from becoming bloated with dozens of endpoint-specific tools.
The specialized tools cover the core app publishing lifecycle: discovery, auth, package upload, compile status, submission, reviews, ratings, and reports. The generic agc_request tool plus search/get documentation tools ensures any remaining Connect API endpoint can be reached, so there are no obvious dead ends.