Ext Ops Panel
Open dashboard
Comparison

Perplexity vs thinking-partner

Perplexity is an MCP server published by perplexityai. Marketplaces we read that list it: 1 (Docker MCP Catalog). thinking-partner is a plugin bundle for AI coding tools published by mattnowdev. 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
MarketplacePerplexitythinking-partner
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: 1.0.0
Forks (GitHub): 17
Stars (GitHub): 206
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 thinking-partner
FactPerplexitythinking-partner
Marketplaces that list it11
Stars (GitHub) (differs)2 562 (better)206 (worse)
Pulls (Docker Hub) (differs)79 799No figure on Docker Hub
Forks (GitHub) (differs)380 (better)17 (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: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)MITNot stated
Repository (differs)github.com/ppl-ai/modelcontextprotocolgithub.com/mattnowdev/thinking-partner
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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.

thinking-partner

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

A deterministic thinking partner that challenges assumptions and applies 150+ mental models across 17 disciplines to sharpen decisions, solve problems, and think more clearly. Features include orientation detection that diagnoses 6 thinking states with targeted interventions, a structured 6-step workflow from diagnosis to synthesis, 7 complementary cognitive operation pairs, and explicit anti-patterns to avoid common reasoning failures. Works as a sparring session, not a lecture, asks one question at a time, names the model being applied, and challenges where it matters.

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)

thinking-partner

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 thinking-partner publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Perplexity · What it can do: thinking-partner · 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