Not even able to connect

The Dataverse MCP server is completely unusable out of the box. Following the official Microsoft Learn documentation
step by step results in an endless auth loop with zero useful error messages. Whoever designed this flow should be
forced to use it.

Environment

• Client: Claude Code (latest)
• OS: Windows 11 Pro
• Package: @microsoft/dataverse (local proxy)
• Dataverse org: https://orgbbcce9b6.crm4.dynamics.com/
• Node: v18+
• Docs followed: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-mcp-other-clients

What the docs tell you to do

1. Run this command:
   claude mcp add dataverse -t stdio -- npx -y @microsoft/dataverse mcp https://.crm.dynamics.com/
2. Enable the Dataverse MCP feature in the environment ✅ done
3. Enable "Dataverse CLI" in the Allowed MCP Clients list ✅ done
4. Grant admin consent via:
   https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id=0c412cc3-0dd6-449b-987f-05b053db9457
5. Restart Claude Code, sign in, and everything is supposed to "just work"

What actually happens

• claude mcp list reports dataverse: ✓ Connected — a lie. It's just the stdio handshake, no tools are ever exposed.
• On Claude Code restart, the browser login window pops up three times in a row. Each time the auth silently fails. No
  error code, no message, no traceback, nothing in the terminal. Just three browser tabs and three failures.
• Trying to pre-grant admin consent via the URL in step 4 hangs indefinitely on the sign-in page. Browser spins
  forever. Other Microsoft logins in the same browser session work fine — it's just this specific endpoint that's broken.
• There are zero logs, zero diagnostics, zero guidance on what's failing. The proxy happily says "Connected" and the
  MCP exposes no tools. You're left staring at an empty tool list with no way to figure out why.
• The docs don't mention that the "Dataverse CLI" first-party service principal may not even exist in the tenant until
  someone provisions it, which can silently cause the consent URL to hang. That should be in the docs at minimum, or
  better: fix the damn endpoint to return an error instead of hanging.

Start by reproducing the documented claude mcp add dataverse command with the listed Windows, Claude Code, Node and Dataverse setup, then compare the proxy's stdio handshake, browser login and exposed tool list. Read the Microsoft Learn MCP client documentation and inspect the admin-consent flow described there. Done means the authentication failure is diagnosable rather than silently looping, or the documentation clearly explains the required service-principal provisioning.