App Publish MCP vs McpProxy — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
App Publish MCP vs McpProxy
In-depth architectural comparison of the App Publish MCP and McpProxy MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
App Publish MCP
Browser Automation · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
McpProxy
Browser Automation · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose App Publish MCP if you need specialized Browser Automation tools running via a local process. Choose McpProxy if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose App Publish MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: APPLE_API_KEY, APPLE_API_ISSUER_ID, GOOGLE_SERVICE_ACCOUNT_KEY.
Primary tools included: Manage app metadata, localizations, and screenshots on App Store Connect, Create, assign, and submit app versions for review on Apple platform, Handle TestFlight beta groups and testers management.
Unified MCP server for App Store Connect & Google Play Console — 91 tools for iOS/Android app management, TestFlight, builds, submissions, pricing, and sales reports.
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
App Publish MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, McpProxy belongs to Browser Automation using local stdio subprocess. Select App Publish MCP when you need capabilities focused on browser automation and McpProxy when you require tools for browser automation.
Primary tools included: Proxies MCP requests to JetBrains IDEs via local webserver, Supports configuration of IDE host and port, Enables logging via environment variable.