Ext Ops Panel
Open dashboard
Comparison

Perplexity vs nexus-the-cartographer

Perplexity is an MCP server published by perplexityai. Marketplaces we read that list it: 1 (Docker MCP Catalog). nexus-the-cartographer is a plugin bundle for AI coding tools published by kronosderet. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplacePerplexitynexus-the-cartographer
Docker MCP Catalog Listed
Version: sha256:7816f45a6f26
Forks (GitHub): 380
Pulls (Docker Hub): 79 799
Stars (Docker Hub): 17
Stars (GitHub): 2 562
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 4.9.1
Forks (GitHub): 1
Stars (GitHub): 2
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

Perplexity vs nexus-the-cartographer
FactPerplexitynexus-the-cartographer
Marketplaces that list it11
Stars (GitHub) (differs)2 562 (better)2 (worse)
Pulls (Docker Hub) (differs)79 799No figure on Docker Hub
Forks (GitHub) (differs)380 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/perplexity-ask)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle10
LicenceMITMIT
Repository (differs)github.com/ppl-ai/modelcontextprotocolgithub.com/kronosderet/nexus
Changes in the last 7 days00
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

Perplexity

In its own words, on Docker MCP Catalog:

Connector for Perplexity API, to enable real-time, web-wide research.

nexus-the-cartographer

In its own words, on Claude Code: claude-plugins-community:

AI Cowork metabrain with Knowledge Graph, Thought Stack, Fuel Intelligence, and local AI Overseer. 20 native MCP tools for persistent session memory across Claude instances.

How to run each

Perplexity As a local MCP server: Docker image

Claude Code
claude mcp add --env "PERPLEXITY_API_KEY=<YOUR_PERPLEXITY_API_KEY>" --transport stdio perplexity-ask -- docker run -i --rm -e PERPLEXITY_API_KEY mcp/perplexity-ask

Requires: PERPLEXITY_API_KEY (secret)

nexus-the-cartographer

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

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

Tools each declares

The marketplaces of nexus-the-cartographer publish no list of tools, so we do not compare tools.

Settings each asks for

Only Perplexity asks for

  • PERPLEXITY_API_KEY (secret)

Only nexus-the-cartographer asks for

  • NEXUS_STANDALONE

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

What it can do: Perplexity · What it can do: nexus-the-cartographer · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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