Pabal MCP
Pabal MCP is an MCP server that provides comprehensive management of App Store Connect and Google Play Console directly from AI clients like Cursor, Claude Code, and VS Code.
Authentication & Setup: Check authentication status for both stores, automatically fetch and register apps from store APIs, or manually add apps by bundle ID or package name. Search registered apps using various criteria (slug, bundleId, packageName, or name).
ASO Data Management: Pull ASO data from stores to local cache for offline editing, push cached data back to stores with optional image uploads, and preview changes with dry-run mode before applying them.
Release Management: Check latest versions across stores, create new versions on either or both platforms (with version code support for Google Play), pull release notes from stores, and update "What's New" sections with multi-locale support or automatic translation from a source locale.
Key Features: Multi-store support through a single interface, local-first architecture keeping credentials and cached data secure on your machine, flexible app targeting by slug/bundleId/packageName, and scriptable workflows enabling automated ASO and release management tasks from within AI coding assistants.
Enables management of App Store Connect metadata, releases, and app information through ASO workflows, including pulling and pushing app data, checking versions, and updating release notes.
Provides tools for managing Google Play Console apps, including ASO data synchronization, release management, version checking, and updating release notes for Android applications.
Integrates with Google Search Console for SEO management and indexing through the Pabal Web interface.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pabal MCP pull the latest metadata from App Store Connect for my app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

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.
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-mcpConfigure
Create config directory:
mkdir -p ~/.config/pabal-mcp
chmod 700 ~/.config/pabal-mcpAdd your credentials to
~/.config/pabal-mcp/config.json:App Store Connect: API key (
.p8file) withissuerIdandkeyIdGoogle Play: Service account JSON key
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-checkApp Management:
apps-init,apps-add,apps-searchASO Sync:
aso-pull,aso-pushRelease 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:mcpLicense
MIT
🌐 Pabal Web
Want to manage ASO and SEO together? Check out 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.
Available Tools
10 toolsapps-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.
apps-searchB
Search registered apps. Returns all apps if called without query.
Inputs: query, store.
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
Scored across 10 tools
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.
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.
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.
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
Related MCP Connectors
App Store Connect operator for AI agents: icons, TestFlight builds, listings, IAP, rejection fixes.
Create App Store screenshots, icons, ASO copy, localization, and revisions via hosted MCP.
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for App Store Optimization, enabling AI agents to read rankings, keywords, competitors, reviews, and revenue, and manage metadata with human approval.11-
- AlicenseNot gradedqualityCmaintenanceExposes the full App Store Connect API (1,263 operations) to AI agents via four token-efficient MCP tools, enabling app metadata, TestFlight, subscriptions, and reporting management through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.56 npm1MIT
- AlicenseAqualityBmaintenanceAn 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.6021MIT