Ext Ops Panel
Open dashboard
Comparison

Iaptic vs App Store Connect

Iaptic is an MCP server published by iaptic. Marketplaces we read that list it: 1 (Docker MCP Catalog). App Store Connect is an MCP server published by forgeopslabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceIapticApp Store Connect
Docker MCP Catalog Listed
Version: sha256:7f86e3becb71
Forks (GitHub): 6
Pulls (Docker Hub): 16 319
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Iaptic vs App Store Connect
FactIapticApp Store Connect
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)2 (worse)
Pulls (Docker Hub) (differs)16 319No figure on Docker Hub
Forks (GitHub) (differs)6 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/iaptic)On your machine (https://github.com/forgeopslabs/appstore-mcp/releases/download/v0.3.1/appstore-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)17Not published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/iaptic/mcp-server-iapticgithub.com/forgeopslabs/appstore-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Iaptic

In its own words, on Docker MCP Catalog:

Model Context Protocol server for interacting with iaptic.

App Store Connect

In its own words, on Official MCP Registry:

MCP server for the Apple App Store Connect API - 114 annotated tools, optional read-only mode.

How to run each

Iaptic As a local MCP server: Docker image

Claude Code
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iaptic

Requires: IAPTIC_API_KEY (secret)

App Store Connect

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: ASC_ISSUER_ID, ASC_KEY_ID, ASC_PRIVATE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of App Store Connect publish no list of tools, so we do not compare tools.

Settings each asks for

Only Iaptic asks for

  • IAPTIC_API_KEY (secret)
  • IAPTIC_APP_NAME

Only App Store Connect asks for

  • ASC_ISSUER_ID
  • ASC_KEY_ID
  • ASC_PRIVATE_KEY (secret)
  • ASC_PRIVATE_KEY_PATH
  • ASC_READ_ONLY
  • ASC_TOOLS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Iaptic · What it can do: App Store Connect · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built