FieldMCP

FieldMCP is an MCP (Model Context Protocol) infrastructure platform for agricultural APIs. Integrate once, access John Deere — and soon Climate FieldView and CNHi — through unified MCP servers.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants (like Claude) call external tools and access data sources. FieldMCP implements MCP servers that expose agricultural data as tools any MCP client can use.

What FieldMCP Provides

• Unified API — One integration covers multiple agricultural data providers. No need to learn each provider's API separately.
• MCP Native — Works with any MCP client (Claude Desktop, Claude Code, custom apps). Your AI assistant can directly query field data, equipment status, and agronomic intelligence.
• Normalized Data — Responses are normalized across providers. A field from John Deere looks the same as a field from any other provider.
• Farm Intelligence — Built-in agronomic analysis engine with 140+ diagnostic rules. Get yield analysis, soil recommendations, and prioritized action plans.
• Weather Data — Historical and forecast weather data for any location, including GDD calculations.

Architecture

flowchart TB
    A("Your App — Claude, custom MCP client")
    B("FieldMCP Gateway")
    C("John Deere API")
    D("Weather API")
    E("Farm Intelligence Engine")
 
    A -- MCP Protocol --> B
    B -- OAuth --> C
    B -- REST --> D
    B -- Direct --> E
 
    style B fill:#2d7a4a,stroke:#1f5c36,color:#fff

Your application connects to the FieldMCP gateway using the MCP protocol. The gateway is a standard OAuth 2.1 Authorization Server — MCP clients discover it via /.well-known endpoints and authenticate using OAuth with PKCE. The gateway handles authentication, rate limiting, data normalization, and provider-specific API calls.

Available Tools

FieldMCP exposes 11 tools across 3 providers:

See the Tools Reference for complete documentation.

Getting Started

Head to the Quickstart guide to get your first MCP call working.