Ext Ops Panel
Open dashboard
Comparison

Apify Remote vs exa

Apify Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). exa is a plugin bundle for AI coding tools published by exa-labs. Marketplaces we read that list it: 5 (Claude Code: claude-plugins-official, Official MCP Registry, Docker MCP Catalog, Claude: knowledge-work-plugins, Community GitHub marketplaces). 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
MarketplaceApify Remoteexa
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Listed
Version: sha256:d88edd571d98
Forks (GitHub): 401
Pulls (Docker Hub): 36 173
Stars (Docker Hub): 7
Stars (GitHub): 5 110
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
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

Apify Remote vs exa
FactApify Remoteexa
Marketplaces that list it (differs)1 (worse)5 (better)
Stars (GitHub) (differs)No figure on GitHub5 110
Pulls (Docker Hub) (differs)No figure on Docker Hub36 173
Forks (GitHub) (differs)No figure on GitHub401
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apify.com)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published2
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Parts of the bundle (differs)Not a bundle3
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/exa-labs/exa-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot checked yet

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

Apify Remote

In its own words, on Docker MCP Catalog:

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.

exa

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

Exa AI web search, deep research, and content extraction. Provides MCP tools and research skills for comprehensive web search, people discovery, company research, academic papers, and more.

How to run each

Apify Remote

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

Requires: APIFY_API_KEY (secret)

exa As a Claude Code plugin

Claude Code
/plugin install exa@claude-plugins-official

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

Tools each declares

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

Settings each asks for

Only Apify Remote asks for

  • APIFY_API_KEY (secret)

Only exa asks for

  • EXA_API_KEY (secret)

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

What it can do: Apify Remote · What it can do: exa · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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