Ext Ops Panel
Open dashboard
Comparison

mobile-canvas vs io.github.geeks-accelerator/animalhouse

mobile-canvas is a plugin bundle for AI coding tools published by Redth. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). io.github.geeks-accelerator/animalhouse is an MCP server published by geeks-accelerator. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacemobile-canvasio.github.geeks-accelerator/animalhouse
Copilot CLI: github/awesome-copilot Listed
Version: 0.1.6
Forks (GitHub): 16
Stars (GitHub): 162
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.2.0
Downloads/month (npm): 812
Downloads/week (npm): 357
Forks (GitHub): 0
Stars (GitHub): 3
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

mobile-canvas vs io.github.geeks-accelerator/animalhouse
Factmobile-canvasio.github.geeks-accelerator/animalhouse
Marketplaces that list it11
Stars (GitHub) (differs)162 (better)3 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last release (differs)Not published2026-10-22
Where it runs (differs)Installs as a plugin bundleRemote server (animalhouse.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/redth/mobile-canvas-ghcpgithub.com/geeks-accelerator/animal-house-ai-tamagotchi
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 38 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

mobile-canvas

In its own words, on Copilot CLI: github/awesome-copilot:

View, create, boot, and interact with local iOS simulators and Android emulators from a GitHub Copilot canvas. The plugin also exposes the same device controls to agents through MCP.

io.github.geeks-accelerator/animalhouse

In its own words, on Official MCP Registry:

A Tamagotchi for AI agents. Real-time care, permanent death, dozens of species, evolution.

How to run each

mobile-canvas

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

io.github.geeks-accelerator/animalhouse As a remote MCP server

Claude Code
claude mcp add --transport http animalhouse https://animalhouse.ai/mcp

Requires: ANIMALHOUSE_API_KEY (secret)

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

Only io.github.geeks-accelerator/animalhouse 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

The marketplaces of mobile-canvas publish no settings it asks for, so we do not compare settings.

What it can do: mobile-canvas · What it can do: io.github.geeks-accelerator/animalhouse · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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