# FieldMCP

> MCP infrastructure platform for agricultural APIs. Integrate with John Deere, Climate FieldView, and more through a unified, LLM-ready interface.

Connect your AI to farm data in minutes, not weeks. FieldMCP provides MCP servers that give AI agents access to John Deere Operations Center data, farm intelligence analysis, and field weather over the Model Context Protocol. Start with the [Quickstart](https://www.fieldmcp.com/docs/quickstart). The full documentation corpus in a single file: https://www.fieldmcp.com/llms-full.txt

## Docs

- [Introduction](https://www.fieldmcp.com/docs)
- [Quickstart](https://www.fieldmcp.com/docs/quickstart)
- [OAuth 2.1](https://www.fieldmcp.com/docs/authentication/oauth)
- [Tools Overview](https://www.fieldmcp.com/docs/tools)
- [Rate Limits](https://www.fieldmcp.com/docs/rate-limits)
- [Error Handling](https://www.fieldmcp.com/docs/errors)
- [List Resources](https://www.fieldmcp.com/docs/tools/deere/list-resources)
- [Get Field Overview](https://www.fieldmcp.com/docs/tools/deere/get-field-overview)
- [Get Equipment Status](https://www.fieldmcp.com/docs/tools/deere/get-equipment-status)
- [Search Operations](https://www.fieldmcp.com/docs/tools/deere/search-operations)
- [Diagnose Field](https://www.fieldmcp.com/docs/tools/intelligence/diagnose-field)
- [Analyze Yield](https://www.fieldmcp.com/docs/tools/intelligence/analyze-yield)
- [Compare Fields](https://www.fieldmcp.com/docs/tools/intelligence/compare-fields)
- [Get Action Plan](https://www.fieldmcp.com/docs/tools/intelligence/get-action-plan)
- [Get Rule Details](https://www.fieldmcp.com/docs/tools/intelligence/get-rule-details)
- [Search Rules](https://www.fieldmcp.com/docs/tools/intelligence/search-rules)
- [Get Conditions](https://www.fieldmcp.com/docs/tools/weather/get-conditions)
- [Pricing](https://www.fieldmcp.com/docs/pricing)
- [Changelog](https://www.fieldmcp.com/docs/changelog)

## Blog

- [FieldView + Deere Side by Side: Building Cross-Provider Agronomic Workflows with FieldMCP](https://www.fieldmcp.com/blog/fieldview-deere-side-by-side-building-cross-provider-agronom): Most farm data tools pick a side. Here's how to build workflows that pull from both Climate FieldView and John Deere at the same time, without gluing two APIs together yourself.
- [What Multi-Provider Farm Data Actually Costs You at Query Time](https://www.fieldmcp.com/blog/what-multi-provider-farm-data-actually-costs-you-at-query-ti): When your field data lives across John Deere, FieldView, Trimble, and Raven, the hidden cost isn't the integration. It's what happens when you try to query across all of it at once.
- [ARC vs. PLC Calculator: How to Estimate 2025 Program-Year Payments by County and MYA Price](https://www.fieldmcp.com/blog/arc-vs-plc-calculator-how-to-estimate-2025-program-year-payments): How to estimate ARC-CO versus PLC payments for the 2025 program year using county benchmarks, MYA price assumptions, and PLC yield inputs.
- [Platform Consolidation in Ag Data: What the Farmers Edge + Leaf Partnership Actually Means for Developers](https://www.fieldmcp.com/blog/platform-consolidation-in-ag-data-what-the-farmers-edge-leaf): When ag data platforms consolidate through unified APIs, the real winners are developers building cross-provider tools. Here's what that means in practice.
- [The Field Identity Problem: Why the Same Acre Has Three Different Names](https://www.fieldmcp.com/blog/the-field-identity-problem-why-the-same-acre-has-three-diffe): How Leaf's boundary merging works under the hood, what a canonicalFieldId actually means, and why it matters when you're building tools that span John Deere, FieldView, and Trimble.
- [AI in Precision Agriculture: What Developers Actually Need to Build](https://www.fieldmcp.com/blog/ai-in-precision-agriculture-what-developers-actually-need-to): A staff engineer's take on where AI in farm software is headed, why the data plumbing problem still matters, and how to build tools that hold up in the field.
- [How to Access Climate FieldView Data Through Leaf's Unified API](https://www.fieldmcp.com/blog/how-to-access-climate-fieldview-data-through-leaf-s-unified-): A practical guide to pulling Climate FieldView field data, operations, and boundaries through Leaf's unified agriculture API, with real code examples.
- [Getting Started with John Deere Field Data Using FieldMCP](https://www.fieldmcp.com/blog/getting-started-with-john-deere-field-data-using-fieldmcp): A step-by-step tutorial for connecting your John Deere Operations Center account to FieldMCP and pulling real field data in minutes.
- [What Is MCP and Why It Matters for Agricultural Data](https://www.fieldmcp.com/blog/what-is-mcp-and-why-it-matters-for-agricultural-data): A practical explanation of the Model Context Protocol and why it's the missing plumbing between farm data systems and AI assistants.

## Glossary

- [Agronomic Intelligence](https://www.fieldmcp.com/glossary/agronomic-intelligence): Data-driven analysis that combines field data, agronomic science, and algorithms to generate actionable farming recommendations.
- [API Gateway](https://www.fieldmcp.com/glossary/api-gateway): A server that acts as a single entry point for API requests, handling authentication, rate limiting, and routing to backend services.
- [Crop Scouting](https://www.fieldmcp.com/glossary/crop-scouting): The practice of systematically walking fields to observe and document crop conditions, pest pressure, and other agronomic issues.
- [Data Normalization](https://www.fieldmcp.com/glossary/data-normalization): The process of transforming agricultural data from multiple providers into a consistent, standardized format.
- [Equipment Telematics](https://www.fieldmcp.com/glossary/telematics): The remote monitoring of agricultural equipment through GPS tracking, engine diagnostics, and operational data transmitted from machines in real time.
- [Farm Management Information System (FMIS)](https://www.fieldmcp.com/glossary/fmis): Software that helps farmers plan, monitor, and document crop production activities and field operations.
- [Field Boundaries](https://www.fieldmcp.com/glossary/field-boundaries): GeoJSON polygons that define the geographic extent of agricultural fields, serving as the spatial foundation for all field-level data.
- [Geospatial Data](https://www.fieldmcp.com/glossary/geospatial-data): Data that includes geographic coordinates, enabling it to be mapped and analyzed in relation to specific locations on Earth.
- [Harvest Data](https://www.fieldmcp.com/glossary/harvest-data): Georeferenced crop production data collected during harvest, including yield, moisture, and machine performance metrics.
- [John Deere Operations Center](https://www.fieldmcp.com/glossary/operations-center): John Deere's cloud platform for managing farm data, equipment, and operations — the primary data source FieldMCP integrates with.
- [Machine-to-Machine Authentication](https://www.fieldmcp.com/glossary/machine-to-machine-auth): An authentication pattern where services authenticate directly with each other without human interaction, using client credentials.
- [Model Context Protocol (MCP)](https://www.fieldmcp.com/glossary/mcp): An open protocol that standardizes how AI applications connect to external data sources and tools.
- [NDVI (Normalized Difference Vegetation Index)](https://www.fieldmcp.com/glossary/ndvi): A satellite or drone-derived index that quantifies vegetation health by comparing near-infrared and visible red light reflectance.
- [OAuth 2.1](https://www.fieldmcp.com/glossary/oauth-2-1): The modern authorization framework that FieldMCP uses to securely delegate access to agricultural data without sharing credentials.
- [Planting Prescriptions](https://www.fieldmcp.com/glossary/planting-prescriptions): Georeferenced maps that specify variable seeding rates across different zones of a field for use by precision planting equipment.
- [Precision Agriculture](https://www.fieldmcp.com/glossary/precision-agriculture): A farming management approach that uses data and technology to optimize crop production at a sub-field level.
- [Rate Limiting](https://www.fieldmcp.com/glossary/rate-limiting): A mechanism that restricts how many API requests a client can make within a given time window to protect service availability.
- [Soil Sampling](https://www.fieldmcp.com/glossary/soil-sampling): The practice of collecting and analyzing soil samples at georeferenced points to map nutrient variability across a field.
- [Variable Rate Technology (VRT)](https://www.fieldmcp.com/glossary/variable-rate-technology): Technology that enables field equipment to automatically adjust input application rates based on prescription maps.
- [Yield Mapping](https://www.fieldmcp.com/glossary/yield-mapping): The process of collecting georeferenced harvest data to visualize crop production variability across a field.

## Legal

- [Privacy Policy](https://www.fieldmcp.com/legal/privacy)
- [Terms of Service](https://www.fieldmcp.com/legal/terms)
- [Data Processing Agreement](https://www.fieldmcp.com/legal/dpa)
- [Service Level Agreement](https://www.fieldmcp.com/legal/sla)

## Optional

- [Pricing](https://www.fieldmcp.com/pricing)
- [ARC/PLC Calculator](https://www.fieldmcp.com/arc-plc-calculator)
- [Security](https://www.fieldmcp.com/security)
- [About](https://www.fieldmcp.com/about)
- [Customers](https://www.fieldmcp.com/customers)
- [Integrations](https://www.fieldmcp.com/integrations)
- [Service Status](https://status.fieldmcp.com)