io.github.heznpc/iconnect vs WWDC MCP
io.github.heznpc/iconnect is an MCP server published by heznpc. Marketplaces we read that list it: 1 (Official MCP Registry). WWDC MCP is an MCP server published by jabbertones-cloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  io.github.heznpc/iconnect |  WWDC MCP |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 0.1.1 Downloads/month (npm): 124 Downloads/week (npm): 40 Forks (GitHub): 3 Stars (GitHub): 18 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | io.github.heznpc/iconnect | WWDC MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 18 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (iconnect-mcp) | On your machine (https://github.com/jabbertones-cloud/wwdc-mcp-server/releases/download/v0.2.1/WWDC-MCP-v0.2.1.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/heznpc/iconnect | github.com/jabbertones-cloud/wwdc-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.heznpc/iconnect
MCP server for the entire Apple ecosystem — 123 tools across 14 modules. macOS only.
WWDC MCP
Apple developer intelligence for agents: WWDC26, docs, HIG, Swift, App Review, and app audits.
How to run each
io.github.heznpc/iconnect As a local MCP server: npm package
claude mcp add --transport stdio iconnect -- npx -y iconnect-mcpWWDC MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands 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: io.github.heznpc/iconnect · What it can do: WWDC MCP · Compare two other plugins
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.