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.

John Deere MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: John Deere
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install John Deere and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "john-deere": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About John Deere MCP Server

Connect your John Deere Operations Center to any AI agent and manage fleet, field, and agronomic data through natural conversation instead of switching between dashboards.

GitHub Copilot Agent mode brings John Deere data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Organizations & Farms — List all farms, cooperatives, and organizations you manage with their full profiles
Fleet Management — View every tractor, combine, and sprayer with serial numbers, engine hours, and make/model details
Real-Time GPS — Get live machine positions and telemetry data to know exactly where your equipment is operating
Field Mapping — List all agricultural fields with boundaries, acreage, and current crop assignments
Operation History — Review planting, spraying, harvesting, and tillage records with product rates, yields, and operators
Alerts & Clients — Monitor machine alerts by severity and manage grower and landowner relationships

The John Deere MCP Server exposes 7 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect John Deere to VS Code Copilot via MCP

Follow these steps to integrate the John Deere MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using John Deere

Ask Copilot: "Using John Deere, help me...". 7 tools available

Why Use VS Code Copilot with the John Deere MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with John Deere through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

John Deere + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the John Deere MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

John Deere MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect John Deere to VS Code Copilot via MCP:

get_field_operations

Includes date, product, rate, yield, and operator. Get field operations

get_machine_locations

Get machine GPS locations

list_alerts

Includes alert type, severity, timestamp, and affected machine. List machine alerts

list_clients

List farm clients

list_fields

List fields/plots

list_machines

List fleet machines

list_organizations

Each org has machines, fields, and clients. List farms and organizations

Example Prompts for John Deere in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with John Deere immediately.

"Show me all machines in my main farm and their current locations."

"What was the corn yield on the North Quarter field this season?"

"Are there any active alerts on my fleet?"

Troubleshooting John Deere MCP Server with VS Code Copilot

Common issues when connecting John Deere to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

John Deere + VS Code Copilot FAQ

Common questions about integrating John Deere MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.