Documentation

John Deere connector

Live, read-only MCP tools against your John Deere Operations Center fleet: current machine location, engine hours, idle hours, fuel, and odometer from the ISO 15143-3 (AEMP) snapshot. The connector is tools-only — there is no knowledge-source picker and no RAG crawler. Telematics change too quickly to index.

Connect — tenant OAuth

  1. In the OrgMCP admin console open /app/connectors/new?kind=johndeere (the connector is not listed in the catalog) and click Connect via OAuth. Sign in with the farm John Deere account (Werkdata owns the developer app — you do not paste a client id).
  2. After OAuth, open connections.deere.com and enable the Operations Center organization for OrgMCP if Test stays red.
  3. Click Test connection. Green means the grant authenticates and the fleet snapshot has at least one machine. Zero equipment fails — either the org is not enabled on Connections, or the org has no telematics-sharing machines.

Access tokens last 12 hours and refresh automatically. Unused refresh tokens expire after 365 days — reconnect if Test reports an expired grant.

MCP tools

  • johndeere_list_fleet — one AEMP page (header, location, hours, fuel, odometer). Pass page from the previous nextPage.
  • johndeere_get_equipment — lookup by equipment id, PIN, or serial on the current snapshot
  • johndeere_diagnose — same picture as admin Test connection (needsOrgConnection, Connections URL, visible equipment count)

An empty first fleet page is a grant problem, not an empty list — use johndeere_diagnose. An empty page after page 1 is the end of the list.

What is not included

  • Operations Center JSON history (engine hours time-series, location breadcrumbs).
  • Alerts, device-state reports, Fields, Files, Equipment write/delete.
  • Personal OAuth or a tenant-owned Deere developer app.
  • RAG / ISOXML file ingest.