Skip to main content
Glama
quartz-labs-dev

Pabal MCP

by quartz-labs-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Pabal MCP

No user-submitted related servers found.

    Related Servers

    • shipstores

      FidelisMM
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that lets AI agents drive App Store Connect, Google Play Console, and Expo EAS end to end — builds, listings, screenshots, privacy labels, in-app purchases, review submission and even replying to App Review. It automates roughly 60 tools so an app can go from a build to 'Waiting for Review' without clicking through two consoles.
      60
      69 PyPI
      17
      MIT

    • ASOHawk

      prodocik
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for App Store Optimization, enabling AI agents to read rankings, keywords, competitors, reviews, and revenue, and manage metadata with human approval.
      11
      -

    • Mağaza MCP

      tunaarikaya
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to manage both App Store Connect and Google Play from one server, covering 27 tools across apps, versions, TestFlight builds, reviews, subscriptions, pricing, and purchase diagnostics. Cross-store tools compare subscription prices and match iOS/Android app listings in a single call, while credentials stay in the macOS Keychain.
      27
      380 npm
      89
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: apps-* tools handle app registration and management, aso-* tools manage ASO data, auth-check handles authentication, and release-* tools manage version and release note operations. The descriptions clearly differentiate their functions, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent hyphenated pattern with clear prefixes (apps-, aso-, auth-, release-) and descriptive suffixes (e.g., add, init, search, pull, push). This structured naming convention makes it easy to understand tool groupings and purposes at a glance.

    Tool Count5/5

    With 10 tools, the server is well-scoped for mobile app store management, covering key areas like app registration, ASO data handling, authentication, and release management. Each tool serves a specific, necessary function without redundancy, making the count appropriate for the domain.

    Completeness4/5

    The tool set provides comprehensive coverage for core mobile app store workflows, including app setup, ASO data synchronization, authentication checks, and version/release note management. A minor gap is the lack of tools for deleting or updating registered apps, but agents can likely work around this given the strong coverage of other operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources