pabal-store-api

The Pabal Store API MCP server exposes the Pabal Store API tools as MCP-compatible commands so you can manage ASO data, releases, and store synchronization directly from your MCP client (e.g., Claude Code, Cursor, MCP Inspector). It provides authenticated access to App Store Connect and Google Play, enabling you to pull and push metadata, create and update releases, and auto-register apps, all while keeping credentials and data local to your machine. The built-in tools cover authentication checks, app management, ASO synchronization, and release management, so you can complete typical store workflows without leaving your editor or AI client.

Once running, you can invoke the MCP tools through your MCP client using the names listed under MCP Tools (auth-check, apps-init, apps-add, apps-search, aso-pull, aso-push, release-check-versions, release-create, release-pull-notes, release-update-notes). This lets you validate credentials, initialize and search apps, synchronize ASO data with App Store and Google Play, and manage releases with notes and versions. All operations are designed to run locally, ensuring credentials and cached data never leave your machine.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to a terminal/command prompt with network to fetch packages from npm

Installation steps:

1. Install the MCP package globally:

npm install -g pabal-store-api-mcp

2. Verify installation:

pabal-store-api-mcp --version

3. Configure credentials:

• Create the config directory for MCP

mkdir -p ~/.config/pabal-mcp
chmod 700 ~/.config/pabal-mcp

• Add credentials to a config file as required by the MCP client you use (ASO keys for App Store Connect, Google Play service account JSON, etc.). Refer to your MCP client’s documentation for the exact file format and locations.

4. Start the MCP server (example):

pabal-store-api-mcp

5. Connect your MCP client to the running server using the named MCP tool commands (auth-check, apps-init, aso-pull, etc.).

Tips and common issues:

• Ensure your credentials are valid and accessible by the MCP server process. Store keys in the recommended ~/.config/pabal-mcp path.
• The server runs locally; be mindful of any firewall rules that might block MCP client connections.
• If you see authentication errors, verify issuerId, keyId, and the presence of the .p8 key file for App Store Connect, as well as your Google Play service account JSON.
• When updating credentials, restart the MCP server to ensure changes take effect.
• The npm package name is pabal-store-api-mcp; use the exact package name in your npx command if you choose that route.
• The MCP Tools list is the canonical set of commands you can invoke from your MCP client; refer to the documentation linked in the README for details on each tool’s usage.