Log inSubmit server
Inegi logo

Inegi

Access Mexico’s INEGI population data and indicators by geography through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Inegi

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "inegi": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-inegi"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-inegi

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The Inegi MCP server connects AI clients to Mexico’s national statistics office through the INEGI Indicators API. It provides population lookups for Mexico, states, and municipalities, plus access to indicators such as GDP, employment, prices, and economic census data. The server can run as a remote streamable-HTTP endpoint or as a local stdio package, and its tools return current values, reference years, or historical series. Reach for it when geographic detail from official Mexican statistics matters more than a general web search.

Use cases

  • Find Mexico’s population by state or municipality
  • Retrieve the latest value for an INEGI indicator
  • Compare an indicator across geographic levels
  • Fetch historical GDP or employment data
  • Call INEGI tools from an MCP-compatible client

Key features

  • Population lookup for Mexico, states, and municipalities
  • Numeric-ID access to the INEGI indicator catalog
  • Latest-value or full-history indicator results
  • Remote gateway and local stdio deployment
  • HTTP tool-calling endpoint

Tools2

What Inegi lets your agent do. Expand a tool for its parameters.

Self-reported~157 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @pipeworx/mcp-inegi (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads437Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed2Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Inegi works

What Inegi MCP server does

The Inegi MCP server exposes selected data from Mexico’s Instituto Nacional de Estadística y Geografía (INEGI) through the Model Context Protocol. It is intended for AI clients that need official Mexican statistics, especially population figures tied to a specific geographic area.

Its dedicated population tool returns the total population for Mexico as a whole or for a state or municipality. Results include the value and its reference year. This geographic coverage makes it suitable for questions about Mexico City, Jalisco, or other Mexican locations where a national figure is insufficient.

A second tool provides access to INEGI indicators by numeric identifier. The indicator catalog covers subjects including GDP, employment and ENOE data, economic censuses, and prices. The tool can return the latest value or the complete available history.

How it works

The Inegi MCP server can be used through the Pipeworx gateway at https://gateway.pipeworx.io/inegi/mcp. A gateway connection lists the two INEGI tools together with shared Pipeworx tools, including routing and discovery functions. The gateway can therefore route broader questions through ask_pipeworx, although the endpoint still exposes the INEGI pack directly.

The same gateway also offers a full endpoint at https://gateway.pipeworx.io/mcp, where all catalog packs are listed directly. Both gateway URLs use the same underlying service; the difference is which tools appear in the direct tool listing.

For a local setup, the package runs as a stdio MCP server with npx -y @pipeworx/mcp-inegi. The local process handles MCP initialization, tool listing, and tool calls for the INEGI tools only. It does not include the gateway’s shared meta-tools or cross-catalog routing.

Setup and configuration

Add the remote endpoint to an MCP client with a server entry whose url is https://gateway.pipeworx.io/inegi/mcp. Alternatively, configure the local package with command: "npx" and arguments -y and @pipeworx/mcp-inegi.

The gateway documentation states that initial calls do not require an account. Tools can also be called over HTTP; for example, send a JSON POST to /v1/tools/inegi_population with an area such as Mexico.

Tools and capabilities

  • inegi_population: retrieves total population for Mexico, a state, or a municipality, with the reference year.
  • inegi_indicator: retrieves an INEGI indicator by numeric ID at a selected geographic level, returning either the latest value or its history.
  • ask_pipeworx: available through the gateway for plain-language routing across the broader Pipeworx catalog, not through the standalone package.

Indicator IDs are selected from INEGI’s Constructor de consultas at inegi.org.mx/app/indicadores.

The Inegi MCP server is therefore a good fit for applications that need population by Mexican administrative area or that already know the INEGI indicator IDs they want to query. It is less direct when the task requires discovering an indicator without consulting INEGI’s indicator builder first.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Inegi

Inegi is an MCP server that connects AI clients to Mexico’s national statistics office, INEGI, through its Indicators API. Its main tools retrieve population for Mexico, states, and municipalities, or fetch catalog indicators such as GDP and employment by numeric ID, geography, latest value, or historical series.

Install it locally by configuring an MCP client to run `npx -y @pipeworx/mcp-inegi`. The package communicates over stdin and stdout and does not require a Pipeworx gateway account. You can instead use the remote endpoint at `https://gateway.pipeworx.io/inegi/mcp`.

Yes, Inegi works with Cursor through the documented remote MCP configuration. Add `https://gateway.pipeworx.io/inegi/mcp` as the server URL, or configure the local stdio command with `npx -y @pipeworx/mcp-inegi`.

Find indicator IDs in INEGI’s Constructor de consultas at `inegi.org.mx/app/indicadores`. Pass the numeric ID to `inegi_indicator`, along with the desired geographic level, to retrieve the latest value or its full history.

Yes, call them over HTTP through the Pipeworx tools API. For example, send a JSON POST to `https://gateway.pipeworx.io/v1/tools/inegi_population` with `{"area":"Mexico"}` to request the national population.

Related MCP servers

All in Data Science Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewInegi AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/inegi?style=directory)](https://allmcps.com/mcp/inegi)
HTML Embed
<a href="https://allmcps.com/mcp/inegi"><img src="https://allmcps.com/api/badge/inegi?style=directory" alt="Inegi on AllMCPs" /></a>