Ext Ops Panel
Open dashboard
Comparison

WebMCP Kit vs Glif

WebMCP Kit is a plugin bundle for AI coding tools published by nekuda. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. 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
MarketplaceWebMCP KitGlif
Community marketplace nekuda-ai/webmcp-kit Listed
Version: 0.10.0
Forks (GitHub): 8
Stars (GitHub): 51
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 32
Stars (GitHub): 217
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3f93ddceeb99
Forks (GitHub): 32
Pulls (Docker Hub): 20 322
Stars (Docker Hub): 2
Stars (GitHub): 217
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

WebMCP Kit vs Glif
FactWebMCP KitGlif
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)51 (worse)217 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub20 322
Forks (GitHub) (differs)8 (worse)32 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.nekuda.ai/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published10
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)511
LicenceMITMIT
Repository (differs)github.com/nekuda-ai/webmcp-kitgithub.com/glifxyz/glif-mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-302026-10-11
Endpoint at the last check (differs)Responded 2 h agoResponded less than an hour 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

WebMCP Kit

In its own words, on Community GitHub marketplaces:

Add WebMCP tools to a web app: read the repo, propose a reviewable tool plan, implement against @nekuda/webmcp-sdk, and verify the tools in a browser — or connect the tools a site already has, without rebuilding them.

Glif

In its own words, on Official MCP Registry:

Generate images, video, and audio with Glif's media-generation agent

How to run each

WebMCP Kit As a Claude Code plugin

Claude Code
/plugin marketplace add nekuda-ai/webmcp-kit
/plugin install webmcp-kit@nekuda

Glif As a remote MCP server

Claude Code
claude mcp add --transport http glif https://glif.app/api/mcp

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of WebMCP Kit publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of WebMCP Kit publish no settings it asks for, so we do not compare settings.

What it can do: WebMCP Kit · What it can do: Glif · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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