Edit

Overview of Dynamics 365 Customer Service MCP tools

Dynamics 365 Customer Service Model Context Protocol (MCP) tools provide standardized business actions that AI-powered experiences can use to access customer service data and perform service-related operations. These tools are part of the Dynamics 365 Customer Experience MCP Server for Service, which is generally available as an independent offering. Organizations can connect this server to a growing ecosystem of MCP-compatible AI clients to make customer service capabilities available within the tools and experiences their teams already use.

The server exposes Dynamics 365 Customer Service capabilities through MCP, an open standard for connecting AI applications to enterprise tools and data. Connections are managed through the Microsoft-hosted Agent 365 Tooling Gateway, and access aligns with existing Dataverse roles and permissions.

Service representatives and supervisors don't typically use MCP tools directly. Instead, these users interact with an AI-powered experience, such as Service Agent. The agent determines which tool to use, invokes the tool in the background, and presents the result to the user in chat or through an app-in-chat component.

For example, when a service representative asks Service Agent to summarize a case, the agent can use the appropriate case-related MCP tools to retrieve and summarize the information. The representative sees the result in the conversational experience and doesn't need to know the internal tool name or call the tool directly.

MCP tools can support interactive app-in-chat experiences. In these experiences, the result of a tool is shown inside the chat as an interactive component, where users can review the information and take supported follow-up actions. You can also access MCP tools through Work IQ. Learn how to enable Work IQ in Business Applications in Work IQ (preview).

Supported MCP clients

The Dynamics 365 Customer Experience MCP Server for Service supports integration with the following validated clients:

  • Microsoft 365 Copilot, including Service Agent
  • Microsoft Copilot Studio agents
  • Visual Studio Code
  • GitHub Copilot CLI
  • Other HTTP-based MCP clients

Learn about setup and configuration details for connecting supported clients in the Agent 365 overview.

Key uses

The Dynamics 365 Customer Experience MCP Server for Service includes more than 90 service-oriented tools that cover end-to-end workflows in a customer service organization. Organizations can use these tools to enable AI-powered customer service experiences across the following categories.

Case management

MCP tools can help retrieve, search, update, assign, and resolve customer cases. These tools support scenarios where users need quick access to case details, related activities, next actions, SLA status, and resolution workflows.

Customer information access

MCP tools can retrieve and summarize customer information such as accounts, contacts, and related records, including activity timelines. This capability helps users understand customer context during service interactions.

Knowledge management

MCP tools can support knowledge-related tasks such as searching knowledge articles, retrieving article details, drafting knowledge content, harvesting new articles, identifying knowledge gaps, and publishing articles. These capabilities help users find and reuse knowledge while resolving customer issues.

Email assistance

MCP tools can support AI-assisted email workflows such as drafting, generating, rewriting, translating, and sending emails, as well as applying email templates, logging activities, linking email to cases, and creating cases directly from email.

Activity and conversation management

MCP tools can help you create activities, add notes, view timelines, and summarize conversations or customer interactions. These capabilities help you capture and review service context without manually navigating across multiple records.

Intelligence and recommendations

MCP tools can surface next-best-action suggestions, preview responses, and answer knowledge and service questions in context. These tools help users make informed decisions during service interactions.

MCP tools can query and update Dataverse entity records and run cross-entity search and lookups. These capabilities support flexible data access and record management across the service environment.

Administration and configuration

Some MCP tools support administrative tasks such as managing environments, agent configurations, MCP registrations, profiles, tool selections, and user preferences. Additional admin and maker tools support extensibility scenarios, including registering and managing external MCP servers and Copilot Studio agents, and customizing Dynamics grids and views. These tools are most relevant to administrators and developers who configure or maintain AI-powered service experiences.

Personas

Service representatives

Service representatives use AI-powered experiences, such as Service Agent, to complete customer service tasks through natural language. They don't need to call MCP tools directly or understand internal tool names.

Common tasks include:

  • Retrieving case details.
  • Summarizing customer interactions.
  • Finding relevant knowledge articles.
  • Drafting or refining customer emails.
  • Adding notes or creating activities.
  • Resolving or updating cases.

Supervisors

Supervisors use AI-powered experiences, such as Service Agent, to review service activity, monitor escalations, understand case context, and support service teams. Like service representatives, supervisors typically interact with Service Agent rather than individual MCP tools.

Common tasks include:

  • Reviewing case or queue activity.
  • Understanding escalated or high-priority issues.
  • Getting summaries of customer service interactions.
  • Monitoring autonomous agent activity through supervisory experiences.
  • Taking follow-up actions based on service insights.

Administrators

Administrators configure and maintain the environments and settings that support AI-powered customer service experiences. They might work with tools or configuration experiences related to environments, profiles, registrations, and tool selections.

Common tasks include:

  • Configuring customer service environments.
  • Managing agent configurations.
  • Managing MCP registrations.
  • Configuring user preferences or profile settings.
  • Enabling or maintaining AI-powered service experiences.

MCP app developers and agent developers

MCP app developers and agent developers are the primary personas who work directly with the MCP tool catalog. They use tools as reusable building blocks to create conversational applications, app-in-chat components, and AI agent workflows.

Common tasks include:

  • Building app-in-chat components that present tool results to users.
  • Orchestrating multiple MCP tools into end-to-end workflows.
  • Deciding how tool responses should appear in the user experience.
  • Building conversational experiences for case management, knowledge assistance, email workflows, and service operations.
  • Designing experiences that use available tools at runtime rather than hard-coding dependencies on specific tool names or schemas.

Privileges, access, and security considerations

Dataverse security privileges govern access to Dynamics 365 Customer Service MCP tools. A user must hold all of the privileges that a tool requires before that tool becomes discoverable to the AI-powered experience. Tools that aren't mapped to specific privileges are discoverable by default. Privileges are also enforced when a tool runs, so a tool can be discoverable yet still be denied at run time if the underlying record or action isn't permitted.

Because each tool maps to one or more privileges, administrators can use security roles to control which capabilities are available to service representatives, supervisors, administrators, and developers. Learn more in Privilege reference for Customer Service Copilot tools

Agent 365 Tooling Gateway

The Microsoft-hosted Agent 365 Tooling Gateway manages connections to the Dynamics 365 Customer Experience MCP Server for Service. The gateway handles authentication to your Microsoft Dataverse environment and enforces existing Dataverse roles and permissions at both tool discovery and execution time. This enforcement means that users only see the tools they're permitted to use, and execution is subject to the same access controls that govern the underlying Dataverse data.

Organizations can use the Agent 365 Tooling Gateway to connect the server to supported MCP clients while maintaining established governance controls. Learn more in Agent 365 overview.

Dynamics Customer Service MCP server is extensible by design.

Important

When you connect to non-Microsoft MCP servers, you do so at your own risk. Microsoft has no responsibility related to your use of non-Microsoft MCP servers, and you're responsible for any associated terms and charges. Some of your data might be passed to the non-Microsoft MCP server, or your MCP client might receive data from the non-Microsoft MCP server. You're responsible for managing whether your data flows outside your organization's compliance and geographic boundaries.

MCP implementations are vulnerable to attacks, cascading failures, and loss of human oversight. To mitigate these risks, vet MCP servers for security and reliability, follow Microsoft's recommendations and industry best practices, and implement approval mechanisms to monitor cascading behaviors.

Available tools

Learn more about the available MCP tools in Service Agent tools.

  • Last updated on