MCP Dataverse MCP Server

The most complete MCP server for Microsoft Dataverse. 81 production-ready tools for AI agents: OData & FetchXML queries, CRUD, metadata, solutions, audit, batch operations, schema write, record access and more. Device code, client. The mcp dataverse mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

79 tools · 4 resources · 10 guided workflows · Three auth modes

• Three auth modes — — device code (local), client credentials (CI/CD), managed identity (Azure-hosted)
• Works with any MCP client — — VS Code, Claude, Cursor, Windsurf, Gemini, Codex CLI
• Atomic tools — — each tool does one thing well; the AI picks the right one
• Structured outputs — — every response returns {summary, data, suggestions}
• Guardrails — — destructive operations require explicit confirmation
• Encrypted tokens — — AES-256-GCM cached credentials, never logged

Its toolset

Everything the assistant can do here goes through one of these:

• Guardrails — destructive operations require explicit confirmation
• Mode — When to use
• Category — Count
• Metadata — 9
• Query — 3
• CRUD — 6
• Relations — 4
• Batch — 1
• Solutions — 2
• Search — 1
• RBAC — 7
• Files — 2

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: MCP_HTTP_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Dataverse's toolset — Guardrails, Mode, Category and 11 more — is a fair guide to whether it matches your workflow. It is maintained by codeurali; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Dataverse.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp dataverse mcp server does with a few real requests.