legacy2mcp vs io.github.devinwang/app-store-connect-mcp
legacy2mcp is an MCP server published by bvenkata. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.devinwang/app-store-connect-mcp is an MCP server published by devinwang. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
| Marketplace |  legacy2mcp |  io.github.devinwang/app-store-connect-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.1 Downloads/month (PyPI): 262 Downloads/week (PyPI): 697 Forks (GitHub): 6 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 0.5.0 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.5.1 Downloads/month (PyPI): 262 Downloads/week (PyPI): 697 Forks (GitHub): 6 Stars (GitHub): 6 Not marked · First seen |
Not listed |
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
| Fact | legacy2mcp | io.github.devinwang/app-store-connect-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 6 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 1 (worse) |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (legacy2mcp) | On your machine (apple-app-store-connect-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/bvenkata/legacy2mcp | github.com/devinwang/app-store-connect-mcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
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
legacy2mcp
Turn a legacy SOAP/WSDL, database, or REST API into a safe, typed, audit-logged MCP server
io.github.devinwang/app-store-connect-mcp
MCP server for Apple's App Store Connect API: 1316 tools generated from the official OpenAPI spec.
How to run each
legacy2mcp As a local MCP server: PyPI package
claude mcp add --transport stdio legacy2mcp -- uvx legacy2mcp run --config "<YOUR_CONFIG>"Requires: --config
io.github.devinwang/app-store-connect-mcp As a local MCP server: npm package
claude mcp add --transport stdio app-store-connect-mcp -- npx -y apple-app-store-connect-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: legacy2mcp · What it can do: io.github.devinwang/app-store-connect-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.