USDA NASS MCP Server
Related Servers
Alternatives to USDA NASS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables plain English queries about US agricultural data, including historical crop statistics from NASS QuickStats and current cash grain prices from AMS Market News.-
- AlicenseNot gradedqualityCmaintenanceMCP server for accessing USDA National Agricultural Statistics Service (Quick Stats) data, enabling natural language queries about agricultural statistics.312 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes read-only tools for querying USDA NASS Quick Stats, covering reported counts, filtered data pulls, parameter values, crop progress and condition, county yield and production, acreage and forecasts, and prices received. Results are capped with guidance on narrowing queries.Apache 2.0

mcp-fasofficial
AlicenseNot gradedqualityBmaintenanceEnables access to USDA Foreign Agricultural Service trade and global production data through MCP, supporting natural language queries and tool-based data retrieval.173 npmMIT- AlicenseAqualityCmaintenanceEnables natural language queries of U.S. Census Bureau data, translating plain English questions into proper API calls and returning demographic, economic, and housing statistics with proper statistical interpretation and context.320MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to query the full FAOSTAT API for global food and agriculture statistics, allowing natural-language questions about crop production, trade, food security, emissions, and more.23184 PyPI20MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: retrieving full data, retrieving only a record count, and discovering parameter values. An agent can easily tell which tool to use for each task.
All tool names follow a consistent snake_case get_<object> pattern. The naming is predictable and readable across the entire small tool set.
Three tools are well within the appropriate range for a focused data-query server, and each tool serves a distinct necessary function. There is no obvious redundancy or padding.
The surface covers core data retrieval, counting, and parameter-value discovery, but lacks an explicit way to discover parameter names or datasets before querying. This is a minor gap that a knowledgeable agent can work around.