database-access. Keep production connections out of the allowlist or on Read only; Full access lets an agent change data.
Who it is forA developer who wants the coding agent to check real schema and data while writing queries and migrations.
The problemAgents guess at schemas, and giving them raw database credentials is risky.
The outcomeAn agent that queries your DBX connections through MCP with read only access to the connections you allow.
What you need first
- macOS, Windows or Linux desktop, Docker for team access, or the web version
- An AI provider for the SQL assistant: Claude, OpenAI or a local model via Ollama
- Node.js (npx) for the MCP server
Steps
- Install DBX and set up your connections in the app
- Run
npx @dbx-app/mcp-serveronce to check it starts - Add the DBX entry to your .mcp.json with command npx and args -y @dbx-app/mcp-server
- In DBX Settings, MCP, set the connection allowlist and choose Read only
- Ask the agent to inspect a table's schema and sample rows before writing a query
Prompt for your agent
Add the t8y2/dbx MCP server to this project's .mcp.json, then use it in read only mode to inspect the <table> schema on <connection> and write a query that <goal>. Do not run any write statements.
Caveat.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for t8y2/dbx and "Let Claude Code or Cursor query your databases, read only"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer