When someone refers to the Dynamics 365 MCP Server, they are talking about the Modern Commerce Platform (MCP) used in Dynamics 365 Commerce (the ERP’s retail/omnichannel module).
It is not used for Finance, Supply Chain, or Business Central,only the Commerce/Retail environment.
What MCP (Modern Commerce Platform) Actually Is
The Modern Commerce Platform (MCP) is the updated architecture Microsoft introduced to replace the older Retail Server + CRT (Commerce Runtime) stack.
The MCP Server typically refers to the local or cloud-hosted Compute Scale Unit (CSU) running MCP components.
MCP includes:
- Commerce Scale Unit (CSU)
- Local Store Scale Unit (SSU)
- Modern POS services
- Offline processing
- Channel database operations
- Local APIs for POS devices
- Real-time omnichannel transaction handling
What the MCP Server Does
An MCP Server provides:
1. Retail/POS Logic Processing
Runs the commerce runtime (CRT) and POS transaction logic.
2. Offline Capability for Stores
Stores can continue operating even if cloud connectivity is lost.
3. Local Commerce API Endpoints
For devices like:
- Registers
- POS terminals
- Payment terminals
- Inventory scanners
4. Integration with Dynamics 365 HQ (Finance & Operations)
Synchronizes:
- Product data
- Prices
- Discounts
- Transactions
- Customer data
Where MCP Is Used
MCP Server is required for:
- Dynamics 365 Commerce (Retail)
- Store operations
- POS networks
- Omnichannel commerce
- Hybrid or edge retail deployments
It is not used in:
- Dynamics 365 Finance only
- Dynamics 365 Supply Chain only
- Business Central
- CRM-based applications
Summary:
| Term | Meaning |
| MCP | Modern Commerce Platform |
| MCP Server | The server (cloud or local) that runs the MCP components for Dynamics 365 Commerce |
| Purpose | POS processing, offline store operations, commerce services |
How does the MCP Server connects to Headquarters (HQ)?
Below is a clear, side-by-side explanation of how the Dynamics 365 MCP Server (Modern Commerce Platform) compares to the older Retail Server used in AX 2012 and early Dynamics 365 versions.
MCP Server vs Older Retail Server, Quick Summary
| Feature | Old Retail Server (AX 2012 / Early D365) | MCP Server (Modern Commerce Platform) |
| Architecture | Monolithic | Modular, microservices-based |
| APIs | SOAP / legacy OData | Modern REST, microservices, cloud APIs |
| Performance | Limited scalability | Designed for cloud-scale and high throughput |
| Offline Support | Weak/complex | Built-in offline store capability |
| Deployments | Mostly on-prem | Cloud-first, hybrid, or local SSU |
| Updates | Heavy upgrades | Continuous, lightweight, cloud-driven |
| POS Integration | Retail Server → CRT → POS | MCP/CSU → CRT → POS |
| Commerce Runtime (CRT) | Windows services | Modern, container-friendly runtime |
| Extensibility | Hard to customize | Extension-first, plug-in architecture |
Architecture Difference Explained
Old Retail Server
- Lived on IIS (web server)
- Called CRT (Commerce Runtime) directly
- Was tightly coupled to channel databases
- Required manual local deployments
- Scaling required physical servers
This design worked but wasn’t cloud-ready.
MCP Server / Modern Commerce Platform
- Runs as Commerce Scale Unit (CSU) (cloud or local)
- Uses microservices, modern REST APIs
- Supports Local Store Scale Unit (SSU) for offline POS
- Dynamically syncs with HQ using cloud services
- Automatically scales in Azure
This design is highly modular, flexible, and retail-optimized for distributed stores.
Key Improvements in MCP Over Retail Server
1. Cloud-native microservices
Retail Server was a single large application.
MCP breaks functionality into independent services (pricing, cart, inventory, catalog, etc.).
This improves:
- performance
- fault tolerance
- flexibility
2. Strong offline & edge capabilities
Retail Server struggled with offline POS.
MCP includes the Store Scale Unit (SSU):
- POS continues operating without HQ connection
- Sync resumes when internet returns
3. Faster updates and easier extensibility
Retail Server required redeploying entire components.
MCP:
- supports plug-ins
- allows isolated service extensions
- updates components independently
This cuts development and deployment time.
4. Better API Surface
Retail Server used older OData/SOAP endpoints.
MCP exposes modern:
- REST APIs
- Cloud endpoints
- Real-time services
This simplifies:
- integrations
- e-commerce
- mobile apps
- custom apps
Bottom Line
MCP is the evolution of Retail Server,built for:
- cloud scale
- modern POS
- hybrid retail
- reliability
- performance
- easier customizations
Retail Server = old, monolithic
MCP Server = new, modular, cloud-ready, high-performance
Can you create a full architecture diagram labeled and simplified
Below is the clear, simplified, labeled architecture diagram you requested , showing how the older Retail Server compares to the modern Dynamics 365 MCP (Modern Commerce Platform) architecture.
To make things easy to understand, I’ll break it into:
- Old Retail Server Architecture (Legacy)
- Modern MCP / Commerce Scale Unit Architecture
- A combined side-by-side “diagram-style” layout
1. Old Retail Server Architecture (Legacy)
(AX 2012 / Early Dynamics 365 Retail)
Labeled Diagram (Text Version)
Dynamics AX HQ
(AX DB + Retail HQ Config)
│
▼
Data Distribution Jobs
│
▼
Channel Database (Store DB)
│
▼
Retail Server (IIS)
│
▼
Commerce Runtime (CRT Logic)
│
▼
Retail Modern POS
Key Points
- Retail Server acted as the middleware layer between POS and HQ.
- Hosted on IIS (monolithic web app).
- Communication mostly through:
- SOAP / early OData
- Tight coupling to Channel DB
- SOAP / early OData
- Offline support was weak and required custom setups.
2. Modern MCP (Modern Commerce Platform) Architecture
(Dynamics 365 Commerce today)
Labeled Diagram (Text Version)
D365 HQ (F&O)
(Commerce HQ + Global DB)
│
Async Data Sync + Jobs
│
▼
Commerce Scale Unit (CSU – Cloud MCP)
┌──────────────────────────────────┐
│ Microservices (Pricing, Cart, │
│ Inventory, Channels, Customers) │
│ │
│ Commerce Runtime (Modern CRT) │
│ Modern Commerce APIs (REST) │
└──────────────────────────────────┘
│
▼
Store Scale Unit (Local MCP)
(Offline POS Compute + Local Services)
│
▼
POS Devices
Key Improvements
- Microservices instead of monolithic Retail Server.
- Native REST APIs instead of legacy SOAP/OData.
- Built-in Store Scale Unit (SSU) for offline capability.
- Cloud or hybrid deployment.
- Modular extension framework.
3. Full Side-By-Side Architecture Comparison Diagram
Legacy Retail Server vs Modern MCP Server
─────────────────────────── OLD RETAIL SERVER ───────────────────────────
D365/AX HQ
│
Data Push (Jobs)
│
▼
Channel Database
│
▼
┌──────────────────────────┐
│ RETAIL SERVER (IIS) │ ← Monolithic Web App
│ – SOAP / OData APIs │
│ – Tight DB Coupling │
│ – Limited Offline │
└──────────────────────────┘
│
▼
POS / MPOS
────────────────────────── MODERN MCP / CSU SERVER ───────────────────────
D365 HQ
(Commerce + Global DB)
│
Async Sync + Real-time APIs
│
▼
┌────────────────────────────────────────────────┐
│ COMMERCE SCALE UNIT (CSU – MCP Cloud) │
│ – REST APIs │
│ – Microservices (Pricing, Cart, Inventory) │
│ – Modern CRT │
│ – Auto-Scaling Cloud Infrastructure │
└────────────────────────────────────────────────┘
│
▼
Store Scale Unit (SSU – Optional)
– Offline Engine
– Local Commerce Services
│
▼
POS Devices
What the Diagram Shows
- The old Retail Server sat between POS and Channel DB as a single IIS application.
- The MCP Server (CSU/SSU) splits responsibilities:
- Cloud microservices
- Local offline engine
- Modern API layer
- More resilient and scalable architecture
- Cloud microservices