AppFactory
Related Servers
Alternatives to AppFactory
No user-submitted related servers found.
Related Servers
- 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-
- 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.6018MIT
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.24 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that exposes the entire Apple App Store Connect API (1,200+ operations) as MCP tools, enabling AI assistants to query apps, manage builds, handle submissions, read analytics, and more.6 npmMIT
- AlicenseAqualityAmaintenanceAn opinionated MCP server for App Store Connect that provides 13 curated tools, slash-command workflows, and a Claude Skill to manage apps, reviews, sales, and pre-submission audits via natural language.41263 npm1MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that exposes the Apple App Store Connect API to AI agents, enabling management of apps, metadata, in-app purchases, subscriptions, TestFlight, provisioning, reviews, analytics, and more through 113 curated tools plus two generic JSON:API escape-hatch tools.2-
TDQS
Scored across 125 tools
The tool descriptions are unusually thorough with 'Use when' and 'Not for' cross-references, which helps separate many overlapping areas. However, with 125 tools, several boundaries remain easy to confuse: setup_set vs config_set, pipeline_mark vs orchestrator_record_attempt, metadata_check vs metadata_listing_check vs aso_validate_metadata, and individual asc_* writes vs store_setup. Descriptions mitigate but do not fully eliminate ambiguity at this scale.
Tool names are overwhelmingly snake_case and grouped by domain prefix (asc_, setup_, pipeline_, screenshot_, etc.), which gives a readable and predictable surface. The main inconsistency is the internal pattern: some names use verb_noun (asc_list_apps), others noun_verb (metadata_check) or noun_noun (config_doctor), but these deviations are minor and not chaotic.
125 tools is an extreme mismatch for an MCP server, far beyond the recommended 3-15 range and well past the 50+ threshold that the rubric treats as severe. Even for a broad app-factory pipeline, the surface is too large for an agent to navigate reliably, with many legacy or narrowly scoped operations that could be consolidated.
The server covers an unusually complete app lifecycle: idea validation, ASO, design, scaffolding, backend deployment, store setup, screenshots, TestFlight shipping, metadata, legal pages, and submission. Remaining gaps are minor, such as TestFlight tester management, App Privacy settings (explicitly unavailable via API), and post-launch review/analytics management, which agents can work around or handle manually.