For years we have talked about automation, assistants and “intelligent agents”, yet most of those ideas remained as prototypes or isolated experiences. The reason was simple: there was no standard, secure and governed way for an agent to interact with real business tools.
This is where MCP and Foundry come in.
They are not new concepts. MCP has been around since 2024. Foundry has been maturing for some time. But now, with agents becoming more integrated into Business Central and the wider Dynamics ecosystem, these two capabilities are starting to have a real functional impact.
And that impact deserves to be explained from a business perspective, not a technical one.
1. What MCP is (explained for functional teams)
At its core, MCP is a standard that allows an agent to use business tools in a secure, structured and predictable way.
It is not an API. It is not a connector. It is not a plugin.
It is a common language that enables an agent to:
- retrieve information
- perform actions
- validate data
- interact with systems
- all within clear permissions, limits and rules
For functional teams, MCP means something very straightforward: agents stop behaving like “black boxes” and start acting as part of the process.
2. What Foundry is (without technical jargon)
If MCP is the language, Foundry is the platform that turns agents into governed enterprise resources.
Foundry allows an agent to:
- maintain context over time
- operate within defined boundaries
- use approved tools
- be audited
- comply with corporate security
- scale without breaking processes
In other words: Foundry makes an agent trustworthy, manageable and suitable for real business workflows.
3. Why this matters now (even though MCP has existed since 2024)
Because until recently, MCP was available… but without an ecosystem capable of fully leveraging it.
Today the situation is different:
- Business Central now includes agents that can use MCP
- Foundry provides real governance
- Organisations are demanding more mature automation
- Processes require agents that work with real data, not examples
So even if MCP is not new, its functional relevance is.
4. What changes for functional teams
Here is where the real value appears:
✔ Agents can work with real business tools
Not just “answer questions”, but perform actual tasks.
✔ Processes can delegate repetitive work
Data validation, document review, status checks, summaries.
✔ Automation no longer depends entirely on technical teams
MCP standardises interaction. Foundry governs it. Functional teams define the process.
✔ Security and auditability are built‑in
No more “shadow automations”. Everything is traceable.
✔ Specialised agents become possible
Not a generic assistant, but agents for purchasing, sales, finance, inventory…
5. What to expect in the next posts
This is only the beginning. The next posts will explore:
Post 2 — How MCP enables agents to work with real business tools
Functional examples, no code.
Post 3 — How Foundry provides governance, security and persistence
Why this changes how we design processes.
Post 4 — What this means for Business Central and functional roles
Impact on consulting, architecture and operations.
To Conclude
MCP and Foundry are not new technologies. What is new is their functional impact.
For the first time, agents can integrate into real processes with security, governance and approved tools. And that changes how functional teams design, execute and supervise work.
This is the starting point. The interesting part begins now.
Deja un comentario