Dash MCP on Dash Enterprise

This documentation is for Dash Enterprise.
Dash Enterprise is the fastest way to write & deploy Dash apps and
Jupyter notebooks.
10% of the Fortune 500 uses Dash Enterprise to productionize AI and
data science apps. Find out if your company is using Dash Enterprise.

Dash apps can act as MCP servers, letting AI agents like Claude and Cursor discover and interact with your app’s data and callbacks directly.

Once a user points their AI agent at your app, it can answer questions about your specific datasets, charts, and analyses by executing the callbacks you have written. Rather than drawing on general knowledge, the agent queries your app to discover trustworthy, domain-specific answers.

This guide describes Dash MCP usage on Dash Enterprise.

Enabling MCP for an App

Enabling MCP requires that your app uses dash>=4.4.1. There are two ways to enable the MCP server for an app on Dash Enterprise:

<img>

Note: enable_mcp in code always takes precedence over the App Info toggle. If your app hard-codes Dash(enable_mcp=False), the toggle will not enable the MCP server; and for Dash(enable_mcp=True), the toggle will not disable it.

Connecting an AI Agent

When MCP is enabled, the MCP tab displays the app’s MCP endpoint. By default, it’s your app’s URL followed by _mcp:

<a href="https://&lt;your-dash-enterprise-server&gt;/&lt;app-name&gt;/_mcp">https://&lt;your-dash-enterprise-server&gt;/&lt;app-name&gt;/_mcp</a>

The MCP tab displays connection instructions for each supported agent.

The app endpoint is pre-filled for you. Select Copy to copy the endpoint, or Edit to change the path (for example, if _mcp collides with a route in your app). The path can contain only letters, numbers, hyphens, and underscores.

Note that the instructions vary according to your agent, app name, and app settings. Instructions for connecting Claude to an Authenticated or Restricted app look similar to the example below.

<img>

Instructions for Unauthenticated apps do not include a step for setting the OAuth Client ID.

Follow the steps in the MCP tab to connect your agent.

Authentication and Access

On Dash Enterprise, MCP access follows your app’s viewer access settings. If viewer access is Restricted or Authenticated, agents must complete a sign-in flow, and only users with access to the app can connect.

For the full details on what AI agents can access and how to control it, see the Dash MCP documentation.

Troubleshooting

Client Registration Errors

When you connect an AI agent to an Authenticated or Restricted app, the connection fails with an error about client registration. For example, Cursor shows the following error:

Policy 'Trusted Hosts' rejected request to client-registration service. Details: Host not trusted.

This happens when the agent tries to register itself as a new OAuth client with Dash Enterprise (dynamic client registration). By default, Keycloak only accepts registration requests from trusted hosts, so it rejects the request. Agents usually do this when they aren’t configured with an OAuth client ID.

How you fix it depends on whether the agent lets you set a client ID.

Agents That Accept a Client ID

Set the agent’s OAuth client ID to mcp-agent. The agent then uses this existing client and skips registration. Where you set the client ID depends on the agent, so check its documentation for OAuth or authentication settings.

For example, in Cursor, add the client ID to the server entry in your MCP config:

{
  "mcpServers": {
    "&lt;app-name&gt;": {
      "type": "http",
      "url": "https://&lt;your-dash-enterprise-server&gt;/&lt;app-name&gt;/_mcp",
      "auth": {
        "CLIENT_ID": "mcp-agent"
      }
    }
  }
}

Save the config and connect again. The agent opens a browser window so you can sign in to Dash Enterprise.

Microsoft Copilot Studio

Copilot Studio offers two ways to configure OAuth 2.0 for an MCP tool: Dynamic discovery and Manual. Both require changes in the Keycloak admin console, so you’ll need a Keycloak administrator to make them.

With Dynamic discovery, Copilot Studio registers itself as a client. To allow this, a Keycloak administrator adds Microsoft’s hosts to the Trusted Hosts client registration policy, which makes the policy less strict: anyone can then register an OAuth client with Dash Enterprise that uses redirect URIs on those hosts.

With Manual, you enter the mcp-agent client details in Copilot Studio yourself, so no registration is needed and the Trusted Hosts policy doesn’t change. Instead, a Keycloak administrator allows Copilot Studio’s redirect URIs on the mcp-agent client. If your organization doesn’t allow changes to the Trusted Hosts policy, use this option.

To allow Copilot Studio to register itself, add Microsoft’s hosts to the Trusted Hosts policy:

  1. Log in to Keycloak at https://auth-&lt;your-dash-enterprise-server&gt;, and make sure dash is selected in the realm list.
  2. Go to Clients > Client registration > Anonymous access policies, and select Trusted Hosts.
  3. Add global.consent.azure-apim.net and copilotstudio.microsoft.com to Trusted Hosts.
  4. Select Save.

If registration still fails with Host not trusted, or with URL doesn't match any trusted host or trusted domain, the request may be coming from a Microsoft host that isn’t on the list. Add that host to Trusted Hosts, or turn off Host Sending Client Registration Request Must Match. Turning off this setting removes the check on where registration requests come from, so prefer adding the host when you can identify it.

After you update the Trusted Hosts policy, add the MCP tool in Copilot Studio with OAuth 2.0 > Dynamic discovery and connect again.

To use the existing mcp-agent client, first allow Copilot Studio’s redirect URIs on the client:

  1. Log in to Keycloak at https://auth-&lt;your-dash-enterprise-server&gt;, and make sure dash is selected in the realm list.
  2. Go to Clients and select mcp-agent.
  3. In Valid redirect URIs, add https://global.consent.azure-apim.net/redirect/* and https://copilotstudio.microsoft.com/*. Copilot Studio redirect URIs often end with a suffix that is different for each connector, so include the wildcard (*).
  4. In Web origins, add https://global.consent.azure-apim.net and https://copilotstudio.microsoft.com.
  5. Select Save.

Then, in Copilot Studio, add the MCP tool with OAuth 2.0 > Manual, and enter the following values:

Field Value
Client ID mcp-agent
Client secret Leave blank
Authorization URL https://auth-&lt;your-dash-enterprise-server&gt;/auth/realms/dash/protocol/openid-connect/auth
Token URL https://auth-&lt;your-dash-enterprise-server&gt;/auth/realms/dash/protocol/openid-connect/token
Refresh URL https://auth-&lt;your-dash-enterprise-server&gt;/auth/realms/dash/protocol/openid-connect/token
Scope openid

Replace &lt;your-dash-enterprise-server&gt; with the domain of your Dash Enterprise server. For example, if your Dash Enterprise URL is https://dash.example.com, the authorization URL is https://auth-dash.example.com/auth/realms/dash/protocol/openid-connect/auth.