Perplexity API Platform vs io.github.jshelley/briefings
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). io.github.jshelley/briefings is an MCP server published by jshelley. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.1 Downloads/month (npm): 87 686 Downloads/week (npm): 18 636 Not marked · First seen |
Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:7816f45a6f26 Forks (GitHub): 388 Pulls (Docker Hub): 81 004 Stars (Docker Hub): 17 Stars (GitHub): 2 589 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | 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 |
Not listed |
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 | Perplexity API Platform | io.github.jshelley/briefings |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 592 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 81 004 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 389 (better) | 0 (worse) |
| Last release (differs) | 2026-10-17 | Not published |
| Where it runs (differs) | On your machine (@perplexity-ai/mcp-server) | Remote server (briefing-service.wholemind.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ppl-ai/modelcontextprotocol | github.com/jshelley/briefing-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 47 h ago |
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 API Platform
Real-time web search, reasoning, and research through Perplexity's API
io.github.jshelley/briefings
Hourly ranked news (AI, markets, sports, world): JSON, e-ink pages, Morning Paper PDF; 25 free/day
How to run each
Perplexity API Platform As a local MCP server: npm package
claude mcp add --transport stdio perplexity-api-platform -- npx -y @perplexity-ai/mcp-server
io.github.jshelley/briefings As a remote MCP server
claude mcp add --transport http briefings https://briefing-service.wholemind.workers.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: BRIEFING_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.jshelley/briefings has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.jshelley/briefings publish no list of tools, so we do not compare tools.
Settings each asks for
Only Perplexity API Platform asks for
PERPLEXITY_API_KEY (secret)PERPLEXITY_TIMEOUT_MS
Only io.github.jshelley/briefings asks for
BRIEFING_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Perplexity API Platform · What it can do: io.github.jshelley/briefings · Compare two other plugins
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). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.