Ext Ops Panel
Open dashboard
Comparison

sailfishos-dev vs io.github.engineerdeep/buildtree

sailfishos-dev is a plugin bundle for AI coding tools published by juergenbr. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.engineerdeep/buildtree is an MCP server published by engineerdeep. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacesailfishos-devio.github.engineerdeep/buildtree
Claude Code: claude-plugins-community Listed
Version: 3047b94
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 710
Downloads/week (npm): 49
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

sailfishos-dev vs io.github.engineerdeep/buildtree
Factsailfishos-devio.github.engineerdeep/buildtree
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@buildtree/mcp)
Transport (differs)Not statedstdio
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)Not statedMIT
Repository (differs)github.com/juergenbr/claude-plugin-sailfishos-devgithub.com/engineerdeep/buildtree-mcp
Changes in the last 7 days (differs)04
First seen2026-10-112026-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

sailfishos-dev

In its own words, on Claude Code: claude-plugins-community:

A Claude Code skill that turns Claude into a SailfishOS app development expert, covering Silica QML components, sfdk build/deploy commands, design guidelines, Harbour store submission, and platform APIs.

io.github.engineerdeep/buildtree

In its own words, on Official MCP Registry:

Upload Android and iOS builds to buildtree and get install links, QR codes and tester feedback.

How to run each

sailfishos-dev As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sailfishos-dev@claude-community

io.github.engineerdeep/buildtree As a local MCP server: npm package

Claude Code
claude mcp add --env "BUILDTREE_TOKEN=<YOUR_BUILDTREE_TOKEN>" --transport stdio buildtree -- npx -y @buildtree/mcp

Requires: BUILDTREE_TOKEN (secret)

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

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

What it can do: sailfishos-dev · What it can do: io.github.engineerdeep/buildtree · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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