Ext Ops Panel
Open dashboard
Comparison

playhtml vs ui-ticket-mcp

playhtml is a plugin bundle for AI coding tools published by Spencer Chang. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ui-ticket-mcp is an MCP server published by 0ics-srls. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplaceplayhtmlui-ticket-mcp
Community marketplace spencerc99/playhtml Listed
Version: 1.0.0
Forks (GitHub): 20
Stars (GitHub): 522
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.2
Downloads/month (PyPI): 532
Downloads/week (PyPI): 117
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.6.2
Downloads/month (PyPI): 532
Downloads/week (PyPI): 117
Forks (GitHub): 1
Stars (GitHub): 9
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

playhtml vs ui-ticket-mcp
Factplayhtmlui-ticket-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)522 (better)9 (worse)
Forks (GitHub) (differs)20 (better)1 (worse)
Last release (differs)Not published2026-11-07
Where it runs (differs)Installs as a plugin bundleOn your machine (ui-ticket-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITCC-BY-NC-4.0
Repository (differs)github.com/spencerc99/playhtmlgithub.com/0ics-srls/ui-ticket-mcp_public
Changes in the last 7 days22
First seen (differs)2026-11-062026-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

playhtml

In its own words, on Community GitHub marketplaces:

Skill for building collaborative, real-time HTML elements with playhtml. Covers APIs, data types, and common mistakes.

ui-ticket-mcp

In its own words, on Official MCP Registry:

Human-to-AI code review bridge. Review UI in the browser, AI agents fix code via MCP.

How to run each

playhtml As a Claude Code plugin

Claude Code
/plugin marketplace add spencerc99/playhtml
/plugin install playhtml@playhtml

ui-ticket-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "PROJECT_ROOT=<YOUR_PROJECT_ROOT>" --transport stdio ui-ticket-mcp -- uvx ui-ticket-mcp

Requires: PROJECT_ROOT

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

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

What it can do: playhtml · What it can do: ui-ticket-mcp · 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 Python Package Index (pypi.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