Connect to Dataverse with model context protocol FAQ

This article provides answers to frequently asked questions about using Microsoft Dataverse with a model context protocol (MCP) server.

I can’t authenticate. What is the problem?

Verify that the Dataverse environment URL in your MCP client configuration is correct. Go to Power Apps, select the correct environment, and then select Settings (gear icon) > Session details to confirm your instance URL.

Also verify that the MCP client you’re using is enabled in the Power Platform admin center. More information: Configure and manage the Dataverse MCP server for an environment

Which MCP tools are available and what do they do?

The Dataverse MCP server provides tools for common data operations such as querying records, creating and updating rows, and describing table schemas. For the full list of tools and descriptions, go to Connect to Dataverse with Model Context Protocol.

Can I restrict which tables or records are accessible through the MCP server?

Yes. The Dataverse MCP server respects Dataverse security roles and row-level security. Users can only access tables and records that their security role permits. No additional MCP-specific access controls are needed beyond standard Dataverse security configuration.

Are there costs associated with using the Dataverse MCP server?

Starting December 15, 2025, Dataverse MCP tools are charged when accessed by AI agents created outside of Microsoft Copilot Studio. If you have qualifying Dynamics 365 Premium licenses or a Microsoft 365 Copilot User Subscription License (USL), you aren’t charged for accessing Dynamics 365 data. For information about billing rates, go to Connect to Dataverse with Model Context Protocol.

Can I use the Dataverse MCP server with multiple environments?

Yes. Each Dataverse environment can have its own MCP server configuration. You can connect to multiple environments by configuring separate MCP server entries in your client, each pointing to a different environment URL.

Tip

If you use Microsoft Copilot Studio, you can use the MCP onboarding wizard to connect your agent to Dataverse MCP servers across multiple environments. The wizard guides you through server configuration and authentication setup. More information: Connect your agent to an existing MCP server

What should I do if a Dataverse MCP tool returns an error?

If a tool returns an error, try rephrasing your prompt and submitting it again. Use more specific language to describe what you want to accomplish. If the error persists, verify that you have the appropriate Dataverse permissions for the operation you’re attempting.

What happened to the describe_table, list_tables, and fetch tools?

The Dataverse MCP server tool surface is updated. The previous describe_table, list_tables, and fetch tools are removed and their functionality is provided by other tools:

Removed tool	Replacement
describe_table	describe
list_tables	describe
fetch	describe

The previous search tool that searched Dataverse data was renamed to search_data. The current search tool searches Dataverse metadata to help agents find relevant tables and apps.

If your MCP client maintains allow or deny lists by tool name, review and update your configuration so that the new tool names reflect your intended permissions.

For the full list of tools, go to Connect to Dataverse with Model Context Protocol.

Why don't I see the search_data tool in the Dataverse MCP server?

The search_data tool is only available when Dataverse search is enabled for your environment. If Dataverse search isn't turned on, the search_data tool doesn't appear in the list of available MCP tools. To enable Dataverse search, go to Configure Dataverse search for your environment.

Why do I see different tools on the /api/mcp and /api/mcp_preview endpoints?

The /api/mcp endpoint provides the generally available set of Dataverse MCP tools. The /api/mcp_preview endpoint includes additional preview tools that are evaluated before general availability. Preview tools might change or be removed without notice. To access the preview tools, an administrator must enable the preview features setting in the Power Platform admin center. More information: Use preview tools and upcoming features in Dataverse MCP server

How do I enable debug logging for the local proxy?

If you experience issues with the local proxy (@microsoft/dataverse), you can enable debug logging to capture detailed output for troubleshooting. Add the --log-level and --log-file arguments to the proxy command:

npx @microsoft/dataverse mcp https://yourorg.crm.dynamics.com --log-level Debug --log-file

The log file is written to the system temporary directory. The default location depends on your operating system:

Operating system	Log file location
Windows	C:\Users\<username>\AppData\Local\Temp\
Linux	/tmp/
macOS	The directory specified by the $TMPDIR environment variable, typically /var/folders/.../T/. Run echo $TMPDIR in a terminal to find the exact path.

You can share the output log file with Microsoft when opening a support incident to help diagnose the issue.