Appstoreconnect MCP vs MCP Server Docker | AllMCPs
Side-by-Side Model Context Protocol Comparison
Appstoreconnect MCP vs MCP Server Docker
In-depth architectural comparison of the Appstoreconnect MCP and MCP Server Docker 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
Appstoreconnect MCP
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
MCP Server Docker
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Appstoreconnect MCP if you need specialized Developer Tools tools running via a local process. Choose MCP Server Docker if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Appstoreconnect MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Appstoreconnect MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Server Docker belongs to Developer Tools using local stdio subprocess. Select Appstoreconnect MCP when you need capabilities focused on developer tools and MCP Server Docker when you require tools for developer tools.
current price schedule per subscription. One row per territory (~175 unfiltered) — pass `territoryId` to narrow to one market
asc_list_subscription_price_points
valid price points for a subscription in a territory. Pass `nearAmount` to narrow the response to the nearest tiers around a target price.
asc_post_subscription_group
create the container every subscription must live in. A customer can hold only **one active subscription per group**, so mutually exclusive plans (Monthly vs Yearly) belong in the *same* group
asc_patch_subscription_group
rename (`referenceName` is the only mutable attribute; groups cannot move between apps)
asc_delete_subscription_group
lists the group's subscriptions first and refuses client-side naming the specific products that block the delete, instead of letting Apple return a bare 409
asc_post_subscription
create an auto-renewable subscription. **`productId` is permanent**: it cannot be changed, and Apple never lets it be reused on the account — not even after the subscription is deleted. `subscriptionPeriod` is optional at create but required before submission; the new product starts in `MISSING_MET…