Pabal FAQs

Question 1

Is Pabal secure with my App Store Connect and Google Play credentials?

Accepted Answer

Yes, Pabal runs entirely locally on your machine. This means all your credentials and cached ASO data never leave your environment, as API calls to the app stores are made directly from your device, ensuring maximum security.

Question 2

What are the main benefits of using Pabal for app management?

Accepted Answer

Pabal eliminates manual clicks for store updates, prevents copy-paste errors across locales and release notes, and enables reusable, scriptable ASO workflows. It offers unified data pull/push for both major app stores and ensures consistent version checks from your AI client.

Question 3

What ASO and release management tasks can I perform with Pabal?

Accepted Answer

Pabal provides tools for authentication checks, app registration and search, ASO data pull/push to a local cache, and release management including checking latest versions, creating new versions, and updating release notes ('what's new').

Question 4

What is Pabal and how does it work?

Accepted Answer

Pabal is an MCP server that exposes App Store Connect and Google Play API workflows as local tools. It allows you to manage app metadata, releases, and ASO data syncs directly from your AI client (like Claude Code or Cursor) by running 100% locally on your machine.

Question 5

What are the requirements to use Pabal?

Accepted Answer

You need Node.js 18+, an MCP-compatible client (such as Cursor, Claude Code, or VS Code with MCP extension), and valid App Store Connect API keys and Google Play service account JSON credentials configured locally.

Pabal

Key Features

Use Cases

Android Control

OneSignal

Firebase

Background Coding Agent

Meme Maker

Agent Skill Creator

Key Features

Use Cases