mcp-dataverse

This MCP server enables querying a Dataverse environment using SQL-style queries through MCP-compatible tools. By wiring this server into your MCP configuration, AI copilots and LLM assistants can send SQL-like requests to Dataverse and receive structured results in a consistent format. The server relies on a Dataverse connection URL provided via the DATAVERSE_ENVIRONMENT_URL context, so you can point it at your Dataverse instance and let it translate SQL queries into Dataverse fetch operations behind the scenes.

Prerequisites:

• .NET 9.0 SDK installed on your machine
• Access to a Dataverse environment and its URL
• Optional: Docker if you plan to run inside a container

Installation steps:

1. Install the Dataverse MCP dotnet tool (as described in the README of the project):
   • Ensure you have the tool package dataverse-mcp-dotnet-tool available from the project's install instructions.
2. Prepare the environment variable with your Dataverse URL:
   • Create a shell environment variable named DATAVERSE_ENVIRONMENT_URL or provide it directly in your MCP config.
3. Run the MCP server locally:
   • Use the recommended MCP integration method (e.g., add the following server config to your MCP client): { "command": "dotnet", "args": ["tool", "run", "dataverse-mcp-dotnet-tool"], "env": {"DATAVERSE_ENVIRONMENT_URL": "https://your-dynamics-environment.crm.dynamics.com"} }
4. If desired, run via Docker or a development container following the project’s Docker guidance and VS Code MCP Docker config snippets.
5. Verify connectivity by issuing a simple SQL-like query through your MCP-enabled tooling to ensure results are returned from Dataverse.

Notes and tips:

• Set DATAVERSE_ENVIRONMENT_URL to the exact Dataverse environment URL you intend to query.
• If you encounter authentication issues, ensure you’re authenticated to Azure/Dataverse as required by your environment (e.g., Azure CLI login or DevContainer context).
• The SQL dialect is translated by the MCP tool; some Dataverse-specific functions may map differently, so consult the Dataverse SQL mapping when composing complex queries.
• When running in containers or Dev Containers, ensure network access to the Dataverse endpoint and proper environment variable propagation.
• Monitor logs from the dotnet tool run to troubleshoot authentication, URL, or permission problems.