John Deere Operations Center MCP Server

A remote MCP server hosted on Cloudflare Workers that connects to John Deere Operations Center. Browse organizations, fields, field operations, equipment, work plans, and more via any MCP-compatible client (Claude Desktop, Cursor, etc.).

Architecture

The server runs as a Cloudflare Worker with a Durable Object (McpAgent) providing stateful MCP sessions. Authentication uses a double OAuth proxy pattern:

• Downstream: The Worker is an OAuth server to MCP clients

• Upstream: The Worker is an OAuth client to John Deere

This means authentication happens at the transport layer — no manual auth tool call is needed.

Setup

Prerequisites

• A Cloudflare account (free tier works)

• A John Deere developer account with an application registered at developer.deere.com

• Node.js 18+

Quick setup (recommended)

git clone <repo-url>
cd john-deere-ops-center
npm run setup

The interactive setup script (scripts/setup.mjs) will walk you through every step:

1. Install dependencies — runs npm install

2. Cloudflare login — runs wrangler login in your browser

3. Create KV namespace — creates the OAUTH_KV namespace and patches its ID into wrangler.jsonc automatically

4. Enter credentials — prompts for your John Deere Application ID (JD_CLIENT_ID) and Secret (JD_CLIENT_SECRET), then pushes them as Cloudflare secrets along with an auto-generated COOKIE_ENCRYPTION_KEY

5. Deploy — runs wrangler deploy and prints your Worker URL

At the end of setup, the script prints:

MCP endpoint:   https://<worker>.<subdomain>.workers.dev/mcp
Redirect URI:   https://<worker>.<subdomain>.workers.dev/callback

Register the redirect URI at developer.deere.com under My Applications → your app → Redirect URIs before attempting to authenticate.

First login: After signing in with John Deere, you will be prompted to connect your Operations Center organization to the application. This is a required one-time step — the server detects it automatically and redirects you to connections.deere.com to complete the selection. See docs/oauth2-flow.md for details.

Manual setup

If you prefer to run each step yourself:

npm install
npx wrangler login
npx wrangler kv namespace create OAUTH_KV   # paste the id into wrangler.jsonc
npx wrangler secret put JD_CLIENT_ID
npx wrangler secret put JD_CLIENT_SECRET
npx wrangler secret put COOKIE_ENCRYPTION_KEY
npm run deploy

Register your application at developer.deere.com and add https://<worker>.<subdomain>.workers.dev/callback as a redirect URI.

For local development, copy .dev.vars.example to .dev.vars and fill in the values.

Connect an MCP Client

Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "john-deere": {
      "command": "npx",
      "args": ["mcp-remote", "https://<worker>.<subdomain>.workers.dev/mcp"]
    }
  }
}

Tools

Organizations & Fields

Work Plans

Equipment & Machine Health

Reference Data

Commands

Local Development

cp .dev.vars.example .dev.vars
# Fill in JD_CLIENT_ID, JD_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY
npm run dev

Test with the MCP Inspector:

npx @modelcontextprotocol/inspector@latest

Connect to http://localhost:8787/mcp.

Transport Type: Streamable HTTP Connection Type: Direct

Environment

This targets the John Deere Sandbox (sandboxapi.deere.com). Sandbox limits:

• Max 5 connected organizations

• Max 150,000 API calls/month

• 18-month maximum sandbox duration

For production access, apply through the John Deere developer portal.

Required OAuth Scopes

The following scopes are requested automatically during the OAuth flow: