Pabal MCP
Related Servers
Alternatives to Pabal MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceGives AI assistants complete, spec-driven access to Apple's App Store Connect API through 1300+ tools covering the full surface — apps and versions, TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases and subscriptions, pricing, review submissions, provisioning, analytics, sales and finance reports. It lets users automate submission workflows, manage multi-account credentials, and orchestrate builds and releases across any MCP client.500189 npm3MIT
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.25 npm1MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets AI agents drive App Store Connect, Google Play Console, and Expo EAS end to end — builds, listings, screenshots, privacy labels, in-app purchases, review submission and even replying to App Review. It automates roughly 60 tools so an app can go from a build to 'Waiting for Review' without clicking through two consoles.6019MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for App Store Optimization, enabling AI agents to read rankings, keywords, competitors, reviews, and revenue, and manage metadata with human approval.11-
- AlicenseNot gradedqualityAmaintenanceEnables terminal and MCP clients to manage Google Play, App Store Connect, and AdMob through official APIs, including listings, releases, reviews, vitals, sales, and reports, with dry-run safety by default.MIT
- AlicenseNot gradedqualityCmaintenanceExposes the full App Store Connect API (1,263 operations) to AI agents via four token-efficient MCP tools, enabling app metadata, TestFlight, subscriptions, and reporting management through natural language.MIT
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.