MDCplus vs Kepware: 2026 Integrator's Comparison

Integrators evaluating MDCplus and Kepware are usually deciding between two genuinely different categories of product, not two interchangeable competitors. Kepware (KEPServerEX, owned by PTC) is a general-purpose industrial connectivity platform. MDCplus is a CNC-specialized data collection and analytics platform with OEM protocols and dashboards built in. This article compares both at the level integrators actually need: per-protocol coverage, real total cost on representative projects, deployment options, and where each genuinely wins.

We've tried hard to keep this balanced. Kepware has real strengths MDCplus doesn't match. MDCplus has real strengths Kepware doesn't match. The right choice depends on the project, not on which product is "better."

TL;DR: When to Choose Each

Choose Kepware if: the project's center of gravity is PLCs, drives, and historians; the customer already runs a PTC stack (ThingWorx, Vuforia); or you need a single connectivity layer for >50 different device types across IT and OT.

Choose MDCplus if: the project is CNC-heavy; the customer wants OEE, downtime classification, and dashboards within weeks; you're an integrator without a dedicated dashboard-building team; or per-connection pricing on Kepware would erode your margin.

What Each Product Actually Is

Kepware KEPServerEX in One Paragraph

KEPServerEX is an industrial communication platform that aggregates data from over 150 protocols (CNC, PLC, drives, RTUs, sensors) and exposes them via OPC UA, OPC DA, MQTT, REST, and a few legacy interfaces. It's a connectivity layer — you bring your own historian, dashboard, and analytics stack on top.

MDCplus in One Paragraph

MDCplus is a CNC machine data collection and monitoring platform. It includes OEM protocol drivers for the major CNC brands (Fanuc Focas 1/2, Siemens SINUMERIK OPC UA, Heidenhain DNC, Mitsubishi MELSEC, Mazak, Okuma THINC, Brother CNC Net), plus the dashboards, OEE engine, downtime classification, alerts, and reports that customers see.

Why This Comparison Isn't Apples to Apples

A fair comparison covers Kepware plus a custom-built dashboard layer (Power BI, Grafana, custom React) versus MDCplus on its own. Comparing Kepware as just the OPC server against MDCplus as a full platform makes Kepware look weaker than it is — and ignores the engineering time to build everything on top of it.

OEM Protocol Coverage Compared

Fanuc (Focas 1 / Focas 2)

Both support Focas 1 and Focas 2. Kepware ships a Focas driver in its CNC suite. MDCplus integrates Focas natively across controller series 0i, 16i, 18i, 21i, 30i, 31i, 32i, 35i. Practical difference: MDCplus's tag model is pre-built around CNC concepts (active program, modal G-codes, alarm queue, axis feedrate), while in Kepware you map raw Focas function calls into your own tag tree. See Focas tech guide and Focas 1 vs 2 comparison.

Siemens SINUMERIK

Both rely primarily on Siemens OPC UA server (option on 828D, 840D sl, ONE). Coverage is comparable for current controllers. MDCplus also supports older 840D powerline through Run MyHMI / Snap7 and direct PLC reads. Kepware can do this with its S7 driver but requires more configuration. See Siemens OPC UA integration.

Mazak (MTConnect, SmartBox)

Mazak's primary integrator-facing protocol is MTConnect (via SmoothX, SmartBox, or older agents). Kepware reads MTConnect via its MTConnect driver. MDCplus reads MTConnect natively and additionally handles older Mazatrol controllers via direct connection where MTConnect is unavailable. On a fleet with mixed Mazak generations MDCplus typically covers more machines without supplemental hardware.

Heidenhain TNC Family

Heidenhain TNC controllers (TNC 530, TNC 640, TNC7) require the DNC option (Option 18) on the controller side. Both Kepware and MDCplus integrate with Heidenhain DNC. MDCplus has deeper coverage for older iTNC 530 and granular tag access (cycle time, current tool, axis position). Kepware's Heidenhain support is functional but more generic. See Heidenhain monitoring guide.

Mitsubishi MELSEC

Both have native MELSEC drivers. Comparable coverage for M700, M800, M80 series.

Okuma OSP / THINC

MDCplus integrates Okuma THINC API natively. Kepware relies on MTConnect or generic OPC UA — adequate for OSP P200/P300 but less expressive than THINC API for tool data and program info.

Brother CNC-B00 / B10

MDCplus has native Brother CNC Net support including Speedio series. Kepware coverage relies on MTConnect adapters or generic protocols, with reduced data fidelity.

Coverage Summary Table

Pricing and Licensing

Kepware's Per-Connection Model

KEPServerEX licenses are tiered: server + driver suite (CNC suite includes Fanuc Focas, MTConnect, etc.) + connection count. A typical CNC project quote starts around $4,000–$8,000 for the base suite plus per-connection charges. PSP (annual support / upgrades) is normally 20% of license fee. Detailed breakdown in Kepware Pricing for CNC.

MDCplus Licensing

