Ext Ops Panel
Open dashboard
Comparison

mlx-vlm-skills vs LLM Configurator

mlx-vlm-skills is a plugin bundle for AI coding tools published by MLX-VLM contributors. Marketplaces we read that list it: 1 (Community GitHub marketplaces). LLM Configurator is an MCP server published by aikuba. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplacemlx-vlm-skillsLLM Configurator
Community marketplace blaizzy/mlx-vlm Listed
Version: 0.1.0
Forks (GitHub): 858
Stars (GitHub): 5 656
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

mlx-vlm-skills vs LLM Configurator
Factmlx-vlm-skillsLLM Configurator
Marketplaces that list it11
Stars (GitHub) (differs)5 656No figure on GitHub
Forks (GitHub) (differs)858No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/blaizzy/mlx-vlmgithub.com/aikuba/llmconfigurator.com
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

mlx-vlm-skills

In its own words, on Community GitHub marketplaces:

Skills for MLX-VLM: command-line and server inference, convert/quantize, adding new models, benchmarking, contributing, cached-model listing, and reproducible GitHub issues.

LLM Configurator

In its own words, on Official MCP Registry:

Read-only: which local LLMs a GPU or Mac can run - VRAM fit, tokens/sec, model specs.

How to run each

mlx-vlm-skills As a Claude Code plugin

Claude Code
/plugin marketplace add blaizzy/mlx-vlm
/plugin install mlx-vlm-skills@mlx-vlm

LLM Configurator As a remote MCP server

Claude Code
claude mcp add --transport http llmconfigurator https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp

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

Only LLM Configurator 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

Neither one's marketplaces publish the settings it asks for.

What it can do: mlx-vlm-skills · What it can do: LLM Configurator · 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. 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