Skip to main content

Set up the DX MCP server

The DX MCP server gives AI agents access to DX's Data Cloud and software catalog — querying the underlying Postgres database and reading software-entity context, relationships, and scorecards. This guide covers creating a DX bearer token and connecting DX's hosted MCP server to MintMCP.

Prerequisites

  • A MintMCP admin account
  • A DX account with Data Cloud access
  • For per-user setup: each user needs permission to create a Personal Access Token in DX
  • For shared setup: a DX admin to create an organization token

Get a DX bearer token

DX authenticates with a bearer token. Choose the method that fits your team:

  • Per-user PAT (recommended): each user supplies their own token. DX attributes audits per user and applies that user's permissions. Best for analyst-facing deployments.
  • Shared org token: a single token used for all users. Best for read-only catalog and lookup use.

Each user does this once for themselves.

  1. Log in to DX and open your account settings.
  2. Go to Personal access tokens.
  3. Create a new Personal Access Token. Enable the read scopes you need exposed through MCP. Follow the principle of least privilege.
  4. Copy the token — you will paste it into MintMCP when connecting.

Scope reference:

CapabilityScope
Data Cloud readssnapshots:read
Software catalogcatalog:read
Scorecardsscorecards:read

Add DX to MintMCP

  1. In MintMCP, go to MCP store > Manage store.
  2. Click + Add an MCP to your registryConnect to an MCP by URL.
  3. Fill in the form:
    • Name: DX
    • MCP Server URL: https://ai.getdx.com/mcp
    • Authorization Method: Bearer Token
    • Connection Type: Per-user credentials
  4. Click Save.

When users connect, each person pastes their own DX PAT. DX sees each user individually and applies their permissions.

Security considerations

  • Personal Access Tokens reflect the creating user's existing DX permissions — each user can only access data they're already authorized to see.
  • Organization tokens run as a single shared identity. Limit scopes to the minimum your use case requires.
  • Rotate organization tokens from the same Admin > Organization tokens page where they were created.

Next steps