Ext Ops Panel
Open dashboard
Comparison

blockbench-mcp vs io.github.kendall8388/keyframe

blockbench-mcp is a plugin bundle for AI coding tools published by Jason J. Gardner. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.kendall8388/keyframe is an MCP server published by kendall8388. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
Marketplaceblockbench-mcpio.github.kendall8388/keyframe
Community marketplace jasonjgardner/blockbench-mcp-project Listed
Version: 1.9.1
Forks (GitHub): 3
Stars (GitHub): 24
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.0
Downloads/month (npm): 1 732
Downloads/week (npm): 114
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.8.0
Downloads/month (npm): 1 732
Downloads/week (npm): 114
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

blockbench-mcp vs io.github.kendall8388/keyframe
Factblockbench-mcpio.github.kendall8388/keyframe
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)24No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (localhost/bb-mcp)On your machine (keyframe-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)18Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/jasonjgardner/blockbench-mcp-projectgithub.com/kendall8388/keyframe-it
Changes in the last 7 days (differs)20
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)not checked yetno 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

blockbench-mcp

In its own words, on Community GitHub marketplaces:

Blockbench desktop and headless MCP servers with skills for modeling, texturing, PBR, particles, animation, and Hytale.

io.github.kendall8388/keyframe

In its own words, on Official MCP Registry:

Animate 2D skeletons in Keyframe.it, pixel sprites in Sprite Puppeteer, 3D rigs in MeshForge.

How to run each

blockbench-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add jasonjgardner/blockbench-mcp-project
/plugin install blockbench-mcp@blockbench-mcp-project

io.github.kendall8388/keyframe As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio keyframe -- npx -y keyframe-mcp

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: blockbench-mcp · What it can do: io.github.kendall8388/keyframe · 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. Package data comes from the public npm registry (registry.npmjs.org). 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