Emuluxe vs io.github.aitor-alt/pixel-squads
Emuluxe is an MCP server published by Emuluxe. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.aitor-alt/pixel-squads is an MCP server published by aitor-alt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Emuluxe | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Downloads/month (npm): 392 Downloads/week (npm): 360 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 77 Downloads/week (npm): 11 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 | Emuluxe | io.github.aitor-alt/pixel-squads |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.emuluxe.com/api/mcp) | On your machine (pixelsquads-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/emuluxe/emuluxe-mcp | github.com/aitor-alt/pixel |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
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
Emuluxe
Launch and verify high-fidelity mobile simulations from an AI agent.
io.github.aitor-alt/pixel-squads
MCP Server for Pixel Squads — observe your AI agents as pixel-art characters in a live office
How to run each
Emuluxe As a remote MCP server
claude mcp add --transport http emuluxe https://app.emuluxe.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: EMULUXE_TOKEN (secret), Authorization header
io.github.aitor-alt/pixel-squads As a local MCP server: npm package
claude mcp add --env "PIXEL_SQUADS_TOKEN=<YOUR_PIXEL_SQUADS_TOKEN>" --transport stdio pixel-squads -- npx -y pixelsquads-mcp-serverRequires: PIXEL_SQUADS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Emuluxe has a remote endpoint we 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
Only Emuluxe asks for
EMULUXE_API_URLEMULUXE_DEFAULT_NETWORKEMULUXE_IDEEMULUXE_TOKEN (secret)
Only io.github.aitor-alt/pixel-squads asks for
PIXEL_SQUADS_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Emuluxe · What it can do: io.github.aitor-alt/pixel-squads · 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.