Ext Ops Panel
Open dashboard
Comparison

summer vs dev.glbforge/glbforge

summer is a plugin bundle for AI coding tools published by SummerEngine. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). dev.glbforge/glbforge is an MCP server published by glbforge.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacesummerdev.glbforge/glbforge
Claude Code: claude-plugins-community Listed
Version: 2.5.1
Forks (GitHub): 6
Stars (GitHub): 75
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.0
Downloads/month (npm): 389
Downloads/week (npm): 47
Forks (GitHub): 1
Stars (GitHub): 2
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

summer vs dev.glbforge/glbforge
Factsummerdev.glbforge/glbforge
Marketplaces that list it11
Stars (GitHub) (differs)75 (better)2 (worse)
Forks (GitHub) (differs)6 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (summer-engine)On your machine (@glbforge/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)2Not published
Parts of the bundle (differs)83Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/summerengine/summergithub.com/glbforge/glbforge
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

summer

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

Summer turns Claude Code into a complete game-dev studio for Summer Engine, the AI-native game engine. Twenty-four auto-trigger skills cover the full pipeline, from brainstorm, design, scaffold, build, debug, ship. Also brings a 37-tool MCP bridge that lets Claude create scenes, run the game, read diagnostics, and import assets directly in your local engine. Say "make me an FPS" and it does.

dev.glbforge/glbforge

In its own words, on Official MCP Registry:

Make AI-generated 3D assets web-ready: budgets, SSIM-verified optimization, STL/USDZ export.

How to run each

summer As a Claude Code plugin

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

dev.glbforge/glbforge As a local MCP server: npm package

Claude Code
claude mcp add --env "MESHY_API_KEY=<YOUR_MESHY_API_KEY>" --transport stdio glbforge -- npx -y @glbforge/mcp

Requires: MESHY_API_KEY (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 summer publish no settings it asks for, so we do not compare settings.

What it can do: summer · What it can do: dev.glbforge/glbforge · 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. 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