Pabal MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth-checkC | Check authentication status for App Store Connect / Google Play Console. |
| apps-initA | Query app list from store API and register automatically. App Store: auto-register all apps, Google Play: packageName required. |
| apps-addC | Register individual app by bundleId or packageName. Automatically checks both stores. |
| apps-searchB | Search registered apps. Returns all apps if called without query. |
| aso-pullC | Fetch ASO data from App Store/Google Play and save to local cache. |
| aso-pushC | Push ASO data from local cache to App Store/Google Play. |
| release-check-versionsC | Check latest versions from App Store/Google Play. |
| release-createB | Create a new version on App Store/Google Play. If version is not provided, checks and displays latest versions from each store. |
| release-pull-notesC | Fetch release notes from App Store/Google Play. |
| release-update-notesC | Update release notes (What's New) for App Store/Google Play version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.