Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Related Servers

Alternatives to Connect IQ MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage App Store Connect releases—versions, builds, TestFlight groups, metadata, pricing, reviews, and submission—while staying read-only by default and requiring human approval before any public or destructive action.
      23
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets coding agents manage apps in App Store Connect through workflow-level tools: shipping TestFlight builds, managing testers and groups, editing listings, replacing and reordering screenshots, handling subscriptions, replying to reviews, downloading sales reports, and submitting for App Review. It is read-only unless writes are explicitly enabled, and destructive actions run as dry runs until confirmed.
      31
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Lets Claude and other AI agents work with Apple's developer API to manage app metadata, versions, review submissions, builds, TestFlight, customer reviews, reports, Xcode Cloud, devices, and team members, with optional read-only safeguards.
      36
      89 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to manage app listings, versions, localizations, screenshots, TestFlight groups and testers, bundle IDs, devices, users, analytics reports, and sales or finance reports through the App Store Connect API.
      36
      28 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are grouped by clear domains (auth, sdk, sim, store) and most pairs are distinct, e.g. sdk_device_get vs sdk_devices_list or store_apps_list vs store_app_get. A few boundaries need the descriptions to resolve: store_reviews_inbox (all apps, unanswered) vs store_reviews_list (one app, paged), and sdk_build vs sim_run, which can also build a project+device before running.

    Naming Consistency4/5

    A predictable {domain}_{noun}_{verb} pattern dominates: sdk_device_get, sdk_manifest_set_products, store_reviews_list, sim_logs. Minor deviations exist where the noun is dropped (sdk_build, auth_login, store_installs, store_ratings), but prefixes consistently signal domain and the set reads coherently.

    Tool Count4/5

    21 tools sit at the upper end of comfortable but are justified by four genuinely separate surfaces (developer portal auth, SDK/key/manifest, simulator, store analytics/reviews). Each tool covers a distinct operation, with only the meta 'toolsets' tool feeling auxiliary rather than essential.

    Completeness3/5

    Core flows are covered (auth, build, device/manifest inspection, simulator run/stop/logs, store metadata/installs/ratings/reviews), but notable gaps remain: replies are read by the review tools yet there is no tool to post a review reply, no SDK/device install tool, no logout, and no app upload/publish step for the build output.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues