leafengines — Claude Code MCP server: soil and crop data
Hands your agent USDA soil data, NOAA weather forecasts and carbon credit math. Useful when the project touches farming or field mapping.
claude mcp add leafengines -e LEAFENGINES_API_KEY=<LEAFENGINES_API_KEY> -- npx -y @ancientwhispers54/leafengines-mcp-serverWhat leafengines does
leafengines is an MCP server bundling agricultural tools. It reads soil composition and N/P/K guidance from the SSURGO database, pulls water quality metrics from EPA sources, and serves historical weather plus climate trends from NOAA. On top of that sit crop selection for a given soil and climate, irrigation scheduling, pest identification, yield estimates and commodity prices. Carbon footprint and sustainability scoring cover environmental reporting.
The package is @ancientwhispers54/leafengines-mcp-server, started through npx over stdio. Core functionality is described as offline-first, so processing stays local for fields with poor connectivity. The TurboQuant hardware check runs without a key; everything else needs LEAFENGINES_API_KEY set. Register the server without that variable and it still starts, but data calls fail.
Clients include Claude, Codex, Cursor, GitHub Copilot, Windsurf, Cline, Zed and Gemini CLI. Cursor and Copilot take a JSON block in their settings file; the rest have add commands. The key travels as the LEAFENGINES_API_KEY environment variable at registration time.
What it helps with
- check soil composition and pH from USDA before planting
- pick crops that fit a specific field and climate
- schedule irrigation around a weather forecast
- estimate the carbon footprint of a field for reporting
- get yield and price estimates for a crop ahead of harvest
Example prompts for the agent
- Analyze the soil for this field using USDA data and tell me what N/P/K is missing
- Recommend crops that fit this climate and soil type
- Build an irrigation schedule for the next month from the weather forecast
How to install leafengines
Platform CLI
claude mcp add leafengines -e LEAFENGINES_API_KEY=<LEAFENGINES_API_KEY> -- npx -y @ancientwhispers54/leafengines-mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add leafengines --env LEAFENGINES_API_KEY=<LEAFENGINES_API_KEY> -- npx -y @ancientwhispers54/leafengines-mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"leafengines": {
"command": "npx",
"args": [
"-y",
"@ancientwhispers54/leafengines-mcp-server"
],
"env": {
"LEAFENGINES_API_KEY": "<LEAFENGINES_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"leafengines": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ancientwhispers54/leafengines-mcp-server"
],
"env": {
"LEAFENGINES_API_KEY": "<LEAFENGINES_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e LEAFENGINES_API_KEY=<LEAFENGINES_API_KEY> leafengines npx -y @ancientwhispers54/leafengines-mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about leafengines
How do I install leafengines in Claude Code?
Run claude mcp add leafengines -e LEAFENGINES_API_KEY=<LEAFENGINES_API_KEY> -- npx -y @ancientwhispers54/leafengines-mcp-server. The alternative form uses --env and --transport stdio with the same package.
What does leafengines do?
It gives the agent agricultural tools: soil analysis, crop recommendations, weather forecasts, water quality checks, carbon credit calculations and yield prediction.
Does it need an API key?
Yes, most tools require LEAFENGINES_API_KEY, passed when you register the server. The TurboQuant capability check works without one.
