Ext Ops Panel
Open dashboard
Comparison

campy vs Flyto2 Runtime

campy is a plugin bundle for AI coding tools published by dropdevrahul. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Flyto2 Runtime is an MCP server published by flytohub. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplacecampyFlyto2 Runtime
Community marketplace dropdevrahul/campy Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.8
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 1 (last published figure)
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

campy vs Flyto2 Runtime
FactcampyFlyto2 Runtime
Marketplaces that list it11
Stars (GitHub) (differs)141 (last published figure)
Forks (GitHub) (differs)00 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleNot stated
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)8Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/dropdevrahul/campygithub.com/flytohub/flyto-runtime
Changes in the last 7 days00
First seen (differs)2026-10-162026-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

campy

In its own words, on Community GitHub marketplaces:

Animated terminal pet that reacts to your coding (hooks + statusline + slash commands)

Flyto2 Runtime

In its own words, on Official MCP Registry:

Self-hosted MCP runtime for ChatGPT to edit files, run commands, and test local projects.

How to run each

campy As a Claude Code plugin

Claude Code
/plugin marketplace add dropdevrahul/campy
/plugin install campy@campy

Flyto2 Runtime

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: campy · What it can do: Flyto2 Runtime · 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.

Where the data comes from: how the catalog is built