Leafengines
Wire soil analysis, crop recommendations, and weather forecasts into an ag-tech agent without hand-rolling SoilSidekick APIs.
Overview
LeafEngines is an MCP server for the Build phase that exposes agricultural soil, crop, and weather intelligence to AI coding agents via SoilSidekick/LeafEngines APIs.
What is this MCP server?
- stdio MCP via npm package @ancientwhispers54/leafengines-mcp-server (v1.1.6)
- Soil analysis, crop recommendations, and weather forecast tooling for agent workflows
- FREE TurboQuant capabilities tool usable without a paid API key
- Optional LEAFENGINES_API_KEY from app.soilsidekickpro.com for paid tools
- Agricultural AI positioning with TurboQuant as the no-key entry point
- Server schema version 1.1.6 on npm @ancientwhispers54/leafengines-mcp-server
- One documented FREE tool: turbo_quant_capabilities
- Paid tools gated by LEAFENGINES_API_KEY secret env var
Community signal: 4 GitHub stars.
What problem does it solve?
Ag founders waste days re-explaining soil APIs and weather data shapes to agents instead of shipping integrated recommendations.
Who is it for?
Solo builders on ag-tech or climate-adjacent products who want MCP-native agronomy tools in the same session as code.
Skip if: Teams with no agricultural domain needs or builders who only want generic web scraping without structured ag APIs.
What do I get? / Deliverables
After install, your agent can call LeafEngines tools for soil, crops, and forecasts—with a free TurboQuant path before you commit to an API key.
- Registered stdio MCP server in agent config
- Callable soil, crop, and weather tools from chat
- Documented free vs paid tool boundaries for your app
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the value is hooking external agricultural intelligence into the product via MCP during implementation. Integrations subphase fits MCP stdio/npm servers that expose third-party agronomy and forecast tools to coding agents.
How it compares
Domain-specific MCP integration for agricultural APIs, not a general-purpose coding skill or marketplace.
Common Questions / FAQ
Who is LeafEngines for?
Indie and solo builders creating ag-tech SaaS, advisory agents, or field-data workflows who use Claude Code, Cursor, or other MCP clients.
When should I use LeafEngines?
Use it while building features that need soil analysis, crop recommendations, or weather forecasts, starting with the free TurboQuant tool before adding LEAFENGINES_API_KEY.
How do I add LeafEngines to my agent?
Add the stdio MCP entry for @ancientwhispers54/leafengines-mcp-server in your client config, set LEAFENGINES_API_KEY when paid tools are required, and restart the agent.