Ext Ops Panel
Open dashboard
Comparison

SolidWorks vs MCP for Adobe Premiere Pro

SolidWorks is an MCP server published by hjbaard. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). MCP for Adobe Premiere Pro is an MCP server published by leancoderkavy. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), 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
MarketplaceSolidWorksMCP for Adobe Premiere Pro
Official MCP Registry Listed
Version: 0.19.0
Downloads/month (PyPI): 2 916
Downloads/week (PyPI): 1 440
Forks (GitHub): 6
Stars (GitHub): 28
Not marked · First seen
Listed
Version: 1.30.0
Downloads/month (npm): 19 974
Downloads/week (npm): 6 732
Forks (GitHub): 93
Stars (GitHub): 517
Not marked · First seen
PyPI (MCP servers) Listed
Version: 0.19.0
Downloads/month (PyPI): 2 916
Downloads/week (PyPI): 1 440
Forks (GitHub): 6
Stars (GitHub): 28
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 1.30.0
Downloads/month (npm): 19 974
Downloads/week (npm): 6 732
Forks (GitHub): 93
Stars (GitHub): 517
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

SolidWorks vs MCP for Adobe Premiere Pro
FactSolidWorksMCP for Adobe Premiere Pro
Marketplaces that list it (differs)2 (worse)3 (better)
Stars (GitHub) (differs)28 (worse)517 (better)
Forks (GitHub) (differs)6 (worse)93 (better)
Last release (differs)2026-11-03 (worse)2026-11-08 (better)
Where it runs (differs)On your machine (solidworks-mcp)On your machine (premiere-pro-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle3
LicenceMITMIT
Repository (differs)github.com/hjbaard/solidworks-mcpgithub.com/leancoderkavy/premiere-pro-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-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

SolidWorks

In its own words, on Official MCP Registry:

Model, measure and verify parametric parts and assemblies in a running SolidWorks (Windows).

MCP for Adobe Premiere Pro

In its own words, on Official MCP Registry:

Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.

How to run each

SolidWorks As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio solidworks-mcp -- uvx solidworks-mcp

MCP for Adobe Premiere Pro As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio premiere-pro -- npx -y premiere-pro-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: SolidWorks · What it can do: MCP for Adobe Premiere Pro · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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