When setting up the Dataverse MCP Server, many users follow the official Microsoft Learn article to configure their mcp.json file. The tutorial instructs you to create a connection via make.powerautomate.com and then grab the URL from the connection page.

However, if you follow these instructions precisely, the URL you obtain will likely look something like this:

https://make.powerautomate.com/environments/
[YOUR_ENVIRONMENT_ID]/connections
/shared_commondataserviceforapps
/[YOUR_CONNECTION_ID]/details

Unfortunately, directly using this URL in your mcp.json file will not work as expected. The Dataverse MCP Server requires a slightly different URL format.

The correct URL format that will successfully configure your Dataverse MCP Server should be structured as follows:

https://make.powerautomate.com/environments/
[YOUR_ENVIRONMENT_ID]/connections
?apiName=shared_commondataserviceforapps
&connectionName=[YOUR_CONNECTION_ID]

Notice the key differences: the slashes after “connections” and “shared_commondataserviceforapps” are replaced with query parameters (?apiName= and &connectionName=), and the /details suffix is removed.

To correct the URL you obtain from Power Automate, you’ll need to manually tweak it:

1. Take the initial part of the URL: Copy everything from https://` up to and includingconnections`.
2. Replace the first slash: Change the / immediately after connections to ?apiName=.
3. Replace the second slash: Change the / after shared_commondataserviceforapps to &connectionName=.
4. Remove /details: Delete the /details portion from the very end of the URL.

By following these manual adjustments, you can transform the URL obtained from the Power Automate connection page into the correct format required by the Dataverse MCP Server, ensuring a successful configuration. This small but critical change can save you significant troubleshooting time!