Ext Ops Panel
Open dashboard
Comparison

Prism — Crossdeck vs Umami Compass

Prism — Crossdeck is an MCP server published by cross-deck.com. Marketplaces we read that list it: 1 (Official MCP Registry). Umami Compass is an MCP server published by webcredo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplacePrism — CrossdeckUmami Compass
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 222
Downloads/week (npm): 41
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.5.1
Downloads/month (npm): 274
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
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

Prism — Crossdeck vs Umami Compass
FactPrism — CrossdeckUmami Compass
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.cross-deck.com/mcp)On your machine (umami-compass)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 110, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/crossdeckhq/crossdeck-prismgithub.com/webcredo/umami-compass
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

Prism — Crossdeck

In its own words, on Official MCP Registry:

Ask your app anything — revenue, errors, read-cost, growth — and get rendered charts back.

Umami Compass

In its own words, on Official MCP Registry:

Secure Umami Analytics MCP server for Cloud and self-hosted deployments

How to run each

Prism — Crossdeck As a remote MCP server

Claude Code
claude mcp add --transport http prism https://api.cross-deck.com/mcp

Requires: CROSSDECK_SECRET_KEY (secret)

Umami Compass As a local MCP server: npm package

Claude Code
claude mcp add --env "UMAMI_ACCESS_TOKEN=<YOUR_UMAMI_ACCESS_TOKEN>" --env "UMAMI_API_KEY=<YOUR_UMAMI_API_KEY>" --env "UMAMI_PASSWORD=<YOUR_UMAMI_PASSWORD>" --transport stdio umami-compass -- npx -y umami-compass

Requires: UMAMI_ACCESS_TOKEN (secret), UMAMI_API_KEY (secret), UMAMI_PASSWORD (secret)

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

Only Prism — Crossdeck has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Prism — Crossdeck asks for

  • CROSSDECK_API_BASE
  • CROSSDECK_SECRET_KEY (secret)

Only Umami Compass asks for

  • UMAMI_ACCESS_TOKEN (secret)
  • UMAMI_API_KEY (secret)
  • UMAMI_API_URL
  • UMAMI_MAX_RESPONSE_BYTES
  • UMAMI_PASSWORD (secret)
  • UMAMI_TEAM_IDS
  • UMAMI_TOOLSETS
  • UMAMI_URL
  • UMAMI_USERNAME
  • UMAMI_WEBSITE_IDS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Prism — Crossdeck · What it can do: Umami Compass · 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.

Where the data comes from: how the catalog is built