DataverseDevToolsMcpServer

DataverseDevTools MCP Server exposes a suite of ready-to-use Dataverse tools for user and security administration, data operations, metadata exploration, and troubleshooting. The server is designed to run inside any MCP-enabled client (such as VS Code, Visual Studio, Claude, or other MCP clients) so you can perform common Dataverse tasks without leaving your development environment. After starting the server, the MCP client will auto-discover it and you can invoke tools like user management (viewing users, roles, teams), security and privilege exploration, data operations (FetchXML, Web API calls), and metadata queries directly through natural prompts mapped to the Dataverse tooling capabilities. Use the DVMCP server in Copilot Chat or other MCP-integrated interfaces to streamline administration flows while staying in your editor or familiar workspace.

Prerequisites:

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

Install as a 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

Usage after installation (example):

dataversedevtoolsmcpserver --environmentUrl https://yourorg.crm.dynamics.com

If you cloned the repository or run from source, you can build and run the project directly using dotnet with the appropriate --environmentUrl and authentication options as described in the repository's guidance.

Tips and considerations:

• The MCP server typically runs as a stdio-based server within MCP clients. Ensure the environment URL is reachable from the client network.
• If you operate behind a corporate proxy, you may need to set proxy environment variables (HTTP_PROXY, HTTPS_PROXY) in the MCP client configuration when launching the server.
• For automated scenarios, you can configure client credentials (tenantId, clientId, clientSecret) in the MCP JSON configuration where supported by the client.
• Sample mcp.json configurations in the README show usage with the global tool, as well as scenarios for authenticating via Client Credentials (Service Principal).
• If you clone the repository, you can run the project directly with dotnet run --environmentUrl <your-url> (and optional tenantId/clientId/clientSecret) to start the server locally.
• Common issues often involve network access to the Dataverse environment, proper authentication setup, or ensuring the correct version of the .NET SDK is installed.