
FAOSTAT MCP
Give your coding agent live UN FAOSTAT statistics while you research ag markets or build data-heavy products.
Overview
FAOSTAT MCP is a MCP server for the Build phase that exposes FAOSTAT crop, trade, food security, and emissions data for 245 countries through 21 agent-callable tools.
What is this MCP server?
- 21 MCP tools mapping FAOSTAT domains including crops, trade, food security, and emissions
- Country coverage across 245 economies for comparative market and policy research
- PyPI stdio transport (faostat-mcp 1.2.2) with JWT token or username/password refresh
- Optional FAOSTAT_API_TOKEN or FAOSTAT_USERNAME and FAOSTAT_PASSWORD from the FAOSTAT Developer Portal
- Agent-callable queries replace hand-rolled REST clients inside Claude Code, Cursor, or Codex sessions
- 245 countries covered in server description
- Package version 1.2.2 on PyPI registry
Community signal: 14 GitHub stars.
What problem does it solve?
Coding agents have no built-in path to FAOSTAT’s authenticated API, so agricultural and food-security research stalls on manual API setup and opaque dataset codes.
Who is it for?
Solo builders using Claude Code or Cursor who need repeatable, country-level FAOSTAT pulls for agtech SaaS, climate narratives, or investor-ready market research.
Skip if: Builders who only need a one-off public CSV and will never run an MCP-capable agent against live FAOSTAT endpoints.
What do I get? / Deliverables
After you add the stdio server and FAOSTAT credentials, your agent can fetch and reason over official FAOSTAT series while you scope, prototype, or ship analytics features.
- Agent-invokable access to FAOSTAT crops, trade, food security, and emissions domains
- Comparable statistics across 245 countries without custom REST glue code
- Repeatable research and prototype data pulls inside the same coding session
Recommended MCP Servers
Journey fit
Solo builders install MCP servers during development to connect agents to external APIs rather than during launch or growth-only workflows. FAOSTAT MCP is a third-party data bridge—exactly the integrations subphase where agent tooling meets official agricultural statistics APIs.
How it compares
Official FAOSTAT data MCP integration—not an agent skill, marketplace bundle, or browser automation scraper.
Common Questions / FAQ
Who is FAOSTAT MCP for?
It is for indie developers and data-minded solo builders who want UN agricultural statistics inside Claude Code, Cursor, or Codex without writing custom FAOSTAT API clients.
When should I use FAOSTAT MCP?
Use it during Build (and upstream research) when your agent must query crops, trade, food security, or emissions across countries while you design APIs, dashboards, or validation memos.
How do I add FAOSTAT MCP to my agent?
Install the PyPI package faostat-mcp (stdio), set FAOSTAT_API_TOKEN or FAOSTAT_USERNAME and FAOSTAT_PASSWORD, then register the server in your host’s MCP configuration per the registry entry.