Cases and customer context
Work with service records, customer context, timelines, and related information while preserving the signed-in user's Dataverse access.
Independent product guide · August 3, 2026
Dynamics service tools can reach approved MCP clients without bypassing Dataverse
Microsoft's GA Customer Experience MCP Server for Service exposes more than 90 service-oriented tools through Agent 365 Tooling Gateway. Use it when an approved client or custom agent needs Dynamics capabilities—and keep identity, record permissions, external data, and actions bounded.
Capability map
More than 90 tools, grouped by the service outcome they can affect
Knowledge and communications
Search knowledge and support email or activity workflows. Require source review and human approval before customer-facing output.
Intelligence and search
Use service recommendations, data retrieval, and search as evidence. Do not treat a model-generated result as an authoritative case record.
Environment and administration
Keep higher-impact operations restricted to accountable administrators, separate identities, tested changes, and audit review.
Access model
A successful connection still passes through four control layers
01
Client
Approve the MCP host, business purpose, retention, model use, and external-data destination.
02
Gateway
Use the correct Agent 365 ring, environment-specific URL, OAuth discovery, and pre-granted delegated consent.
03
Dataverse
Apply existing roles, business units, record ownership, and field-level security to the signed-in identity.
04
Action
Limit tool categories, require review for consequential writes, log activity, verify the result, and retain a revocation path.
Current connection
Use the GA gateway route, not an old preview configuration
The current server URL is https://<ring-host>/mcp/environments/<environment-id>/servers/mcp_D365CX_Service. The environment must match the Agent 365 ring, tenant consent must be granted in advance, and Dataverse roles remain authoritative.
Implementation guides
Server setup
Configure the exact Agent 365 Tooling Gateway URL, OAuth consent, ring, and test sequence.
Clients and permissions
Compare discovery-capable hosts, Copilot Studio, Dynamics roles, and external-data controls.
Service Agent vs. MCP
Choose between the packaged Microsoft 365 Copilot experience and an independent MCP connection.
Dynamics Customer Experience MCP questions, answered
It is a Microsoft-hosted MCP server that exposes more than 90 Dynamics 365 service-oriented tools to compatible clients through Agent 365 Tooling Gateway. Microsoft announced general availability on July 30, 2026.
Microsoft lists Microsoft 365 Copilot and Service Agent, Copilot Studio, VS Code, GitHub Copilot CLI, and supported HTTP MCP clients such as ChatGPT and Claude Code. Verify the current host's remote HTTP MCP and OAuth discovery support.
No. Agent 365 Tooling Gateway authenticates the connection, while existing Dataverse roles and permissions continue to control which records and operations the signed-in user may access.
No. The current GA product is named Dynamics 365 Customer Experience MCP Server for Service and connects through Agent 365 Tooling Gateway. Older preview pages can describe a deprecated name and different setup path.
No. This is an independent, source-checked product guide. It does not embed the server, grant Microsoft or Dynamics access, or establish a Flowith integration.
This page is an independent information guide, not an embedded Microsoft tool or a Flowith integration. Source check: August 3, 2026. Verify current server access, client support, roles, consent, compliance, licensing, and product documentation before production use.