Ext Ops Panel
Open dashboard
Comparison

Horizun Revit MCP vs io.github.microsoft/playwright-mcp

Horizun Revit MCP is an MCP server published by HorizunGroup. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.microsoft/playwright-mcp is an MCP server published by microsoft. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Cursor: cursor/plugins, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-13. 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
MarketplaceHorizun Revit MCPio.github.microsoft/playwright-mcp
Official MCP Registry Listed
Version: 4.0.0
Forks (GitHub): 8
Stars (GitHub): 85
Not marked · First seen
Listed
Version: 0.0.85
Downloads/month (npm): 32 246 268
Downloads/week (npm): 10 095 150
Forks (GitHub): 3 421
Stars (GitHub): 39 514
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 886
Stars (GitHub): 47 083
Not marked · First seen
Cursor: cursor/plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 701
Stars (GitHub): 16 155
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8771dc4666e7
Forks (GitHub): 3 421
Pulls (Docker Hub): 2 796 110
Stars (Docker Hub): 40
Stars (GitHub): 39 514
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

Horizun Revit MCP vs io.github.microsoft/playwright-mcp
FactHorizun Revit MCPio.github.microsoft/playwright-mcp
Marketplaces that list it (differs)1 (worse)5 (better)
Stars (GitHub) (differs)85 (worse)47 083 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub2 796 110
Forks (GitHub) (differs)8 (worse)4 886 (better)
Last release (differs)2026-11-02 (worse)2026-11-09 (better)
Where it runs (differs)On your machine (https://github.com/HorizunGroup/horizun-revit-mcp/releases/download/v4.0.0/horizun-revit-4.0.0.mcpb)On your machine (@playwright/mcp)
Transportstdiostdio
Tools it declares (differs)Not published23
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/horizungroup/horizun-revit-mcpgithub.com/microsoft/playwright-mcp
Changes in the last 7 days (differs)05
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

Horizun Revit MCP

In its own words, on Official MCP Registry:

Local Windows MCP for Revit 2023-2027. Run the Windows installer before connecting a client.

io.github.microsoft/playwright-mcp

In its own words, on Official MCP Registry:

Playwright Tools for MCP

How to run each

Horizun Revit MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.microsoft/playwright-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio playwright-mcp -- npx -y @playwright/mcp

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

Tools each declares

The marketplaces of Horizun Revit MCP publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Horizun Revit MCP · What it can do: io.github.microsoft/playwright-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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