pabal-web-mcp
# pabal-resource-mcp
MCP server for ASO ↔ Web SEO data conversion.
Build synced websites from App Store Connect and Google Play Console data.
> 💡 **Example**: [labs.quartz.best](https://labs.quartz.best/)
[](https://pabal.quartz.best/en-US/docs/pabal-resource-mcp/README) [](https://pabal.quartz.best/ko-KR/docs/pabal-resource-mcp/README)
## Installation
```bash
npm install pabal-resource-mcp
```
**Requirements:** Node.js >= 18, [pabal-store-api-mcp](https://github.com/quartz-labs-dev/pabal-store-api-mcp)
## MCP Configuration
```json
{
"mcpServers": {
"pabal-resource-mcp": {
"command": "npx",
"args": ["-y", "pabal-resource-mcp"]
}
}
}
```
For keyword research, add `mcp-appstore`:
```json
{
"mcp-appstore": {
"command": "node",
"args": ["/PATH/TO/external-tools/mcp-appstore/server.js"],
"cwd": "/PATH/TO/external-tools/mcp-appstore"
}
}
```
## Configuration
Set `dataDir` in `~/.config/pabal-mcp/config.json`:
```json
{
"dataDir": "/path/to/pabal-web"
}
```
## Tools
| Category | Tools |
| ----------- | -------------------------------------------------------------------------------------- |
| ASO | `aso-to-public`, `public-to-aso`, `improve-public`, `validate-aso`, `keyword-research` |
| Apps | `init-project`, `search-app` |
| Screenshots | `translate-screenshots`, `resize-screenshots`, `phone-to-tablet` |
| App Icon | `generate-app-icons` |
| Content | `create-blog-html` |
See [documentation](https://pabal.quartz.best/en-US/docs/pabal-resource-mcp/README) for details.
## License
MIT
---
## Pabal Web
[](https://pabal.quartz.best/)
Unified ASO + SEO management interface. [Visit →](https://pabal.quartz.best/)
TDQS
Scored across 9 tools
Most tools have distinct purposes, but there is some overlap between 'aso-to-public' and 'public-to-aso' as they handle opposite conversion directions, which could cause confusion if not carefully read. Tools like 'improve-public' and 'validate-aso' are clearly different, but the bidirectional conversion tools might be misselected without clear context.
Tool names mostly follow a consistent verb_noun or verb-noun pattern (e.g., 'aso-to-public', 'create-blog-html', 'improve-public'), with minor deviations like 'search-app' (verb_noun) and 'init-project' (verb-noun). The naming is readable and predictable, though not perfectly uniform.
With 9 tools, the count is well-scoped for the domain of ASO (App Store Optimization) and content management. Each tool serves a specific function in the workflow, from data conversion to validation, without being overly sparse or bloated.
The tool set provides comprehensive coverage for ASO workflows, including data initialization, conversion, optimization, validation, and localization. It supports full lifecycle management from pulling data to preparing for store uploads, with no obvious gaps that would hinder an agent.