tiny-pet vs PilotGentic
tiny-pet is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
tiny-pet is a plugin bundle for AI coding tools published by Douglas Cabrera. No marketplace we read lists it any more. PilotGentic is an MCP server published by pilotgentic.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace cabrera-evil/claude-pet | Removed on 2026-10-18 Version: 0.11.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 72 Downloads/week (npm): 15 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 | tiny-petno longer listed · | PilotGentic |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@pilotgentic/mcp-server) |
| Transport (differs) | Not stated | 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/cabrera-evil/claude-pet | github.com/1genadam/pilotgentic |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tiny-pet
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Your own Claude Code token consumption, with nudges on turns, cost and model mix. Entirely local.
-
A persistent Tamagotchi creature that lives in your Claude Code status line — evolves through emoji stages, has session-level moods, and can die from neglect, leaving an egg with…
-
Register a Claude Code session with Paseo so it shows up in the app and you can continue it there.
-
Claude Code is great, but treating every prompt with full context is too expensive. I built Claude_Meister as an MCP plugin to dynamically route tasks and score memory, dropping…
-
End-to-end skill for creating a Claude Code plugin: scaffold, build, test, host, and submit to the official Anthropic marketplace.
-
A la carte toolkit for Claude Code. Best practices, persistent memory, and agent-team planning — pick what fits your project.
What each says it does
tiny-pet
A tiny Claude pet with its own little computer that works alongside you in Claude Code.
PilotGentic
macOS desktop control for Claude: click, type, screenshot, AX tree, browser control, agentic loops.
How to run each
tiny-pet
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PilotGentic As a local MCP server: npm package
claude mcp add --transport stdio pilotgentic -- npx -y @pilotgentic/mcp-server
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: tiny-pet · What it can do: PilotGentic · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.