Pabal Web

The pabal-web-mcp server bridges ASO and Web SEO data, enabling you to convert data between platforms and build synced websites from App Store Connect and Google Play Console data. It is designed to run alongside your MCP client and centralize your data workflows for easier management and automation.

How to use

You operate this MCP server by starting it from an MCP client that supports standard MCP configurations. Deploy the server configurations below, then connect your MCP client to the available HTTP or STDIO endpoints. Once running, you can orchestrate ASO tasks, keyword research, and app store data flows to generate consistent, search-friendly web content and analytics-ready data.

Typical usage patterns include starting the main server and, if needed, an auxiliary app store tool server. You can run either server locally or at a remote host according to your deployment needs. The configuration enables you to publish and consume MCP commands like building projects, searching apps, and processing ASO data through a unified interface.

How to install

npm install pabal-web-mcp

Prerequisites you need before installation:

• Node.js version 18 or newer
• Internet access to install packages
• A supported MCP client to connect to the running server (optional during initial testing)

Create the MCP configuration to run the pabal-web-mcp server as a STDIO process and, optionally, add the keyword research companion server if you plan to do keyword analysis.

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

Additional setup steps

If you want to enable keyword research integration, additionally configure the keyword research server as shown below.

{
  "mcp-appstore": {
    "command": "node",
    "args": ["/PATH/TO/external-tools/mcp-appstore/server.js"],
    "cwd": "/PATH/TO/external-tools/mcp-appstore"
  }
}

Configuration

Set the base data directory for the MCP server to store its data and caches. Create or edit the config file at your home directory under .config/pabal-mcp/config.json and point dataDir to your desired path.

{
  "dataDir": "/path/to/pabal-web"
}

Notes and tips

• The main server is started via the STDIO configuration using the provided command and arguments. You can run multiple MCP servers concurrently if needed, each with its own namespace and settings.

• If you maintain separate environments for development and production, consider using environment-specific config files and namespaced mcpServers to avoid conflicts.

Security and maintenance

• Keep Node.js up to date and validate external tools before running them in production. Use minimal privileges for the process and isolate worker processes where possible.

• Regularly back up your dataDir and rotate credentials or tokens used by connected tools.

Troubleshooting

• If a server fails to start, verify that the command and arguments are correctly quoted and that the specified cwd (for the appstore tool) exists and contains the expected server file.

• Check the MCP client load paths to ensure it can discover and connect to your configured mcpServers.

Examples

Example startup pieces you might use in a typical local development setup.

Available tools

aso-to-public

Convert ASO data into a public-facing format ready for web publication.

public-to-aso

Ingest public data back into ASO representations for analysis and updates.

improve-public

Improve and optimize public-facing ASO entries for better search visibility.

validate-aso

Validate ASO entries against predefined rules and guidelines.

keyword-research

Perform keyword research to inform SEO and ASO strategies.

init-project

Initialize a new project scaffold for APK/APP data integration.

search-app

Search the app catalog or database to retrieve app metadata.

create-blog-html

Generate blog HTML content from data sources for SEO.