Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs Lex API MX

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Lex API MX is an MCP server published by Julio-Patron. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceKagi SearchLex API MX
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 866
Stars (Docker Hub): 1
Stars (GitHub): 543
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 427
Forks (GitHub): 0
Stars (GitHub): 0
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

Kagi Search vs Lex API MX
FactKagi SearchLex API MX
Marketplaces that list it11
Stars (GitHub) (differs)543 (better)0 (worse)
Pulls (Docker Hub) (differs)19 866No figure on Docker Hub
Forks (GitHub) (differs)49 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/kagisearch)On your machine (lex-api-mx-mcp)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/kagisearch/kagimcpgithub.com/julio-patron/lexapi-mx
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11

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

Kagi Search

In its own words, on Docker MCP Catalog:

The Official Model Context Protocol (MCP) server for Kagi Search & other tools.

Lex API MX

In its own words, on Official MCP Registry:

Legislación federal mexicana vigente con fuente, checksum y vigencia para agentes de IA

How to run each

Kagi Search As a local MCP server: Docker image

Claude Code
claude mcp add --env "KAGI_API_KEY=<YOUR_KAGI_API_KEY>" --transport stdio kagisearch -- docker run -i --rm -e KAGI_API_KEY mcp/kagisearch

Requires: KAGI_API_KEY (secret)

Lex API MX As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LEX_API_MX_KEY=<YOUR_LEX_API_MX_KEY>" --transport stdio lex-api-mx -- uvx lex-api-mx-mcp

Requires: LEX_API_MX_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 Lex API MX publish no list of tools, so we do not compare tools.

Settings each asks for

Only Kagi Search asks for

  • KAGI_API_KEY (secret)
  • KAGI_SUMMARIZER_ENGINE

Only Lex API MX asks for

  • LEX_API_MX_BASE_URL
  • LEX_API_MX_KEY (secret)

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

What it can do: Kagi Search · What it can do: Lex API MX · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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