<h4>Use natural language to write and execute queries on your organizational data in DX Data Cloud!</h4>
Learn more about the Model Context Protocol (MCP).
The server publishes 4 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverCursor — Add this configuration to your MCP settings (Cursor > Settings > Cursor Settings > MCP):Configuration — Once installed, configure your AI client with the appropriate settings:Usage — After saving the configuration, restart your AI client. You should see "dx-mcp" in the available MCP servers. When you ask questions about your dataConfiguration is passed through the environment: DB_URL, WEB_API_TOKEN, YOUR_DX_API_TOKEN, YOUR_DB_URL, SESSION_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Dx's toolset — Prerequisites, Cursor, Configuration and 1 more — is a fair guide to whether it matches your workflow. It is maintained by get-dx; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Dx's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Cursor | Add this configuration to your MCP settings (**Cursor > Settings > Cursor Settings > MCP**): |
| Configuration | Once installed, configure your AI client with the appropriate settings: |
| Usage | After saving the configuration, restart your AI client. You should see "dx-mcp" in the available MCP servers. When you ask questions about your data or catalog, the AI will use these tools to query your database or hit t |
**If you're running from source:**
```json
{
"mcpServers": {
"dx-mcp": {
"command": "uv",
"args": ["--directory", "/path/to/dx-mcp-server", "run", "-m", "dx_mcp_server", "run"],
"env": {
"DB_URL": "YOUR-DATABASE-URL",
"WEB_API_TOKEN": "YOUR-DX-API-TOKEN"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DB_URL | Endpoint or connection string the server talks to. | Yes |
| WEB_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_DX_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_DB_URL | Endpoint or connection string the server talks to. | Yes |
| SESSION_ID | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.