Ghost vs ultranix-mcp
Ghost is an MCP server published by NORTHTEKDevs. Marketplaces we read that list it: 1 (Official MCP Registry). ultranix-mcp is an MCP server published by jxoesneon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Ghost |  ultranix-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.23.4 Forks (GitHub): 4 Stars (GitHub): 28 Not marked · First seen |
Listed Version: 1.4.0 Forks (GitHub): 1 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 | Ghost | ultranix-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (https://github.com/NORTHTEKDevs/ghost/releases/download/v0.23.4/ghost-windows-x64.mcpb) | On your machine (ghcr.io/jxoesneon/ultranix-mcp:1.4.0) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/northtekdevs/ghost | github.com/jxoesneon/ultranix-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
Ghost
Verified desktop control for agents on Windows and Linux: apps with no API, windows, shell, browser.
ultranix-mcp
Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard
How to run each
Ghost
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: GHOST_VISION_API_KEY (secret)
ultranix-mcp As a local MCP server: Docker image
claude mcp add --env "ULTRANIX_MCP_API_KEY=<YOUR_ULTRANIX_MCP_API_KEY>" --env "ULTRANIX_MCP_AUDIT_SECRET=<YOUR_ULTRANIX_MCP_AUDIT_SECRET>" --env "ULTRANIX_MCP_HISTORY_SECRET=<YOUR_ULTRANIX_MCP_HISTORY_SECRET>" --env "ULTRANIX_MCP_SENTRY_DSN=<YOUR_ULTRANIX_MCP_SENTRY_DSN>" --transport stdio ultranix-mcp -- docker run -i --rm -e ULTRANIX_MCP_API_KEY -e ULTRANIX_MCP_AUDIT_SECRET -e ULTRANIX_MCP_HISTORY_SECRET -e ULTRANIX_MCP_SENTRY_DSN ghcr.io/jxoesneon/ultranix-mcp:1.4.0Requires: ULTRANIX_MCP_API_KEY (secret), ULTRANIX_MCP_AUDIT_SECRET (secret), ULTRANIX_MCP_HISTORY_SECRET (secret), ULTRANIX_MCP_SENTRY_DSN (secret)
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
Only Ghost asks for
GHOST_VISION_API_KEY (secret)
Only ultranix-mcp asks for
ULTRANIX_MCP_API_KEY (secret)ULTRANIX_MCP_API_KEY_EXPIRESULTRANIX_MCP_API_KEY_FILEULTRANIX_MCP_AUDIT_SECRET (secret)ULTRANIX_MCP_HISTORY_SECRET (secret)ULTRANIX_MCP_SENTRY_DSN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Ghost · What it can do: ultranix-mcp · Compare two other plugins
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.