DataverseDevTools MCP Server

A Model Context Protocol (MCP) server exposing ready-to-use Dataverse tools for user and security administration, data operations, metadata exploration, and troubleshooting. Stay in your flow: as a Dynamics 365/Dataverse developer, you don’t need to switch to XrmToolBox, make.powerapps.com, or admin.powerplatform.com for common tasks—run them right inside Visual Studio/VS Code or any MCP‑enabled client.

Prerequisites

• .NET 8.0 SDK or later
• A Dataverse environment URL (e.g., https://org.crm.dynamics.com)
• Permissions in Dataverse to perform the requested operations
• For plugin trace logs, ensure Plugin Trace Log is enabled in the environment

Install as global .NET tool

dotnet tool install --global vignaesh01.dataversedevtoolsmcpserver

Note: The executable command name is the tool command published with the package. If unsure, check with dotnet tool list -g.

Setup in MCP clients

Use the server from your favorite MCP-enabled client. Below are quick setups for VS Code, Visual Studio, and Claude on Windows.

VS Code (GitHub Copilot Chat)

Prerequisites:

• Latest VS Code
• GitHub Copilot and GitHub Copilot Chat extensions installed

Step-by-Step instructions with Screenshots:

• Go to : Setup in VS Code

mcp.json - using the Global Tool (Recommended)

{
  "servers": {
    "dvmcp": {
      "type": "stdio",
      "command": "dataversedevtoolsmcpserver",
      "args": [
        "--environmentUrl",
        "https://yourorg.crm.dynamics.com"
      ]
    }
  }
}

mcp.json - Using Client Credentials Authentication (Service Principal)

For automated scenarios or when interactive login is not possible, you can use client credentials authentication with an Azure AD application:

{
  "servers": {
    "dvmcp": {
      "type": "stdio",
      "command": "dataversedevtoolsmcpserver",
      "args": [
        "--environmentUrl",
        "https://yourorg.crm.dynamics.com",
        "--tenantId",
        "your-tenant-id",
        "--clientId",
        "your-client-id",
        "--clientSecret",
        "your-client-secret"
      ]
    }
  }
}

Note: To use client credentials authentication, you need to:

1. Register an application in Azure Active Directory
2. Create a client secret for the application
3. Add the application user in Dataverse with appropriate security roles
4. Use the tenant ID, client ID (application ID), and client secret in the configuration

mcp.json - For Corporate Networks behind a proxy

• Use Authenticated/Unauthenticated proxy address as appropriate:

{
  "servers": {
    "dvmcp": {
      "type": "stdio",
      "command": "dataversedevtoolsmcpserver",
      "args": [
        "--environmentUrl",
        "https://yourorg.crm.dynamics.com"
      ],
      "env":{
          "HTTP_PROXY": "http://<username@domain.com>:<password>@<proxy.domain.com>:8080",
          "HTTPS_PROXY": "http://<username@domain.com>:<password>@<proxy.domain.com>:8080"
        }
    }
  }
}

Sample mcp.json if you have cloned the GitHub Repository (For Explorers):

{
  "servers": {
    "dvmcp": {
      "type": "stdio",
      "command": "dotnet",
      "args": [
        "run",
        "--project",
        "C:/Projects/DataverseDevToolsMcpServer/DataverseDevToolsMcpServer/DataverseDevToolsMcpServer.csproj",
        "--environmentUrl",
        "https://yourorg.crm.dynamics.com"
      ]
    }
  }
}

Sample mcp.json with Client Credentials (For Explorers using cloned repository):

{
  "servers": {
    "dvmcp": {
      "type": "stdio",
      "command": "dotnet",
      "args": [
        "run",
        "--project",
        "C:/Projects/DataverseDevToolsMcpServer/DataverseDevToolsMcpServer/DataverseDevToolsMcpServer.csproj",
        "--environmentUrl",
        "https://yourorg.crm.dynamics.com",
        "--tenantId",
        "your-tenant-id",
        "--clientId",
        "your-c

... [View full README on GitHub](https://github.com/vignaesh01/DataverseDevToolsMcpServer#readme)