App-Store-Builder vs Apper MCP Connector
App-Store-Builder is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). Apper MCP Connector is an MCP server published by apperhq. 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 |  Apper MCP Connector | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | App-Store-Builder | Apper MCP Connector |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app-store-builder-mcp.vercel.app/api/mcp) | Remote server (mcp.apper.io/v1/connect) |
| Transport (differs) | SSE | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/apperhq/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (5 days ago) | Responded 18 h ago |
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
App-Store-Builder
Extension bundler packaging plugins for AI agent ecosystems.
Apper MCP Connector
Build and update complete applications in Apper through AI assistants using MCP.
How to run each
App-Store-Builder As a remote MCP server
claude mcp add --transport sse app-store-builder https://app-store-builder-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Apper MCP Connector As a remote MCP server
claude mcp add --transport http apper-mcp https://mcp.apper.io/v1/connectCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Apper MCP Connector responded at the last daily check. How we check endpoints
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: App-Store-Builder · What it can do: Apper MCP Connector · 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.