Per-machine lifetime pricing, with brand-agnostic licenses (you don't pay extra for Fanuc vs Siemens vs Mazak).. Includes connectivity, dashboards, OEE, alerts, reports, user accounts, and updates.

Total Cost on a 50-Machine Project

On a representative 50-machine mixed-brand project (20 Fanuc, 15 Siemens, 10 Mazak, 5 Heidenhain), Kepware first-year cost typically lands at $35,000–$55,000 for the connectivity layer alone - plus internal engineering hours to build dashboards (200–400 hours typical). MDCplus first-year cost on the same project is materially lower including dashboards.

Deployment Architecture

On-Premise, Edge, and Cloud Options

Kepware: on-prem and edge primarily, cloud via IoT Gateway add-on. MDCplus: on-prem, edge, private cloud, public cloud — all officially supported. For customers with strict no-cloud policies (defense, aerospace, certain EU manufacturers) both work. For customers wanting cloud-first, MDCplus is more direct.

Hardware Requirements

Both run on modest Windows or Linux servers. Kepware is Windows-first. MDCplus runs on either, with edge deployments on industrial PCs (Advantech, Siemens IPC, similar).

Network and IT-OT Boundary

Both implement standard segmentation patterns. MDCplus's edge agent is designed to push outbound only (no inbound from IT to OT), simplifying customer firewall negotiations.

What's Included Out of the Box

Kepware: Connectivity Layer Only

Tags, drivers, OPC UA / MQTT / REST endpoints, basic redundancy. No dashboards, no OEE engine, no downtime tagging UI, no operator screens.

MDCplus: Connectivity + Dashboards + Analytics

OEM protocols, tag models, OEE calculation, downtime reason codes, andon, shift reports, alerts, multi-user access, role-based permissions, mobile views.

Integrator Experience

Setup Time on First Machine

Kepware: 0.5–2 days from install to first tags streaming, depending on the protocol. MDCplus: typically a few hours, because the tag model is pre-defined.

Adding the 50th Machine

Kepware: each new connection requires tag mapping work. MDCplus: clone an existing machine profile and adjust IP / parameters.

Customer Handover and Training

Kepware: customer needs to be trained on KEPServerEX configuration, plus whatever you built on top. MDCplus: customer is trained on the unified product UI.

Support and SLAs

Kepware/PTC has a global support organization with multi-tier SLAs. MDCplus offers direct engineering support to integrator partners. For enterprise customers requiring 24/7 with named TAMs, both can deliver, structured differently.

Where Kepware Genuinely Wins

• Mature, broad ecosystem with 30+ years of reference deployments.
• Best-in-class for mixed device fleets (CNC + PLC + drives + sensors + IT systems).
• Deep PTC integration if the customer is on ThingWorx, Vuforia, Windchill.
• Massive third-party tooling and community.
• More prominent in IT enterprise procurement databases.

Where MDCplus Genuinely Wins

• Better OEM CNC coverage out of the box, especially for Mazak older generations, Okuma THINC, Brother, Heidenhain iTNC 530.
• Per-machine pricing avoids margin erosion on multi-CNC projects.
• Dashboards, OEE, downtime tagging built in — no second build phase.
• Faster time-to-first-value (weeks vs months).
• More accommodating partner economics for SMB integrators.
• Direct engineering support without enterprise-tier paywall.

Decision Tree: Which Should You Choose?

1. Is the project >70% CNC machines? → MDCplus
2. Is the customer locked into PTC ecosystem? → Kepware
3. Is the customer a defense / aerospace / regulated buyer with deep IT-OT review? → Either; verify deployment fit per case
4. Does the customer want monitoring live in 4–8 weeks? → MDCplus
5. Is the project really a SCADA/HMI rebuild with CNCs as side-cars? → Kepware (or Ignition)
6. Will the customer expand to second site or add another OEM brand later? → MDCplus (lower marginal cost)

Frequently Asked Questions

Is MDCplus a direct competitor to Kepware?

Partially. They overlap on the CNC connectivity layer. MDCplus extends beyond Kepware into dashboards and analytics, while Kepware extends beyond MDCplus into PLC/SCADA and broader IT-OT scope.

Can I use both in the same project?

Yes — MDCplus for CNCs, Kepware for PLCs and SCADA-style devices. They coexist via OPC UA or MQTT.

Does MDCplus include Focas licensing?

Yes, MDCplus handles Focas distribution licensing as part of its product license. See OEM Protocol Licensing Guide.

How does Kepware's MTConnect support compare?

Kepware's MTConnect driver is solid for current standard implementations. It does not bridge to non-MTConnect protocols, so on a Mazak fleet that mixes MTConnect-equipped and older Mazatrol machines you'll need additional hardware on the older side.

What about Kepware Edge?

Kepware Edge is the Linux edge runtime for KEPServerEX. It's a meaningful product for distributed IIoT but doesn't change the CNC-specific economics discussed here.

Is migration from Kepware to MDCplus practical mid-project?

Yes, with parallel-run methodology. Plan 4–10 weeks for a 30-machine migration. See Migrate from Kepware to MDCplus.

Does Kepware support OEE out of the box?

No. KEPServerEX provides tags. OEE calculation is built downstream — typically in ThingWorx, Power BI, or a custom application. MDCplus calculates OEE natively.

Which has better security posture?

Both implement standard industrial security practices (TLS, certificate-based OPC UA, RBAC). Customer-side IT review will weigh both favorably; specific deployments may have edge-case differences. See IEC 62443 Explained.

Try MDCplus on Your Next Project

The fastest way to validate fit is a single-machine pilot. Request a technical demo — we'll walk through your customer's actual brand mix, not generic slides. Or try MDCplus free on one machine first.

Related:

• CNC Connectivity Software for Integrators (Hub)
• Kepware Alternatives for CNC
• Kepware Pricing for CNC
• Why Integrators Switch from Kepware
• Build vs Buy Fanuc Connector
• Why MDCplus

About MDCplus

Our key features are real-time machine monitoring for swift issue resolution, power consumption tracking to promote sustainability, computerized maintenance management to reduce downtime, and vibration diagnostics for predictive maintenance. MDCplus's solutions are tailored for diverse industries, including aerospace, automotive, precision machining, and heavy industry. By delivering actionable insights and fostering seamless integration, we empower manufacturers to boost Overall Equipment Effectiveness (OEE), reduce operational costs, and achieve sustainable growth along with future planning.