Ext Ops Panel
Open dashboard
Comparison

BibiGPT vs Perplexity API Platform

BibiGPT is a plugin bundle for AI coding tools published by BibiGPT. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Perplexity API Platform is an MCP server published by perplexity.ai. Marketplaces we read that list it: 4 (Official MCP Registry, Docker MCP Catalog, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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
MarketplaceBibiGPTPerplexity API Platform
Official MCP Registry Removed on 2026-10-28
Version: 1.0.0
Forks (GitHub): 9
Stars (GitHub): 131
Not marked · First seen
Listed
Version: 1.2.1
Downloads/month (npm): 87 686
Downloads/week (npm): 18 636
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:7816f45a6f26
Forks (GitHub): 388
Pulls (Docker Hub): 81 028
Stars (Docker Hub): 17
Stars (GitHub): 2 589
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.3.0
Downloads/month (npm): 87 686
Downloads/week (npm): 18 636
Forks (GitHub): 389
Stars (GitHub): 2 592
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

BibiGPT vs Perplexity API Platform
FactBibiGPTPerplexity API Platform
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)133 (worse)2 592 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub81 028
Forks (GitHub) (differs)9 (worse)389 (better)
Last release (differs)2026-10-27 (better)2026-10-17 (worse)
Where it runs (differs)Remote server (bibigpt.co/api/mcp)On your machine (@perplexity-ai/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published3
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)52
LicenceMITMIT
Repository (differs)github.com/jimmylv/bibigpt-skillgithub.com/ppl-ai/modelcontextprotocol
Changes in the last 7 days (differs)60
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-25no 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

BibiGPT

In its own words, on Community GitHub marketplaces:

Video summarizer agent skill / Codex plugin for YouTube, Bilibili, and podcasts via BibiGPT.

Perplexity API Platform

In its own words, on Official MCP Registry:

Real-time web search, reasoning, and research through Perplexity's API

How to run each

BibiGPT As a Codex plugin

Codex
codex plugin marketplace add jimmylv/bibigpt-skill

Perplexity API Platform As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio perplexity-api-platform -- npx -y @perplexity-ai/mcp-server

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

Only BibiGPT has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of BibiGPT publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: BibiGPT · What it can do: Perplexity API Platform · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). 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