Skip to main content
Glama
meyusufdemirci

App Store Operator

by meyusufdemirci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to App Store Operator

No user-submitted related servers found.

    Related Servers

    • apple-revcat-mcp

      ItsJuniorDias
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Claude Desktop that exposes App Store Connect and RevenueCat APIs, enabling indie iOS developers to query portfolio metrics, sales reports, subscriptions, and customer reviews directly in chat.
      17
      MIT

    • meta-ads-mcp-server

      jonathanposovatz
      A
      license
      A
      quality
      D
      maintenance
      MCP Server for the Meta Marketing API. Gives Claude Desktop direct access to your ad account data — campaign performance, creative analysis, audience breakdowns, and budget pacing.
      10
      151 npm
      1
      MIT

    • App Store MCP Server

      LaurMost
      A
      license
      A
      quality
      A
      maintenance
      An open-source MCP server for live Apple App Store competitor research, enabling AI agents to search apps, fetch metadata, compare competitors, and retrieve reviews and top charts as structured JSON.
      7
      MIT

    • saas-brain-mcp

      Mohd16kaif
      F
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server for Claude AI that connects Stripe and Supabase to enable natural language SaaS analytics, including churn analysis, subscription tracking, and revenue insights.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools have clearly distinct purposes: search_app_store for discovery, get_app_details for analytics on specific IDs, research_rivals as a combined convenience wrapper, and prepare_iae for in-app event copy generation. Each description explicitly tells when to use it versus the alternatives, eliminating ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: research_rivals, search_app_store, get_app_details, prepare_iae. Verbs (research, search, get, prepare) clearly indicate actions, and nouns (rivals, app_store, app_details, iae) identify the target. No mixing of casing or verb styles.

    Tool Count5/5

    Four tools is well-scoped for an iOS App Store operations server. The primary workflows are covered: discovering apps (search_app_store), retrieving analytics (get_app_details), a combined research shortcut (research_rivals), and creating in-app events (prepare_iae). No bloat or redundancy; each tool earns its place.

    Completeness4/5

    The tool surface covers the main research and IAE copy generation workflows thoroughly. Minor gaps exist: no tool for managing App Store listing metadata (title, description), and no explicit handling of Google Play, but the tool descriptions clearly scope the server to iOS App Store research and IAE. The explicit boundary is acceptable, though a listing-management tool would round out the 'Operator' name.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources