{
  "markdown": "# IMF — International Monetary Fund Data\n\nThe International Monetary Fund's macro database. Country-level GDP, inflation, current account, fiscal balance, exchange rates, debt, employment, demographics — across 190+ member countries. The standard cross-country macro source. Free, no auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor cross-country macro analysis, the IMF's databases (WEO — World Economic Outlook; IFS — International Financial Statistics; BOP — Balance of Payments) are the canonical source. Where FRED is US-focused, IMF is global and harmonized. Where World Bank focuses on development, IMF focuses on macro/fiscal/financial.\n\nCommon flows:\n\n- **Country macro snapshot.** GDP, inflation, current account for a given country.\n- **Cross-country comparison.** Pull the same indicator across multiple countries to compare.\n- **Time-series analysis.** Historical data for trend analysis.\n\nUsed by the `trade_country_profile` compound and pairs well with [Comtrade](/docs/reference/comtrade) (trade flows) and [BLS](/docs/reference/bls) (US labor).\n\n## Auth\n\nNone. IMF Data API is fully public, free.\n\n## Major databases\n\n| Database | Coverage | Use |\n|---|---|---|\n| **WEO** (World Economic Outlook) | Annual & semi-annual | GDP, inflation, fiscal, current account forecasts |\n| **IFS** (International Financial Statistics) | Monthly/quarterly | Money, banking, prices, government finance |\n| **BOP** (Balance of Payments) | Quarterly | Current/capital/financial accounts |\n| **DOTS** (Direction of Trade) | Monthly | Bilateral trade (mirror to Comtrade) |\n| **GFS** (Government Finance Statistics) | Annual | Government revenue, expenditure, debt |\n\n## Common pitfalls\n\n- **Country code variants.** IMF uses ISO 3-letter codes (USA, GBR, DEU). Comtrade uses 3-digit numeric. Census uses 2-letter. Cross-source linking needs translation.\n- **WEO publishes twice yearly.** April and October. Forecasts can shift dramatically between releases — always cite the vintage (e.g., \"WEO October 2024\").\n- **Exchange-rate definitions vary.** Period average vs. end-of-period vs. PPP vs. real effective. IMF data has all four; specify which.\n- **Coverage gaps.** Small economies and politically isolated countries (North Korea, Venezuela, Eritrea) have spotty data. The IMF API returns nulls; don't treat null as zero.\n- **Real vs. nominal.** Default GDP is nominal in current-USD. For comparisons over time or across rapid-inflation economies, you usually want real (inflation-adjusted, in constant prices) or PPP-adjusted.\n- **Lag.** Annual data published with 6–18 month lag depending on country reporting. Quarterly data faster, ~2–3 month lag for major economies.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"imf\": {\n      \"url\": \"https://gateway.pipeworx.io/imf/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/imf/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Imf data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4790,
  "sha": "8848d67eb3e827a5ead31873293ea806fdcc6e381d0046d393ee45dca020b5bb",
  "repo_slug": "pipeworx-io/mcp-imf",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_imf_a490f7ae/readme"
}