Ext Ops Panel
Open dashboard
Comparison

Perplexity API Platform vs Jobbi Agent Gigs

Perplexity API Platform is an MCP server published by perplexity.ai. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). Jobbi Agent Gigs is an MCP server published by jobbi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplacePerplexity API PlatformJobbi Agent Gigs
Official MCP Registry Listed
Version: 1.2.1
Downloads/month (npm): 102 467
Downloads/week (npm): 16 084
Not marked · First seen
Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:7816f45a6f26
Forks (GitHub): 384
Pulls (Docker Hub): 80 327
Stars (Docker Hub): 17
Stars (GitHub): 2 578
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

Perplexity API Platform vs Jobbi Agent Gigs
FactPerplexity API PlatformJobbi Agent Gigs
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)2 578 (better)0 (worse)
Pulls (Docker Hub) (differs)80 327No figure on Docker Hub
Forks (GitHub) (differs)384 (better)0 (worse)
Last release (differs)2026-10-17 (better)2026-10-14 (worse)
Where it runs (differs)On your machine (@perplexity-ai/mcp-server)Remote server (jobbi.org/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ppl-ai/modelcontextprotocolgithub.com/agenticgigs/jobbi-mcp
Changes in the last 7 days (differs)45
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 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

In its own words, on Official MCP Registry:

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

Jobbi Agent Gigs

In its own words, on Official MCP Registry:

Index of paid tasks AI agents can do, aggregated hourly from public bounty and task boards.

How to run each

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

Jobbi Agent Gigs As a remote MCP server

Claude Code
claude mcp add --transport http gigs https://jobbi.org/mcp

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

Only Jobbi Agent Gigs has a remote endpoint we check. How we check endpoints

Tools each declares

Only Perplexity API Platform has

  • perplexity_ask
  • perplexity_reason
  • perplexity_research

Only Jobbi Agent Gigs has

  • find_jobs
  • get_gig
  • list_gigs
  • list_sources

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Jobbi Agent Gigs as of 2026-10-18). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

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

What it can do: Perplexity API Platform · What it can do: Jobbi Agent Gigs · 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. 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.

Where the data comes from: how the catalog is built