How to Connect Claude Code to a Database (Safely)

To connect Claude Code to a database, you give it a bridge rather than a password. That bridge is an MCP server - a small program that exposes your database to Claude as a set of safe actions like list tables, describe a table, and run a query. You point that server at a read-only connection, add it to Claude Code (the desktop app has an MCP settings panel, and the terminal has a command for the same thing), and from then on Claude can explore your data and answer questions about it without you ever pasting rows into the chat. The entire safety of this setup rests on one choice: the connection is read-only, so the worst Claude can do is read.

MCP stands for Model Context Protocol. It is the standard way Claude Code talks to outside systems - databases, APIs, file stores. A database MCP server sits between Claude and your database and translates Claude's requests into real queries. Instead of Claude holding your credentials, the server holds them, and Claude only sees the actions the server chooses to offer: read the schema, list tables, run a SELECT. This is why the bridge is safer than direct access - you decide at the server what Claude is allowed to touch.

Before you connect anything, make a dedicated database user that can read and nothing else. Do not point Claude at your application's main user or an admin account. Create a fresh user, grant it SELECT on the tables or schema you want Claude to see, and stop there. On Postgres that is a CREATE USER followed by a GRANT SELECT; most databases have the same two steps. The point is that even a badly phrased request - or a confused model - cannot delete, update, or escalate, because the account it is using was never given the power to.

With a read-only user in hand, add the database MCP server to Claude Code and give it the read-only connection string through an environment variable. In the desktop app you do this in the MCP settings; from the terminal there is an add command for the same thing. Put the connection string in your environment or a local secrets file that is git-ignored - never inline it in a prompt, and never commit it. When the server starts, Claude Code loads it as a new source of tools it can call during a session.

Do not assume the connection is safe because it works. Confirm it. In Claude Code, check that the database server is listed and connected, then ask Claude to list the tables and describe one - that proves the read path works. Then test the guardrail directly: ask it to make a trivial write, like inserting a throwaway row, and confirm the database refuses because the user has no permission. A bridge you have watched fail closed is one you can trust. A bridge you only watched succeed is one you are hoping about.

The Read-Only Bridge is the CCC name for this whole pattern: a least-privilege user, a connection string kept out of the chat, and an MCP server that exposes read actions only. It is the default because it makes the dangerous version impossible rather than merely discouraged. You are not trusting Claude to behave - you are removing its ability to misbehave. That is the same principle that keeps a production database safe from a junior engineer: not a promise to be careful, but permissions that make carelessness harmless.

Sometimes reading is not enough - you want Claude to help run a migration or seed test data. Do not solve this by loosening the read-only user. Create a second, separate user with exactly the writes that task needs, use it for that task only, and review every statement before it runs. Better still, have Claude generate the migration as a file you read and apply yourself, so the review step is built in. Write access is a deliberate, scoped exception you turn on for a job and turn off after, not a permanent property of the bridge.

This read-only-first approach to connecting Claude Code to real systems is exactly the kind of thing we build and pressure-test together inside Claude Code Club. If you want the working configs, the safety checklists, and other members who are wiring Claude into their own stacks, join the Club and grab the newsletter - that is where the details that do not fit in a blog post live.