Deere Ops Center MCP
Related Servers
Alternatives to Deere Ops Center MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants to read drawing-review data—projects, drawings, revisions, comments, replies, and notification inbox—through a read-only, locally run connection.925 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- FlicenseCqualityCmaintenanceEnables agents to authenticate to Primavera Unifier and query REST V1/V2 APIs through read-only tools and Enterprise AI workflows for shells, business process records, project health, cost/schedule analysis, risks, documents, approvals, audits, and permissions. Write operations remain gated unless explicitly enabled.18-
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.2MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access Saxo Bank portfolio data, account balances, positions, orders, transactions, and market data such as instruments, quotes, and charts. It is read-only by default, with trading tools available only when explicitly enabled.10MIT
TDQS
Scored across 22 tools
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.
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.
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.
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.