Pabal MCP
[](https://cursor.com/en/install-mcp?name=pabal-store-api-mcp&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInBhYmFsLW1jcCJdfQ%3D%3D)
[](https://pabal.quartz.best/en-US/docs/pabal-store-api-mcp/README) [](https://pabal.quartz.best/ko-KR/docs/pabal-store-api-mcp/README)
# 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).
<br>
## Quick Start
### Install
```bash
npm install -g pabal-store-api-mcp
```
### Configure
1. Create config directory:
```bash
mkdir -p ~/.config/pabal-mcp
chmod 700 ~/.config/pabal-mcp
```
2. 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
3. Set up MCP client (Cursor, VS Code, Claude Code, etc.) to use `pabal-store-api-mcp`
<br>
### 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](docs/en-US/apps.md) / [한국어](docs/ko-KR/apps.md).
<br>
## 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
<br>
## 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`
<br>
## Documentation
📖 **[Pabal Store API MCP Documentation (English)](https://pabal.quartz.best/en-US/docs/pabal-store-api-mcp/README)**
📖 **[Pabal Store API MCP 문서 (한국어)](https://pabal.quartz.best/ko-KR/docs/pabal-store-api-mcp/README)**
<br>
## Development
```bash
git clone https://github.com/quartz-labs-dev/pabal-store-api-mcp.git
cd pabal-store-api-mcp
yarn install
yarn dev:mcp
```
<br>
## License
MIT
<br>
---
<br>
## 🌐 Pabal Web
Want to manage ASO and SEO together? Check out **Pabal Web**.
[](https://pabal.quartz.best/)
**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](https://pabal.quartz.best/)
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.