Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs Lex API MX

Needle Remote is an MCP server published by docker. 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-14. 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
MarketplaceNeedle RemoteLex API MX
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
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

Needle Remote vs Lex API MX
FactNeedle RemoteLex API MX
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (mcp.needle.app/mcp)On your machine (lex-api-mx-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/julio-patron/lexapi-mx
Changes in the last 7 days (differs)02
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

Needle Remote

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

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

Needle Remote As a remote MCP server

Claude Code
claude mcp add --transport http needle https://mcp.needle.app/mcp

Requires: NEEDLE_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

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Needle Remote asks for

  • NEEDLE_API_KEY (secret)

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: Needle Remote · 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