Skip to main content
Glama

Cover

Install MCP Server

Pabal Store API MCP (English) Pabal Store API MCP (한국어)

MCP server for App Store Connect & Play Console API

Up-to-date ASO workflows exposed as MCP tools. Run it as a stdio MCP server (Claude Code, Cursor, MCP Inspector, etc.) to manage metadata, releases, and store syncs without leaving your AI client.

NOTE

Runs 100% locally on your machine, so credentials and cached ASO data never leave your environment (store API calls are made directly from your device).

Quick Start

Install

npm install -g pabal-store-api-mcp

Configure

  1. Create config directory:

mkdir -p ~/.config/pabal-mcp
chmod 700 ~/.config/pabal-mcp
  1. Add your credentials to ~/.config/pabal-mcp/config.json:

    • App Store Connect: API key (.p8 file) with issuerId and keyId

    • Google Play: Service account JSON key

  2. Set up MCP client (Cursor, VS Code, Claude Code, etc.) to use pabal-store-api-mcp

Registered Apps

Registered apps are stored locally in ~/.config/pabal-mcp/registered-apps.json. It is usually created and updated by apps-init or apps-add, then used by tools such as apps-search, aso-pull, and release-note workflows. See the app management docs for the detailed format: English / 한국어.

Related MCP server: App Store Connect MCP Server

Features

  • ✅ ASO Data Sync: Pull/push metadata from App Store and Google Play

  • ✅ Release Management: Create versions and update release notes

  • ✅ App Management: Auto-register apps from store APIs

  • ✅ 100% Local: All operations run on your machine

MCP Tools

  • Authentication: auth-check

  • App Management: apps-init, apps-add, apps-search

  • ASO Sync: aso-pull, aso-push

  • Release Management: release-check-versions, release-create, release-pull-notes, release-update-notes

Documentation

📖 Pabal Store API MCP Documentation (English) 📖 Pabal Store API MCP 문서 (한국어)

Development

git clone https://github.com/quartz-labs-dev/pabal-store-api-mcp.git
cd pabal-store-api-mcp
yarn install
yarn dev:mcp

License

MIT


🌐 Pabal Web

Want to manage ASO and SEO together? Check out Pabal Web.

Pabal Web

Pabal Web is a Next.js-based web interface that provides a complete solution for unified management of ASO, SEO, Google Search Console indexing, and more.

👉 Visit Pabal Web

Available Tools

10 tools
apps-addC

Register individual app by bundleId or packageName. Automatically checks both stores.

Inputs: identifier (required), slug, store.

apps-initA

Query app list from store API and register automatically. App Store: auto-register all apps, Google Play: packageName required.

Inputs: store, packageName.

aso-pullC

Fetch ASO data from App Store/Google Play and save to local cache.

Inputs: app, packageName, bundleId, store, +1 more.

aso-pushC

Push ASO data from local cache to App Store/Google Play.

Inputs: app, packageName, bundleId, store, +2 more.

auth-checkC

Check authentication status for App Store Connect / Google Play Console.

Inputs: store.

release-check-versionsC

Check latest versions from App Store/Google Play.

Inputs: app, packageName, bundleId, store.

release-createB

Create a new version on App Store/Google Play. If version is not provided, checks and displays latest versions from each store.

Inputs: app, packageName, bundleId, version, +2 more.

release-pull-notesC

Fetch release notes from App Store/Google Play.

Inputs: app, packageName, bundleId, store, +1 more.

release-update-notesC

Update release notes (What's New) for App Store/Google Play version.

Inputs: app, packageName, bundleId, store, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      -
    • A
      license
      A
      quality
      B
      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
      21
      MIT