Dataverse MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dataverse MCP Serverlist the top 10 active accounts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dataverse MCP Server
An MCP server that gives AI agents structured access to Microsoft Dataverse — query records, inspect metadata, manage schema, manage model-driven app forms, views, and apps, manage plug-in trace logging, and explore Power Platform environments.
Built with FastMCP, httpx, and the Dataverse OData v4.0 Web API. Communicates over stdio and works with Claude, GitHub Copilot, and any MCP-compatible client.
Quick Start
1. Install uv
pip install uv2. Configure — add to your MCP client config:
Claude (claude_desktop_config.json or .claude/settings.json):
{
"mcpServers": {
"dataverse-mcp": {
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}GitHub Copilot (.vscode/mcp.json):
{
"servers": {
"dataverse-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}3. Sign in
az loginThat's it. Your AI agent can now query your Dataverse environments.
Related MCP server: Dataverse MCP Server
Installation
Install uv
uvx is provided by uv. Install it first if you don't have it:
pip install uvRun from PyPI (recommended)
uvx dataverse-mcpuvx downloads and runs the package in an isolated environment — no virtual environment management required.
Run from a local checkout
git clone https://github.com/ryanmichaeljames/dataverse-mcp.git
cd dataverse-mcp
uv syncThis creates .venv. Use the local source MCP config shown in Client Setup to point your client at it. No build step required — code changes are picked up on the next server start.
Configuration
Set these in the env block of your MCP server entry. This project does not use a .env file.
Variable | Default | Description |
|
| Authentication method: |
| — | Fallback org URL used when a tool call omits |
|
| Set to |
|
| Set to |
Authentication
Method | Description |
| Uses your active |
| Opens a browser window for interactive sign-in. |
Safety Guards
Most write and delete tools are not registered by default, so they do not appear to the agent until explicitly enabled. One exception is dataverse_execute_batch, which is always visible but only allows GET requests unless DATAVERSE_ALLOW_WRITE=true. This prevents accidental mutations when you only need to read or inspect data while still allowing safe batch reads by default.
{
"servers": {
"dataverse-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli",
"DATAVERSE_ALLOW_WRITE": "true",
"DATAVERSE_ALLOW_DELETE": "true"
}
}
}
}Each flag is independent — set only DATAVERSE_ALLOW_WRITE=true to allow creates and updates while keeping deletes disabled.
Client Setup
Claude
Claude Desktop
Add to claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"dataverse-mcp": {
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}Claude Code
Add via the CLI:
claude mcp add dataverse-mcp --env DATAVERSE_AUTH_TYPE=azure_cli uvx dataverse-mcpOr add directly to .claude/settings.json (project) or ~/.claude/settings.json (user):
{
"mcpServers": {
"dataverse-mcp": {
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}Run from a local checkout
{
"mcpServers": {
"dataverse-mcp-local": {
"command": "C:\\path\\to\\dataverse-mcp\\.venv\\Scripts\\python.exe",
"args": ["-m", "dataverse_mcp.server"],
"env": {
"PYTHONPATH": "C:\\path\\to\\dataverse-mcp\\src",
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}GitHub Copilot
Add to .vscode/mcp.json in your project root.
Run from PyPI
{
"servers": {
"dataverse-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["dataverse-mcp"],
"env": {
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}Run from a local checkout
{
"servers": {
"dataverse-mcp-local": {
"type": "stdio",
"command": "C:\\path\\to\\dataverse-mcp\\.venv\\Scripts\\python.exe",
"args": ["-m", "dataverse_mcp.server"],
"env": {
"PYTHONPATH": "C:\\path\\to\\dataverse-mcp\\src",
"DATAVERSE_AUTH_TYPE": "azure_cli"
}
}
}
}Multi-environment targeting
A single server instance can target any Dataverse org — pass dataverse_url on each tool call:
{
"dataverse_url": "https://yourorg.crm.dynamics.com",
"entity_set_name": "accounts",
"select": ["name", "accountid"],
"top": 10
}When dataverse_url is omitted, the server falls back to DATAVERSE_URL if configured. Use dataverse_list_environments to discover available environments first.
Tools
Always available
These 38 tools are registered regardless of safety guard settings.
Tool | Description |
| List Power Platform environments accessible to the authenticated user |
| Return the authenticated user's |
| List OData EntitySet names from the service document |
| List all security privileges assigned to a system user |
| Check access rights a user has to a specific record |
| List solutions with optional OData filter and pagination |
| Get a single solution by unique name or GUID |
| List components in a solution with optional type filter |
| Get cloud flows by query, and optionally scope to a solution by ID or unique name |
| Query records from any table with filter, select, orderby, expand, and top |
| Get a single record by entity set name and GUID |
| Count table rows with optional filter support |
| Execute aggregate queries (sum, avg, min, max, countdistinct) with optional grouping |
| Execute up to 1,000 OData operations in a single |
| List available tables with optional metadata filter |
| Get full schema details for a specific table |
| List column definitions for a table with optional type filter |
| Get full metadata for a single column including type-specific properties |
| Get all option values for a Picklist or MultiSelectPicklist column |
| List relationship definitions for a table or the entire environment |
| Get full metadata for a single relationship by schema name |
| Check whether a table can participate in a relationship before creating one |
| List all global choice (option set) definitions in the environment |
| Get a specific global choice by name or MetadataId, including all option values |
| List runtime performance statistics (execution count, failure rate, crash metrics) for plug-in types |
| Get the current organization-wide plug-in trace log verbosity (off / exception / all) |
| List plug-in trace log records with filters for class name, message, entity, operation type, exceptions-only, and time window |
| List connection references with optional filters for connector ID, status, and OData expression |
| Get a single connection reference by GUID or logical name |
| List model-driven app forms for a table with optional form type filter |
| Get a form's layout as a structured tabs → sections → controls tree |
| Validate FormXml against structural XSD rules; pass |
| List saved views (savedquery records) for a table with optional query type filter |
| Get a view's FetchXml, LayoutXml, and column list |
| Validate a view's FetchXml and LayoutXml against structural rules |
| List model-driven apps; set |
| Get a model-driven app's properties and component list grouped by type |
| Validate a model-driven app using ValidateApp — surfaces missing sitemap and other errors |
Requires DATAVERSE_ALLOW_WRITE=true
These 43 tools are only registered when DATAVERSE_ALLOW_WRITE=true is set.
Tool | Description |
| Associate two records via a collection-valued navigation property |
| Merge a subordinate record into a target record (account, contact, lead, incident) |
| Create a Dataverse publisher with unique name and customization prefixes |
| Update mutable publisher fields by publisher GUID |
| Create a solution with display name, version, and publisher binding |
| Update mutable solution fields by solution GUID or unique name |
| Update only the version of an existing solution |
| Add a component to a solution via the |
| Enable a single cloud flow by workflow ID |
| Enable multiple cloud flows in one |
| Disable a single cloud flow by workflow ID |
| Disable multiple cloud flows in one |
| Create a new custom table with display names, ownership type, and primary name attribute |
| Update an existing table's display name or description |
| Add a new typed column to a table |
| Update an existing column via full PUT — fetch current definition with |
| Create a 1:N relationship and its lookup column |
| Create an N:N relationship and its intersect table |
| Create a polymorphic lookup column referencing multiple tables |
| Update an existing relationship via full PUT — fetch current definition with |
| Create a new global choice with initial options |
| Update an existing global choice via full PUT — fetch current definition with |
| Add a new option to a global or local choice |
| Update the display label of an existing choice option |
| Reorder all options in a global or local choice |
| Publish schema changes via |
| Set the organization-wide plug-in trace log verbosity: |
| Create a connection reference with optional immediate connection assignment and optional solution association |
| Assign or clear a connection on a reference, update display name/description, or associate with a solution |
| Replace a form's FormXml directly and publish; validates before writing, returns |
| Add a column control to a form — resolves classid from column metadata automatically |
| Remove a column control from a form by logical name |
| Create a new saved view with FetchXml and LayoutXml |
| Update an existing view's FetchXml, LayoutXml, name, or description |
| Add a column to a view's LayoutXml |
| Remove a column from a view's LayoutXml |
| Create a model-driven app with auto-generated sitemap, entity components, validation, and publish |
| Update a model-driven app's name or description |
| Add tables, forms, views, charts, or BPFs to a model-driven app |
| Remove components from a model-driven app |
| Create or replace a model-driven app's navigation sitemap from a table list or structured areas |
| Publish a model-driven app to make it visible to users |
| Associate or disassociate a security role with a model-driven app |
Requires DATAVERSE_ALLOW_DELETE=true
These 8 tools are only registered when DATAVERSE_ALLOW_DELETE=true is set.
Tool | Description |
| Delete an unmanaged connection reference (managed ones must be removed via their solution) |
| Remove an association between two records |
| Remove a component from a solution via the |
| Permanently delete a custom table and all its data |
| Permanently delete a custom column and all its data |
| Delete a custom relationship by MetadataId |
| Delete a global choice by logical name |
| Remove a specific option value from a global or local choice |
Development
# Install dependencies
uv sync
# Run the MCP inspector (interactive testing)
uv run mcp dev src/dataverse_mcp/server.py
# Run the server directly
uv run python -m dataverse_mcp.server
# Compile check
uv run python -m py_compile src/dataverse_mcp/server.pyRestart the MCP server in VS Code after code changes to pick up the new source.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ryanmichaeljames/dataverse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server