A service that describes tools to AI – search, read, create, update or run an action – and carries them out when an agent calls them. One server serves many clients, so the same connection does not have to be rebuilt for each one.
AI that reaches your data – and no further than it should.
MCP is an open standard that lets AI clients such as Copilot Studio, GitHub Copilot and Claude use data and actions from other systems. Microsoft provides MCP servers for Dataverse and Dynamics 365. When they are not enough, we build custom MCP servers around your processes.
What an MCP server is, and is not
A way around access control. The server should respect the permissions of the user or agent calling it, and each connection is deliberately enabled for specific clients. Open access to every table is rarely the right answer.
Start with Microsoft's servers
Microsoft runs MCP servers for Dataverse and Dynamics 365. They respect the system's security roles, and an administrator decides which clients may connect. Tools, previews and pricing change quickly, so we confirm the current position for your environment and licences before a decision is made.
Dataverse MCP server
For Dynamics 365 Sales, Customer Service and other apps on Dataverse. An agent can search data, look up tables, run queries and create or update records within the user's security roles and row-level security. Deletion requires explicit approval. Allowed clients are configured in the Power Platform admin center.
Dynamics 365 ERP MCP server
For Finance and Supply Chain Management. An agent works with data entities, forms and actions like a user with the same security role, and your extensions and personalisations are included automatically. The server's metadata and guidance are in English, so Icelandic conversations are tested separately.
Custom MCP servers around your processes.
The built-in servers see tables and records but do not always know your rules. A custom server offers the agent a few well-defined tools, such as “log a complaint against a customer”, instead of general access to every table. We build it in .NET, host it in your Azure environment and connect it to Copilot Studio or other MCP clients.
Built-in or custom?
A built-in server is often enough when the agent needs to read and update standard records. A custom server pays off when an action spans several steps or systems, depends on business rules, or when the agent's scope should be narrower than its security role allows. Sometimes a predictable flow in Power Automate beats both.
Before a connection is enabled
- Allowed clients defined in the Power Platform admin center and Dynamics 365
- A dedicated identity and least-privilege access for each agent
- Human approval for deletion and other consequential actions
- Tests against misleading instructions in data (prompt injection) and attempts to exceed permissions
- A cost estimate and monitoring of Copilot Credit usage
- Retesting when Microsoft changes the server's tools
One connection. Tested on real data.
We connect one agent to a built-in or custom MCP server in a test environment, with agreed success criteria and permissions. Timing and price are confirmed in a proposal. The outcome may be a connection in production, a simpler solution or waiting for now.