USDA NASS MCP Server for Claude Code 8 tools — connect in under 2 minutes
Claude Code is Anthropic's agentic CLI for terminal-first development. Add USDA NASS as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install USDA NASS and 2,500+ MCP Servers from a single visual interface.
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add usda-nass --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About USDA NASS MCP Server
Connect to USDA NASS (National Agricultural Statistics Service) APIs through any AI agent and explore American agriculture data through natural conversation.
Claude Code registers USDA NASS as an MCP server in a single terminal command. Once connected, Claude Code discovers all 8 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where USDA NASS data drives decisions without human intervention.
What you can do
- Crop Production — Query yield, production, harvested acres and price data for all major crops (corn, soybeans, wheat, cotton, rice)
- Livestock Data — Retrieve cattle inventory, hog production, poultry statistics, milk and egg production data
- Agricultural Economics — Access prices received/paid by farmers, farm income, production expenses and land values
- Farm Demographics — Explore Census of Agriculture data including operator age, experience, occupation and veteran status
- Parameter Discovery — Discover valid values for any filter parameter (commodities, states, years, units)
- Survey Metadata — Review information about all NASS surveys including frequencies and methodologies
The USDA NASS MCP Server exposes 8 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect USDA NASS to Claude Code via MCP
Follow these steps to integrate the USDA NASS MCP Server with Claude Code.
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
Add the MCP Server
Run the command above in your terminal
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
Start using USDA NASS
Ask Claude: "Using USDA NASS, show me...". 8 tools are ready
Why Use Claude Code with the USDA NASS MCP Server
Claude Code provides unique advantages when paired with USDA NASS through the Model Context Protocol.
Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
Claude Code runs headlessly, enabling unattended batch processing using USDA NASS tools in cron jobs or deployment scripts
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
USDA NASS + Claude Code Use Cases
Practical scenarios where Claude Code combined with the USDA NASS MCP Server delivers measurable value.
CI/CD integration: embed USDA NASS tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping
Headless batch processing: schedule Claude Code to query USDA NASS nightly and generate reports without human intervention
Shell scripting: pipe USDA NASS outputs into other CLI tools for data transformation, filtering, and aggregation
Infrastructure monitoring: run Claude Code in a cron job to query USDA NASS status endpoints and alert on anomalies
USDA NASS MCP Tools for Claude Code (8)
These 8 tools become available when you connect USDA NASS to Claude Code via MCP:
get_crop_summary
Requires a commodity name (e.g. CORN, SOYBEANS, WHEAT, COTTON). Optionally filter by state and year. Returns detailed statistics with units, geographic scope and time period. Get crop production summary from USDA NASS
get_demographics_data
Optionally filter by state and year. Sector is automatically set to DEMOGRAPHICS. Get farm demographics data from USDA NASS
get_economics_data
Optionally filter by commodity, state and year. Sector is automatically set to ECONOMICS. Get agricultural economics data from USDA NASS
get_livestock_summary
Requires a commodity name (e.g. CATTLE, HOGS, CHICKENS, MILK, EGGS). Optionally filter by state and year. Get livestock production summary from USDA NASS
get_param_values
Parameters include: sector, group, commodity, commodity_desc, short_desc, source_desc, util_desc, unit_desc, freq_desc, domain_desc, state, county. Use this to discover what values you can filter by before making queries. Get valid values for a Quick Stats parameter
get_quick_stats
Accepts parameters: sector (CROPS, ANIMALS & PRODUCTS, ECONOMICS, DEMOGRAPHICS), commodity, group, commodity_desc, state, year, freq (ANNUAL, MONTHLY), unit_desc, source_desc. Returns statistical data with value, unit, state, year and commodity information. Use get_param_values to discover valid parameter values before querying. Query USDA NASS Quick Stats database
get_survey_info
This is useful for understanding what data is available and how frequently it is collected. Get information about USDA NASS surveys
search_by_commodity
Optionally filter by state, year and sector. This is a broad search that returns all available data for the commodity, including production, price, inventory and acreage statistics. Search Quick Stats by commodity name
Example Prompts for USDA NASS in Claude Code
Ready-to-use prompts you can give your Claude Code agent to start working with USDA NASS immediately.
"Show me the corn production summary for Iowa in 2024."
"What are the current cattle inventory numbers for Texas?"
"Show me what commodity values are available for filtering."
Troubleshooting USDA NASS MCP Server with Claude Code
Common issues when connecting USDA NASS to Claude Code through the Vinkius, and how to resolve them.
Command not found: claude
npm install -g @anthropic-ai/claude-codeConnection timeout
USDA NASS + Claude Code FAQ
Common questions about integrating USDA NASS MCP Server with Claude Code.
How do I add an MCP server to Claude Code?
claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.Can Claude Code run MCP tools in headless mode?
How do I list all connected MCP servers?
claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.Connect USDA NASS with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect USDA NASS to Claude Code
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.