Skip to main content
Glama
Sign In
Deere Ops Center MCP

Deere Ops Center MCP

by vanantwerp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Deere Ops Center MCP

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      konstantintutsch
      A
      license
      C
      quality
      B
      maintenance
      Gives AI assistants local, read-only access to your Garmin Connect health and activity data using your normal account login. Enables querying and downloading roughly 260 kinds of data such as activities, sleep, heart rate, stress, body composition, and training metrics without ever modifying your account.
      62
      MIT

    • agribrain

      VasileiosTs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access free, open agronomic data for field briefings, spray windows, water balance, pest pressure, and more, using only public data sources without API keys.
      1
      MIT

    • Jobber MCP Server

      adeocode
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Claude, ChatGPT, and Copilot to query live Jobber data—clients, jobs, quotes, invoices, revenue, and schedule—using natural language, with read-only access and careful API budget management.
      1
      MIT

    • VFS DMS ChatGPT Plugin

      mergi72
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (list vs get for fields, guidance lines, work plans, equipment, machine telemetry). The generic jd_get overlaps with every dedicated read tool, and jd_list_field_operations vs jd_export_field_operations/jd_download_operation_shapefile could be confused, but descriptions clarify intended use.

    Naming Consistency5/5

    All tools use a consistent jd_ prefix and snake_case, with predictable verb_noun or verb_resource_action patterns (list_fields, get_field, get_machine_alerts, download_operation_shapefile). The only minor deviation is the generic jd_get, but it is still readable and consistent with the prefix.

    Tool Count3/5

    22 tools is on the heavy side for the rubric's 16-25 borderline range. The broad John Deere domain covers many resources, so most tools earn their place, but the set could likely be trimmed or consolidated without losing much.

    Completeness4/5

    The surface covers a wide read-only lifecycle: organizations, fields, field operations, measurements, guidance lines, products, operators, work plans, equipment, machine telemetry, plus file export/save and a generic GET fallback. Minor gaps like no dedicated organization detail tool or explicit boundary history exist, but the generic jd_get can fill them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources