Ext Ops Panel
Open dashboard
Comparison

exa vs LexAPI

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). LexAPI is an MCP server published by Lex-API. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceexaLexAPI
Claude Code: claude-plugins-official Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 188
Downloads/week (npm): 40
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:d88edd571d98
Forks (GitHub): 401
Pulls (Docker Hub): 36 257
Stars (Docker Hub): 7
Stars (GitHub): 5 110
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 3.4.1
Forks (GitHub): 401
Stars (GitHub): 5 110
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

exa vs LexAPI
FactexaLexAPI
Marketplaces that list it (differs)5 (better)1 (worse)
Stars (GitHub) (differs)5 110 (better)3 (worse)
Pulls (Docker Hub) (differs)36 257No figure on Docker Hub
Forks (GitHub) (differs)401 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineOn your machine (@lexapi/mcp)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/exa-labs/exa-mcp-servergithub.com/lex-api/lexapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

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.

LexAPI

In its own words, on Official MCP Registry:

Search EUR-Lex, fetch parsed EU legislation and case law, explore the citation graph.

How to run each

exa As a Claude Code plugin

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

LexAPI As a local MCP server: npm package

Claude Code
claude mcp add --env "LEXAPI_API_KEY=<YOUR_LEXAPI_API_KEY>" --transport stdio lexapi-mcp -- npx -y @lexapi/mcp

Requires: LEXAPI_API_KEY (secret)

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

Tools each declares

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

Settings each asks for

Only exa asks for

  • EXA_API_KEY (secret)

Only LexAPI asks for

  • LEXAPI_API_KEY (secret)
  • LEXAPI_BASE_URL

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

What it can do: exa · What it can do: LexAPI · Compare two other plugins

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 Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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