Lex API MX — servidor MCP
Servidor Model Context Protocol que conecta Claude Desktop, Claude Code, Cursor o cualquier agente MCP con la legislación federal mexicana vigente de Lex API MX.
El servidor es un adaptador ligero y de código abierto (MIT): no contiene el corpus. Cada llamada consulta la API de Lex API MX con tu clave y devuelve el paquete normativo tal cual, con cita canónica, vigencia, fuente oficial y checksum SHA-256 del texto.
Herramientas
| Herramienta | Endpoint | Para qué |
|---|---|---|
resolve_legal_citation |
POST /api/v1/resolve |
Resolver una cita o situación a un paquete normativo verificable. |
search_mexican_law |
GET /api/v1/articulos/search |
Buscar artículos vigentes por texto, norma o materia. |
get_norm_structure |
GET /api/v1/normas/{slug}/estructura |
Recorrer el árbol de una norma. |
Todas exigen fecha ("vigente" o YYYY-MM-DD). Las de búsqueda y resolución
exigen además jurisdiccion; hoy la única cobertura es "federal".
Instalación
Requiere uv y una clave de Lex API MX. El plan gratuito incluye 500 créditos al mes: crea tu cuenta con tu correo y genera la clave en lexapi.mx/#cuenta.
{
"mcpServers": {
"lex-api-mx": {
"command": "uvx",
"args": ["lex-api-mx-mcp"],
"env": { "LEX_API_MX_KEY": "tu_clave" }
}
}
}
- Claude Desktop: Settings → Developer → Edit Config y pega el bloque
anterior en
claude_desktop_config.json; reinicia la aplicación. - Claude Code:
claude mcp add lex-api-mx --env LEX_API_MX_KEY=tu_clave -- uvx lex-api-mx-mcp - Cursor: el mismo bloque en
~/.cursor/mcp.json(global) o.cursor/mcp.json(proyecto).
Pruébalo preguntando: ¿Cuáles son las causas de rescisión de la relación de trabajo sin responsabilidad para el patrón? Cita el artículo exacto.
Variables de entorno
| Variable | Obligatoria | Valor por defecto |
|---|---|---|
LEX_API_MX_KEY |
Sí | — |
LEX_API_MX_BASE_URL |
No | https://api.lexapi.mx |
Errores
Los errores de la API llegan al modelo como errores de herramienta legibles: clave inválida (401), permiso faltante (403), saldo agotado (402) y límite de peticiones (429).
Código fuente
github.com/Julio-Patron/Lex-API-Mx
(licencia MIT). También está en el MCP Registry
como io.github.Julio-Patron/lex-api-mx.
Metadata
Release files for lex-api-mx-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lex_api_mx_mcp-0.1.1.tar.gz | 7.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lex_api_mx_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.4 kB
Release files / lex_api_mx_mcp-0.1.1.tar.gz
| Download URL | lex_api_mx_mcp-0.1.1.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
021b4bd808ade5f4f8fb3fe60569f78bd8ea819ffb6e364eb131ab786554c7e7
|
|
BLAKE2b-256 checksum How to use checksums |
77f78281503b8e5574965252039112ba153cc9ed44864ace8ee90a1fb234bb38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / lex_api_mx_mcp-0.1.1-py3-none-any.whl
| Download URL | lex_api_mx_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f95d7eee70d899024d8c685ca44a52467f63cb5e19e95beed4e7bc5d5730024c
|
|
BLAKE2b-256 checksum How to use checksums |
df981f2f12f45fc971d5668d68db321db5963783d511276e410176234e162363
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log