John Deere MCP. Monitor farm data and fleet status via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
John Deere. Connect your farm operations to any AI agent to manage fleet, field, and agronomic data. Track machine GPS locations, review planting/harvest yields, and monitor alerts from your entire farm estate via natural conversation.
What your AI agents can do
Get field operations
Gets records of past field activities, detailing the date, product, rate, yield, and operator.
Get machine locations
Gets the current GPS coordinates and location data for specified machinery.
List alerts
Lists active machine alerts, providing the alert type, severity, timestamp, and the machine affected.
Retrieves detailed records of past field activities, including the product used, the rate applied, and the final yield.
Pulls the current geographical coordinates and location status for any machine on your fleet.
Retrieves active warnings across the fleet, specifying the severity, timestamp, and affected machine.
Retrieves a list of farm clients associated with your organization.
Retrieves a list of all managed agricultural fields, including their boundaries and acreage.
Retrieves a catalog of all registered machines, including their unique serial numbers and model details.
Retrieves a list of all managed organizations, which also includes associated machines, fields, and clients.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019d75bdget field operations
Gets records of past field activities, detailing the date, product, rate, yield, and operator.
019d75bdget machine locations
Gets the current GPS coordinates and location data for specified machinery.
019d75bdlist alerts
Lists active machine alerts, providing the alert type, severity, timestamp, and the machine affected.
019d75bdlist clients
Lists all farm clients managed by the organization.
019d75bdlist fields
Lists all defined agricultural fields or plots.
019d75bdlist machines
Lists all registered machines in the fleet, providing make, model, and serial number details.
019d75bdlist organizations
Lists all managed farm organizations, including associated machines, fields, and clients.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with John Deere, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You've got the John Deere Operations Center hooked up to your AI agent. This server lets you manage all your farm data—the fleet, the fields, and the agronomics—using natural language. You don't gotta jump between a dozen dashboards; you just talk to your agent.
To check out all the organizations you manage, your agent can run list_organizations, which pulls up details on associated machines, fields, and clients. Need to know what clients you work with? list_clients gives you a list of every farm client under your organization's umbrella. You can pull up all the fields you're working with using list_fields, which lists every defined plot and its boundaries.
Want to see all the machines you own? list_machines gives you a catalog of every registered piece of equipment, detailing its make, model, and serial number. You can track where every machine is right now by running get_machine_locations, which returns the current GPS coordinates and location status for any specified piece of machinery.
If there's an issue, list_alerts shows active warnings across the whole fleet, giving you the alert type, severity, timestamp, and the machine that's having problems. To see what happened in the field, get_field_operations retrieves detailed records of past field activities, including the date, product used, rate applied, yield, and operator.
You can also get a list of all farm organizations and co-ops using list_organizations to see their full profiles.
How John Deere MCP Works
- 1 Subscribe to the server and provide your John Deere App ID, App Secret, and OAuth Access Token from
developer.deere.com. - 2 Your AI agent calls the specific tool (e.g.,
get_machine_locations) when you ask a question like, 'Where is the combine right now?' - 3 The server executes the API call, sends the structured data back, and your agent formats the answer for you.
The bottom line is, you never have to switch from your chat interface to a dedicated farm portal to check data.
Who Is John Deere MCP For?
Farm Managers, Agronomists, and Fleet Coordinators. You use this when you need a single source of truth for complex operational data. Stop switching tabs between the Operations Center, maintenance logs, and spreadsheets. You need to analyze yield data or track a machine's location based on natural conversation.
Checks machine locations and field operation status without having to open the full Operations Center app.
Pulls planting and yield data for specific fields to build season analysis reports instantly, comparing rates and yields over time.
Monitors alerts across the entire fleet and identifies machines needing immediate maintenance based on real-time data.
What Changes When You Connect
- See real-time equipment status. Use
get_machine_locationsto track a combine's GPS position and know exactly where it is without opening the Operations Center. - Build instant performance reports. Run
get_field_operationsto pull yield data and product rates for a specific field, allowing instant season-over-season comparisons. - Manage the whole fleet from one spot.
list_machineslets you get a full roster of every tractor and sprayer, making it easy to identify which units are out of service. - Stay ahead of breakdowns. Run
list_alertsto check for high-severity warnings across the entire fleet. You can find maintenance needs before they become emergencies. - Organize your data view. Use
list_organizationsto scope your query, ensuring you are only seeing data for the correct farm or co-op. - Scope your data quickly.
list_fieldslets you quickly list all available plots, so you can narrow down your yield query to a specific acreage.
Real-World Use Cases
The Field Manager needs to know where the equipment is.
A manager needs to check if the sprayer is still running in the East 160 field. Instead of pulling up the Operations Center app, they ask their agent, 'What is the location of the R4045 Sprayer?' The agent runs get_machine_locations and provides the live GPS coordinates and field context instantly.
The Agronomist needs to compare yields.
An agronomist needs to compare this year's corn yield against last year's for the North Quarter field. They ask, 'What was the corn yield on North Quarter?' The agent uses get_field_operations to pull the yield (bu/acre) and total harvest data, giving a direct comparison.
The Coordinator needs to triage alerts.
A coordinator logs in and asks, 'Are there any active alerts on the fleet?' The agent runs list_alerts, instantly listing high-severity issues (e.g., low oil pressure) and low-severity issues (e.g., scheduled maintenance), prioritizing immediate action.
The Owner needs an overview of assets.
An owner wants a quick count of all assets. They ask, 'List all my farms and all my machines.' The agent calls list_organizations and list_machines sequentially, giving a complete, structured count of the entire operational footprint.
The Tradeoffs
Over-relying on manual dashboard views
The user opens the Operations Center app, navigates to 'Fleet', then filters by 'Tractor', then checks 'Hours', and finally copies the data into an Excel sheet for review.
→
Ask your agent directly: 'Give me a list of all machines with engine hours over 1,000.' The agent runs list_machines and filters the results, giving you the data immediately without clicking anything.
Forgetting to scope the query
The user asks, 'Show me the yield data.' The system might return every yield record across every farm, making it impossible to find the data for the desired plot.
→
Always scope the request. Start by calling list_fields to get the correct Field ID, then ask, 'Now, show me the field operations for Field ID XXXXX.' This keeps the data clean.
Mixing up asset types
The user asks, 'Show me the status of the combines.' The system might mix combine data with sprayer data, resulting in a confusing, mixed report.
→
Be specific. First, use list_machines to get the serial number of the specific combine. Then, ask, 'What are the current alerts for serial number YYYYY?' This isolates the data stream.
When It Fits, When It Doesn't
Use this if your primary bottleneck is data aggregation and context switching. You need to run complex reports—like comparing yields across multiple fields (get_field_operations) or coordinating maintenance across the entire fleet (list_alerts)—without leaving your chat window. You are moving from a dashboard-centric workflow to a conversational, data-driven one.
Don't use this if you only need to view a single, simple metric (e.g., 'What is the current temperature?'). For simple data lookups, a dedicated IoT monitoring tool is faster. Also, if you need to update records (e.g., change a machine's owner), you'll need a different, write-enabled server.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by John Deere. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking farm data used to require jumping between five different portals.
Before this server, checking machine status meant opening the Operations Center, switching to the Fleet tab to check hours. Then, if you needed yield data, you had to open a separate agronomic dashboard and search by field ID. It was a constant cycle of tabs, filters, and copy-pasting.
Now, you just talk to your agent. You ask, 'What are the machine locations and what was the yield on the last harvest?' The agent runs the necessary tools—`get_machine_locations` and `get_field_operations`—and delivers a combined, contextual answer right here.
The John Deere MCP Server gives you full visibility into your entire operation.
You no longer have to manually check machine status, review alerts, and cross-reference field boundaries in separate systems. All the data—from `list_alerts` severity to the details from `list_fields`—is brought together on demand.
The result is a single, verifiable stream of data. You get a complete operational picture without the friction of manual data gathering.
Common Questions About John Deere MCP
How do I use the `list_alerts` tool to check my fleet? +
The list_alerts tool retrieves active warnings for your entire fleet. It returns the alert type, severity (High, Medium, Low), timestamp, and the exact machine involved. This lets you prioritize maintenance immediately.
Can I use `get_field_operations` to compare yields? +
Yes, get_field_operations includes yield data, the product used, and the operator. You can pull records for specific fields and use your agent to compare those yield figures against historical averages.
What is the difference between `list_machines` and `list_organizations`? +
Use list_machines to get a detailed list of individual tractors and combines. Use list_organizations when you need to scope the data to a specific farm, co-op, or corporate entity.
How do I find the boundaries of a field? +
Run list_fields to list all defined fields/plots. The output provides the field boundaries and acreage, which is the starting point for any specific field query.
How do I use `list_fields` to get all my farm plots? +
The list_fields tool provides a complete inventory of all your designated plots. You get the field boundaries, acreage, and current crop assignments for every plot listed in your account.
What information does `list_organizations` provide about my farms? +
list_organizations gives you a high-level view of all associated entities. It lists the primary farms, cooperatives, and organizations you manage, letting you see which machines, fields, and clients belong to that group.
How do I use `get_machine_locations` to track equipment? +
The get_machine_locations tool returns real-time GPS data for your fleet. You can check the current coordinates and know exactly where your equipment is operating right now.
Can I use `get_field_operations` to see who operated the equipment? +
Yes, get_field_operations includes the operator's name for every recorded operation. This lets you track which specific person was running the machine when the work was done.
Can my AI agent locate all my machines in real time and tell me which fields they're working? +
Yes! Use list_organizations to pick your farm, then get_machine_locations to fetch live GPS coordinates and telemetry for every machine. Cross-reference with list_fields to match coordinates to specific fields. Your agent builds the complete picture in one conversation.
How can I quickly review harvest yields across all my fields for the season? +
Ask your agent to iterate through your fields: 'Show me harvest data for all fields in org X.' It will call list_fields then get_field_operations for each, filtering for harvest operations. You get yield per acre, product totals, and operator names — perfect for end-of-season reporting without exporting spreadsheets.
Does this integration modify any data on my John Deere account? +
No. All 7 tools are read-only query operations — they list and retrieve data but never create, update, or delete anything. Your OAuth access token scope controls exactly which organizations and data types are accessible, matching the permissions you configured in the John Deere Developer Portal.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Parkopedia
Global parking search, EV charging, and restrictions data via Parkopedia API.
Kisi
Manage cloud-based access control, locks, and users via the Kisi API.
AgroLog
Access grain monitoring data via AgroLog — monitor temperature, moisture, CO2, crop levels, weather, and control aeration systems from any AI agent.
You might also like
Zoho CRM Service
Manage support cases and knowledge base solutions — customer service operations through Zoho CRM.
Ayrshare
Social media automation platform — publish posts, schedule content, and track analytics via AI.
Tactile CRM
Connect your AI to Tactile CRM. Query companies, read contact details, and evaluate your sales opportunities and pipelines natively from the terminal.