Skip to main content
Glama
mcp-comexstat

mcp-comexstat

by luizzzvictor

Servidor MCP para la API de Comexstat

Este proyecto implementa un servidor MCP (Model Context Protocol) para la API de Comexstat, permitiendo que modelos de IA como Claude interactúen directamente con los datos de comercio exterior de Brasil.

Descripción general

El servidor Comexstat del MCP ofrece herramientas para consultar las estadísticas de exportación e importación brasileñas, entre ellas:

  • Datos generales de exportación e importación

  • Datos por municipios

  • Datos históricos (1989-1996)

  • Tablas auxiliares con códigos y descripciones

Related MCP server: br-eli-mcp

Características

  • Implementado usando @modelcontextprotocol/sdk

  • Escribir con TypeScript

  • Validación de datos con Zod

  • Soporte para comunicación vía stdin/stdout (estándar MCP)

  • Manejo robusto de errores y respuestas de API

Instalación

# Clone o repositório
git clone https://github.com/luizzzvictor/mcp-comexstat-easy.git
cd mcp-comexstat-easy

# Instale as dependências
npm install

# Compile o código TypeScript
npm run build

Uso rápido

# Execute o servidor MCP
npm start

Herramientas disponibles

El servidor MCP proporciona las siguientes herramientas:

Datos generales

  • getLastUpdate() - Obtiene la fecha en la que se actualizaron los datos por última vez

  • getAvailableYears() - Enumera los años disponibles para la consulta

  • getAvailableFilters() - Enumera los filtros disponibles

  • getFilterValues(filter, language?) - Obtiene valores para un filtro específico

  • getAvailableFields() - Enumera los campos disponibles para detallar

  • getAvailableMetrics() - Enumera las métricas disponibles

  • queryData(options) - Realiza consultas detalladas con los siguientes parámetros:

    • flow : "exportar" | "importar"

    • period : { desde: "AAAA-MM", hasta: "AAAA-MM" }

    • monthDetail : booleano

    • filters : Matriz de filtros (opcional)

    • details : Matriz de campos para detallar

    • metrics : Matriz de métricas

    • language : cadena (opcional, predeterminado: "pt")

Datos por municipios

  • queryMunicipalitiesData(options) - Consulta datos centrados en los municipios

Datos históricos

  • queryHistoricalData(options) - Consultar datos históricos (1989-1996)

Mesas Auxiliares

  • getStates() - Lista de estados brasileños

  • getStateDetails(ufId) : detalles de un estado específico

  • getCities() - Lista de ciudades

  • getCityDetails(cityId) - Detalles de una ciudad específica

  • getCountries(search?) - Lista de países

  • getCountryDetails(countryId) - Detalles de un país específico

  • getEconomicBlocks(options?) - Lista de bloques económicos

  • getHarmonizedSystem(options?) - Sistema Armonizado (SA)

  • getNBM(options?) - Nomenclatura Brasileña de Mercancías

  • getNBMDetails(coNbm) : detalles de un código NBM específico

Ejemplo de uso

// Consultar exportações para os EUA em 2023
const result = await queryData({
  flow: "export",
  period: { from: "2023-01", to: "2023-12" },
  monthDetail: false,
  filters: [{ filter: "country", values: [105] }],
  details: ["country", "month"],
  metrics: ["metricFOB", "metricKG"],
});

Integración con Claude

Para utilizar el servidor MCP con Claude Desktop:

  1. Agregue la configuración al archivo claude_desktop_config.json :

    {
      "mcpServers": {
        "comexstat": {
          "command": "node",
          "args": ["/caminho/completo/para/mcp-comexstat-easy/dist/index.js"]
        }
      }
    }
  2. En Claude Desktop, utilice el comando:

    /mcp comexstat

Desarrollo

# Executar em modo de desenvolvimento
npm run dev

# Executar testes
npm test

# Verificar cobertura de testes
npm test -- --coverage

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Available Tools

20 tools
getAuxiliaryTableD

Inputs: table (required), page, pageSize, search.

getAvailableFieldsD

Inputs: no named parameters.

getAvailableFiltersD

Inputs: no named parameters.

getAvailableMetricsD

Inputs: no named parameters.

getAvailableYearsD

Inputs: no named parameters.

getCitiesD

Inputs: no named parameters.

getCityDetailsD

Inputs: cityId (required).

getCountriesD

Inputs: search.

getCountryDetailsD

Inputs: countryId (required).

getEconomicBlocksD

Inputs: add, language, search.

getFilterValuesD

Inputs: filter (required), language.

getHarmonizedSystemD

Inputs: add, language, page, perPage.

getLastUpdateD

Inputs: no named parameters.

getNBMD

Inputs: add, language, page, perPage, +1 more.

getNBMDetailsD

Inputs: coNbm (required).

getStateDetailsD

Inputs: ufId (required).

getStatesD

Inputs: no named parameters.

queryDataD

Inputs: details (required), flow (required), metrics (required), monthDetail (required), +3 more.

queryHistoricalDataD

Inputs: details (required), flow (required), metrics (required), period (required), +3 more.

queryMunicipalitiesDataD

Inputs: details (required), flow (required), metrics (required), period (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.9/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting different data entities (countries, states, cities, NBM, etc.) or metadata (available fields, filters, metrics). However, some pairs like getCities/getMunicipalitiesData and getNBM/getNBMDetails have potential overlap that could cause confusion without descriptions to clarify their boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get' or 'query' prefixes, using camelCase uniformly throughout. The naming is highly predictable and readable, with clear conventions for different types of operations (get for metadata/entities, query for data retrieval).

    Tool Count3/5

    With 20 tools, this is borderline heavy for a trade statistics server. While the domain appears broad (covering countries, states, cities, NBM codes, auxiliary tables, etc.), the count feels somewhat inflated with multiple similar metadata tools (getAvailableFields/Filters/Metrics/Years) that might be consolidated.

    Completeness4/5

    The tool set appears to provide comprehensive coverage for trade data exploration and retrieval, including metadata discovery, entity lookups, and data querying across different dimensions (current, historical, municipal). Minor gaps might exist in data modification capabilities, but for a read-only statistical service, the surface seems reasonably complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      MCP Server do SEI Pro para o SEI (Sistema Eletrônico de Informações) via API REST mod-wssei v2 + scraper do frontend web (modo híbrido).
      100
      21
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Brazilian Chamber of Deputies open-data API, enabling search and retrieval of federal legislative bills and their status.
      15
      82 PyPI
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Omie API to list products, consult clients, and create budgets
      MIT