MCP server for App Store / Play Store ASO workflows
Pabal Store Api MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Pabal Store Api MCP directly instead of describing what you should do. MCP server for App Store / Play Store ASO workflows.
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.
Once Pabal Store Api MCP is connected, these are the calls the assistant has available:
Authentication — auth-checkConfigure — 2. Add your credentials to ~/.config/pabal-mcp/config.json: - App Store Connect: API key (.p8 file) with issuerId and keyId - Google PlayInstallation goes through your MCP client rather than a global install: point it at pabal-store-api-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pabal Store Api MCP's toolset — Authentication, Configure — is a fair guide to whether it matches your workflow. It is maintained by quartz-labs-dev; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Authentication | auth-check |
| Configure | 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 |
{
"mcpServers": {
"pabal-store-api": {
"command": "npx",
"args": ["-y", "pabal-store-api-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.