GC AI vs Lex API MX
GC AI is a plugin bundle for AI coding tools published by GC-AI-Inc. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). Lex API MX is an MCP server published by Julio-Patron. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. 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
| Marketplace |  GC AI |  Lex API MX |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 377 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.4.2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 377 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | GC AI | Lex API MX |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | Remote server (app.gc.ai/api/mcp) | On your machine (lex-api-mx-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/gc-ai-inc/gc-ai-claude-plugin | github.com/julio-patron/lexapi-mx |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 46 h ago returned HTTP 405 | no 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
GC AI
Work in your GC AI legal knowledge base from Claude: upload documents, run review playbooks, and ask questions grounded in your own files, all as you.
Lex API MX
Legislación federal mexicana vigente con fuente, checksum y vigencia para agentes de IA
How to run each
GC AI As a Claude Code plugin
/plugin install gc-ai@claude-plugins-officialLex API MX As a local MCP server: PyPI package
claude mcp add --env "LEX_API_MX_KEY=<YOUR_LEX_API_MX_KEY>" --transport stdio lex-api-mx -- uvx lex-api-mx-mcpRequires: LEX_API_MX_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GC AI has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of GC AI publish no settings it asks for, so we do not compare settings.
What it can do: GC AI · What it can do: Lex API MX · 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 public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.