The MCP server is solved. The decision is not.
An MCP server is how a large language model reaches your ERP: it exposes data and actions as tools an agent can call, with permissions attached. Dynamics 365 Business Central ships one built in as of 2026 wave 1, alongside Payables, Sales Order and Expense agents on the included Copilot. What it gives an agent is everything the ERP already records. What it cannot give is the answer to a question the ERP never calculates — the optimal price, the optimal stock level, the route a picker should walk. Those are computed beside the ERP and handed back through the same protocol.
Two questions that look alike
“What is the reorder point on this item?”
The agent reads the field. The ERP stores it. Answered.
“What should the reorder point be?”
Nothing in the ERP holds this. No amount of tool-calling produces it, because the calculation was never there to call.
What an MCP server actually is
The Model Context Protocol is a standard way to describe tools to a language model. An MCP server sits in front of a system and publishes a list: here are the things you can read, here are the things you can do, here is the shape of each one. The model picks a tool and calls it. The server carries out the call under an identity with its own permissions.
For an ERP that matters more than it sounds. Without it, an assistant over Dynamics is doing retrieval over exported documents: it can tell you what a report said, and it cannot act. With it, the agent works the way a person does, through the same supported surface, under a role you granted.
The platform's own supported entry points, not the database. For Finance and Supply Chain Management that means OData data entities, custom services and Business Events. Reaching around them is what breaks upgrades.
An Entra app registration mapped to a service role. The agent can do exactly what that role can do and nothing else, which is the part an IT director will ask about first.
Structured records, not prose. The model reasons over the result; it does not have to parse a screen or trust a summary written by another model.
Business Central already ships one
Dynamics 365 Business Central 2026 wave 1 puts autonomous agents in the product: a Payables Agent that clears invoices end to end, a Sales Order Agent that keys orders, an Expense Agent. They reach data through a built-in MCP server, Copilot comes with the licence, and a person stays in the loop on anything consequential.
That is the honest starting point for anyone searching this term, and it changes the question. It is no longer "who will build me an MCP server for Dynamics". It is "what do I still have to build once the transport is free".
We cover this release in our own newsroom. Our position on it has not required adjusting, because it was never the transport we were selling.
Business Central 2026 wave 1, in our newsroom →What it can reach, and what it cannot compute
An MCP server is a transport and a permission layer. It is not a decision layer. The distinction is not a quibble — it is the line between a question the ERP can already answer and a question nobody has answered yet.
| Ask an agent over the built-in MCP server | What actually has to happen |
|---|---|
| "What is the reorder point on this item?" | It reads the field. The ERP stores it. Answered. |
| "What should the reorder point be?" | Nothing in the ERP holds this. It has to be computed from demand history and lead-time variability, then written back. The ERP records the number; it does not derive it. |
| "What did we quote this customer last time?" | It reads the quote. Answered. |
| "What price should go on this line to protect the margin?" | Requires elasticity over your own transaction history. The ERP has the transactions and none of the model. |
| "Where is this item stored?" | It reads the bin. Answered. |
| "Where should it be stored, and in what order should this wave be picked?" | A routing and slotting computation over the layout and the order profile. Not a field, not a report. |
Every row in the second half has the same shape. The data is in the ERP, the answer is not, and no amount of tool-calling produces it — because the calculation was never there to call. That is the work that sits beside the ERP.
What we build
The decision layer the agent calls
The optimizers compute what the ERP records but never derives — safety stock and reorder points, margin-optimal prices, pick paths and slotting. Exposed as tools, an agent can ask for the number and then act on it through the platform's own MCP server. The transport being free is good for us: it removes the part we were never differentiated on.
The data foundation underneath
An optimizer is only as good as the layer it computes on. Modelling, pipelines, governance and lineage over the Dynamics estate, so the numbers an agent quotes are the same numbers finance would.
The approval boundary
Anything that moves money or stock is prepared and put to a person. That design is what gets an IT director to say yes, and it is stronger than promising autonomy. It applies whether the agent runs on Microsoft's MCP server or ours.
Where we stand, in the five words we use
We publish a status word against everything, because "we do that" is the sentence that wastes a buyer's quarter.
Our own MCP server and Copilot extension for Dynamics
In developmentBeing built now, named as roadmap. Not a thing you can buy from us today, and we will not imply otherwise while Microsoft ships one in the box.
Contract Review Copilot
ShippedRunning for a customer today, as Paralegent AI.
Pricing, Pick-Path & Slotting, Demand & Inventory Optimizers
Built, demonstrated on requestThe software exists and is shown live against your own data.
Warehouse mapping, financial reconciliation, mobile Power Apps
Built to orderWe have the engineering and build it for you; there is no packaged app yet.
Supply-chain risk forecasting, planning-operations tooling
BlueprintArchitecture designed, nothing built.
Dynamics 365 and MCP, answered plainly
- Does Dynamics 365 have an MCP server?
- Business Central does, built in, as of 2026 wave 1 — the same release that adds the Payables, Sales Order and Expense agents, with Copilot included in the licence. For Finance and Supply Chain Management, agents reach data through the platform's supported surface: OData data entities, custom services and Business Events, with an Entra app registration mapped to a service role.
- Do you build an MCP server for Dynamics 365?
- Ours is In development — being built now, named as roadmap. We are deliberate about saying so, because Microsoft now ships one in the box and claiming to build what the platform vendor includes would be a me-too claim. What we build is the layer on the other side of it: the calculations the ERP does not perform.
- If the MCP server is included, what is left to build?
- Everything the ERP does not compute. An agent can read the reorder point because the field exists; it cannot tell you what the reorder point should be, because nothing in the ERP derives it. The same holds for margin-optimal pricing, pick paths and slotting. The transport is solved. The decision is not.
- Can an agent write back to the ERP?
- It can do whatever the role you granted can do. Our design is narrower than that on purpose: the agent reads live rather than from a nightly copy, and writes back only what it created. Anything that moves money or stock is proposed, prepared, and approved by a person.
- Does this require changing our ERP?
- No. The work sits beside the ERP and reaches it through supported surfaces, so what your implementation partner supports does not change. We never alter core ERP logic.
- Business Central or Finance & Supply Chain Management — does it differ?
- Materially. Different product, different data layer, different environment model. Business Central leads on quoting and pricing and now carries the built-in agents; Finance and Supply Chain Management is where the deeper warehouse and planning work lives. Knowing that difference is most of the expertise in these engagements.