domscribe vs org.sylin/ghostlight
domscribe is a plugin bundle for AI coding tools published by patchorbit. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). org.sylin/ghostlight is an MCP server published by sylin.org. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
| Marketplace |  domscribe |  org.sylin/ghostlight |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.6.0 Forks (GitHub): 14 Stars (GitHub): 194 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.14 Downloads/month (npm): 2 350 Downloads/week (npm): 143 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | domscribe | org.sylin/ghostlight |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 194 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 14 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@domscribe/mcp) | On your machine (ghostlight) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle | 2 | 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/patchorbit/domscribe | github.com/sylin-org/ghostlight |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
domscribe
Domscribe bridges your running frontend and your code editor. Click any element in the browser to tell Claude what to change, or let Claude query any source location to see live props, state, and DOM — directly from the running app. Build-time stable IDs, deep runtime context via React fiber walking and Vue VNode inspection, framework-agnostic (React, Vue, Next.js, Nuxt), and zero production impact.
org.sylin/ghostlight
Visible local browser automation in signed-in Chromium, with optional policy and audit.
How to run each
domscribe As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install domscribe@claude-communityorg.sylin/ghostlight As a local MCP server: npm package
claude mcp add --transport stdio ghostlight -- npx -y ghostlightCommands 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: domscribe · What it can do: org.sylin/ghostlight · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.