Pabal MCP

Pabal MCP

Manages App Store Connect and Google Play Console metadata, releases, and ASO workflows locally through MCP tools, enabling store management directly from AI clients without manual console navigation.

Category
访问服务器

README

Cover

Install MCP Server

한국어 docs

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>

❌ Without pabal-mcp

  • Manual App Store Connect and Google Play Console clicks for every update
  • Copy-paste errors across locales and release notes
  • Repeating the same setup per client or project

<br>

✅ With pabal-mcp

  • One MCP server that handles ASO pulls/pushes for both stores
  • Consistent release note updates and version checks from your AI client
  • Reusable, scriptable workflows backed by local cache and config

<br>

🛠️ MCP Client Installation

Requirements

  • Node.js >= 18
  • MCP client: Cursor, Claude Code, VS Code, Windsurf, etc.

[!TIP] If you repeatedly do ASO/store tasks, add a client rule like "always use pabal-mcp" so the MCP server auto-invokes without typing it every time.

Global install (recommended)

npm install -g pabal-mcp
# or
yarn global add pabal-mcp

Install globally first for fastest starts and to avoid npm download issues (proxy/firewall/offline). You can still use npx -y pabal-mcp, but global install is recommended. After global install, set your MCP config to command: "pabal-mcp" (no npx needed).

<details> <summary><b>Install in Cursor</b></summary>

Add to ~/.cursor/mcp.json (global) or project .cursor/mcp.json:

{
  "mcpServers": {
    "pabal-mcp": {
      "command": "npx",
      "args": ["-y", "pabal-mcp"]
    }
  }
}

</details>

<details> <summary><b>Install in VS Code</b></summary>

Example settings.json MCP section:

"mcp": {
  "servers": {
    "pabal-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "pabal-mcp"]
    }
  }
}

</details>

<details> <summary><b>Install in Claude Code</b></summary>

[!TIP] See the official Claude Code MCP documentation for detailed configuration options.

Add to Claude Code MCP settings (JSON format):

{
  "mcpServers": {
    "pabal-mcp": {
      "command": "npx",
      "args": ["-y", "pabal-mcp"]
    }
  }
}

Or if installed globally (npm install -g pabal-mcp):

{
  "mcpServers": {
    "pabal-mcp": {
      "command": "pabal-mcp"
    }
  }
}

</details>

<details> <summary><b>Install in Windsurf</b></summary>

{
  "mcpServers": {
    "pabal-mcp": {
      "command": "npx",
      "args": ["-y", "pabal-mcp"]
    }
  }
}

</details>

<br>

🔐 Configure Credentials

  1. Create config directory and set permissions:
mkdir -p ~/.config/pabal-mcp
chmod 700 ~/.config/pabal-mcp
  1. Create the config file (pre-filled placeholders):
cat <<'EOF' > ~/.config/pabal-mcp/config.json
{
  "dataDir": "/ABSOLUTE/PATH/TO/pabal-web",
  "appStore": {
    "issuerId": "xxxx",
    "keyId": "xxxx",
    "privateKeyPath": "./app-store-key.p8"
  },
  "googlePlay": {
    "serviceAccountKeyPath": "./google-play-service-account.json"
  }
}
EOF

Replace the issuerId and keyId placeholders in the next step after you grab your App Store Connect keys. dataDir is the absolute path where raw data pulled from each store is stored (e.g., /ABSOLUTE/PATH/TO/pabal-web).

  1. Add your credentials to ~/.config/pabal-mcp/:

    App Store Connect API key:

    • App Store Connect > Users and Access > Keys → "Generate API Key." Use Admin/App Manager, download the .p8 (only downloadable once), and save it as ~/.config/pabal-mcp/app-store-key.p8.
    • Copy the Issuer ID and Key ID from the key details, then update issuerId and keyId in ~/.config/pabal-mcp/config.json with those values.

    Google Play service account JSON:

    • Google Cloud Manage service accounts → create a service account (name it pabal for clarity) → Create key → JSON.
    • Save the downloaded JSON as ~/.config/pabal-mcp/google-play-service-account.json.
    • Grant Play Console access to that service account email: go to Users and permissions → Invite new user → enter the service account email → choose the ASO apps → enable:
      • View app information and download bulk reports (read-only)
      • Create, edit, and delete drafts of apps
      • Release to production
      • Manage device exclusion lists
      • Use Play App Signing
      • Manage store presence

    Config file shape (after updating your IDs):

    {
      "dataDir": "/ABSOLUTE/PATH/TO/pabal-web",
      "appStore": {
        "issuerId": "<your-issuer-id>",
        "keyId": "<your-key-id>",
        "privateKeyPath": "./app-store-key.p8"
      },
      "googlePlay": {
        "serviceAccountKeyPath": "./google-play-service-account.json"
      }
    }
    
  2. Pull store data

    Use apps-init to fetch and auto-register existing apps from the store APIs. This will populate your ~/.config/pabal-mcp/registered-apps.json with the apps available in your stores.

  3. Lock file permissions (all files in the config folder):

chmod 600 ~/.config/pabal-mcp/*

This applies to every file under ~/.config/pabal-mcp/; rerun after adding any new credential file.

<br>

🔧 MCP Tools

  • Authentication
    • auth-check: Check App Store Connect / Google Play authentication.
  • App management
    • apps-init: Fetch apps from the store API and auto-register them (Google Play needs packageName).
    • apps-add: Register a single app by bundleId/packageName.
    • apps-search: Search registered apps.
  • ASO data sync
    • aso-pull: Fetch ASO data to the .aso/ local cache.
    • aso-push: Push ASO data from .aso/ to the stores.
  • Release management
    • release-check-versions: Show the latest versions per store.
    • release-create: Create a new version.
    • release-pull-notes: Pull release notes to the .aso/ cache.
    • release-update-notes: Update release notes/what's new.

<br>

🏗️ Development

From source

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

Testing

Run all tests: npm test

<br>


<br>

🌐 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

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选