remittances
This MCP server gives AI agents read-only access to US–Mexico remittance data (quarterly from 2013, through 2026-Q2 for Mexico) via six query tools.
get_coverage— discover available periods, state/municipality counts, sources and API endpoints.get_national_totals— Mexico's total remittances per period, yearly or quarterly.get_mexico_states— rank all 32 Mexican states by amount for a year or a specific quarter.get_mexico_state_timeseries— full time series for one Mexican state, or all states, yearly or quarterly.get_mexico_municipalities— rank municipalities for a year, optionally filtered to one state and paged with limit/offset (annual only).get_us_states— remittances sent from each US state for a year/quarter, plus that state's Mexican-born population.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@remittances which Mexican states received the most remittances in 2025?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Remittances API + MCP
Open API and MCP server for remittance flows between the United States and Mexico: $62.5B received in 2025, broken down by 32 Mexican states, 2,488 municipalities and 51 US states of origin, quarterly from 2013.
No API key. No rate limit worth mentioning. JSON or CSV.
Data powers remittances.mx; docs live at remittances.mx/dashboard/api.
Use it from an AI agent (MCP)
src/server.mjs is a Model Context Protocol server: one dependency-free Node
script speaking JSON-RPC over stdio.
git clone https://github.com/jp-pietrini/remittances-api-mcp.git
cd remittances-api-mcp
claude mcp add remittances -- node "$(pwd)/src/server.mjs"Or for Claude Desktop, in claude_desktop_config.json:
{
"mcpServers": {
"remittances": {
"command": "node",
"args": ["/absolute/path/to/remittances-api-mcp/src/server.mjs"]
}
}
}Then ask things like "which Mexican municipalities received the most remittances in 2025?" or "chart quarterly remittances since 2019".
Tools
Tool | Returns |
| Periods available, counts, sources, endpoint list |
| National series, yearly or quarterly |
| State ranking for one period |
| One state (or all) over time |
| Municipal ranking for one year |
| US sending states, with Mexican-born population |
Point the server at another deployment with REMITTANCES_API_BASE:
REMITTANCES_API_BASE=http://localhost:3000 node src/server.mjsCheck it works:
npm run smokeTroubleshooting
Tool returns
Invalid arguments: the server checks arguments before calling the API.yearis required for the state, municipality and US tools and must be an integer;quartermust beQ1-Q4.Request to ... failed: the API was unreachable or took longer than 30 seconds. Check your network, orREMITTANCES_API_BASEif you set it.Server not listed in your client: confirm the path to
src/server.mjsis absolute and thatnode --versionis 18 or newer, then runnpm run smoke.A state name returns nothing: use the exact name from
get_mexico_states(for exampleMichoacán de Ocampo).
Related MCP server: mcp-inegi
Use it from code (REST)
curl "https://remittances.mx/api/v1/meta"
curl "https://remittances.mx/api/v1/mexico/states?year=2025"
curl "https://remittances.mx/api/v1/mexico/municipalities?year=2025&state=Jalisco&limit=10"
curl "https://remittances.mx/api/v1/us/states?year=2024&format=csv"import pandas as pd
df = pd.read_csv(
"https://remittances.mx/api/v1/national?freq=quarterly&format=csv"
)Endpoint | Parameters |
|
|
|
|
|
|
|
|
|
|
|
|
Runnable examples live in examples/: quickstart.sh (curl),
quickstart.mjs (Node 18+, no dependencies) and quickstart.py (pandas).
Full description in api/openapi.yaml. Every endpoint
accepts format=csv and sends permissive CORS headers, so a browser or
notebook can call it directly.
Run the API yourself
api/nextjs/ holds the reference implementation: Next.js App Router route
handlers plus the loading and formatting helpers they share. Drop them into a
Next.js project as
src/lib/api-data.ts
src/app/api/v1/meta/route.ts
src/app/api/v1/national/route.ts
src/app/api/v1/mexico/states/route.ts
src/app/api/v1/mexico/states/timeseries/route.ts
src/app/api/v1/mexico/municipalities/route.ts
src/app/api/v1/us/states/route.tsand supply the source JSON in public/data/ (mexico_remittances.json,
mexico_muni_remittances.json, mexico_muni_names.json, us_remittances.json,
mexican_born_population.json). The handlers import those files, so there is
no database and no filesystem access at request time.
Data and caveats
Source | Used for |
Banco de México (via the DataMexico cube) | Remittances by Mexican state and municipality |
Banco de México SIE | Remittances by US state of origin |
US Census Bureau (ACS) | Mexican-born population by state |
CONAPO | Migration intensity |
INEGI (ENIGH, Census, ICMM) | Household demographics and income |
All amounts are current USD.
Mexican state and municipal series run to 2026-Q2. US state-of-origin series run to 2025-Q3: they come from a different Banco de México product and lag, so the two sides of the corridor can end on different periods.
Municipal figures are annual only.
The most recent calendar year is partial until all four quarters publish. Check
get_coveragebefore computing year-over-year changes.Banco de México revises past quarters; totals shift slightly between pulls.
Citation
Pietrini, J.P. US-Mexico Remittances Dashboard. Available at remittances.mx.
Please also credit Banco de México, INEGI, CONAPO and the US Census Bureau.
License
MIT. See LICENSE.
Available Tools
6 toolsget_coverageA
Coverage of the US-Mexico remittances dataset: first and last quarter available, state and municipality counts, sources, and the list of API endpoints. Call this first to learn which periods can be requested.
Inputs: no named parameters.
get_mexico_municipalitiesA
Remittances received by Mexican municipality for one year, ranked by amount. Filter to one state with state, and page through results with limit and offset. Municipal data is annual only.
Inputs: year (required), limit, state, offset.
get_mexico_statesA
Remittances received by each of the 32 Mexican states for one period, ranked by amount. Pass a year for the annual total, or a year plus quarter (Q1-Q4) for one quarter.
Inputs: year (required), quarter.
get_mexico_state_timeseriesA
Full remittance time series for one Mexican state (or every state when state is omitted). Use the exact state name from get_mexico_states, e.g. "Michoacán de Ocampo".
Inputs: freq, state.
get_national_totalsA
Total remittances received by Mexico per period, in USD. Use freq=quarterly for the quarterly series or freq=yearly for annual totals (the most recent year may be partial).
Inputs: freq.
get_us_statesB
Remittances sent from each US state for one period, with the Mexican-born population of that state. The US-origin series lags the Mexican series by a quarter or two.
Inputs: year (required), quarter.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct geographic level or query mode: coverage metadata, national totals, state period rankings, state time series, municipality rankings, and US state rankings. There is no meaningful overlap between them, and the descriptions clearly differentiate one-period snapshots from time series.
All tools follow the same get_<domain>_<resource> pattern with snake_case and a consistent verb prefix. Names like get_mexico_states, get_mexico_state_timeseries, and get_us_states are predictable and readable.
Six tools is a well-scoped size for a remittances dataset API. Each tool covers a meaningful queryable view without redundancy or bloat.
The tool set covers the dataset's major queryable dimensions: national totals, Mexican states, Mexican state time series, municipalities, US states, and coverage metadata. This gives agents a complete picture of the available data with no obvious dead ends.
Maintenance
Related MCP Connectors
Official Mexican data for AI agents: CURP, RFC, CFDI, postal codes, phone, SPEI/CEP, DOF, geocoding.
Deterministic Mexican/LatAm verification + sanctions & PEP screening for AI agents. Pay via x402.
SEC filings and financial data for AI agents: 59 tools for statements, valuation and supply chains.
Salary and H-1B disclosed-wage data as agent tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables access to Bank of Mexico (Banxico) economic data including real-time and historical USD/MXN exchange rates, inflation data, interest rates, and other financial indicators. Supports querying current rates, historical data with date ranges, and economic metadata through natural language.9MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to Mexico's INEGI (national statistics office) indicators API, enabling AI agents to query statistical data through natural language or direct tool calls.88 npmMIT

Tlaloc MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides AI assistants with live, authenticated access to official Mexican data sources including CURP, RFC, postal codes, phone numbers, SPEI payments, CFDI status, DOF semantic search, and geocoding via INEGI/INE.MIT- AlicenseAqualityBmaintenanceEnables AI agents to validate Mexican RFC, CURP, CLABE and NSS identifiers with real check digits, parse CFDI 4.0 invoices with labelled SAT catalogue codes and verified totals, and query the SAT's public status service to see whether an invoice is still valid. It also generates coherent test people and companies, all read-only and without API keys, certificates or PAC contracts.9108 npm1MIT