Ext Ops Panel
Open dashboard
Comparison

foundryvtt-plugin vs GripForge

foundryvtt-plugin is a plugin bundle for AI coding tools published by Lauri Gates. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GripForge is an MCP server published by gripforgeai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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
Marketplacefoundryvtt-pluginGripForge
Community marketplace laurigates/claude-plugins Listed
Version: 1.4.0
Forks (GitHub): 6
Stars (GitHub): 59
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.150
Downloads/month (npm): 10 472
Downloads/week (npm): 3 450
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.1.149
Downloads/month (npm): 10 472
Downloads/week (npm): 3 450
Forks (GitHub): 1
Stars (GitHub): 4
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

foundryvtt-plugin vs GripForge
Factfoundryvtt-pluginGripForge
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)59 (better)4 (worse)
Forks (GitHub) (differs)6 (better)1 (worse)
Last release (differs)Not published2026-10-28
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/laurigates/claude-pluginsgithub.com/gripforgeai/mcp
Changes in the last 7 days (differs)220 or more
First seen (differs)2026-10-262026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

foundryvtt-plugin

In its own words, on Community GitHub marketplaces:

FoundryVTT module lifecycle - scaffold a v13 module (Vite + TS + bun), create + seed the repo, open the gitops adoption PR

GripForge

In its own words, on Official MCP Registry:

Turn prompts into production-ready game assets: animated characters, textures, terrain, VFX, HUD.

How to run each

foundryvtt-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add laurigates/claude-plugins
/plugin install foundryvtt-plugin@laurigates-claude-plugins

GripForge As a remote MCP server

Claude Code
claude mcp add --transport http gripforge https://gripforge.ai/mcp --header "x-api-key: <YOUR_X_API_KEY>"

Requires: GRIPFORGE_API_KEY (secret), x-api-key header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only GripForge has a remote endpoint we check. How we check endpoints

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 foundryvtt-plugin publish no settings it asks for, so we do not compare settings.

What it can do: foundryvtt-plugin · What it can do: GripForge · 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