Databases (read-only, switchable)

mcp-db-read-only

Let your AI assistant look at your databases without being able to change them.

Point it at MySQL, PostgreSQL, SQLite, SQL Server, ClickHouse, MongoDB, Redis or Elasticsearch, then just ask questions in plain words: *"how many users signed up this week?"*, *"what's in the orders table?"*, *"which Redis keys hold sessions?"*. It can read anything you give it access to, and it cannot write, update or delete anything.

• Every popular database, one server. Switch between them in the middle of a conversation.
• Read-only, twice over. Every query is checked before it is sent, and the database itself is also told to refuse writes.
• No restart to switch. Change database, server or engine by asking.
• Optional logging, with a live page in your browser that shows every query as it happens.

flowchart LR

Y["You"] -->|"ask in plain words"| AI["Your AI assistant"] AI -->|"tool call"| S["mcp-db-read-only"] S -->|"read-only query"| DB[("Your databases")] DB -->|"rows, documents, keys"| S

Works with Claude Desktop, Claude Code, and any other MCP client.

Quick start

1. Have Node.js 22.13 or newer (node --version), or Docker.

2. Add the server to your client. For Claude Desktop, edit claude_desktop_config.json (Settings, Developer, Edit Config). For Claude Code, create .mcp.json in your project:

{

"mcpServers": { "databases": { "command": "npx", "args": ["-y", "@shibbirweb/mcp-db-read-only"], "env": { "DB_URL": "postgres://readonly:secret@localhost:5432/myapp" } } } }

Replace the DB_URL with your own database. The examples below show one for every kind.

3. Restart the client once, and ask away:

"What tables are in my database?"

"Show me the 5 newest orders."

"How many customers are in each country?"

That's it. You never need to restart again to change database; just ask the assistant to switch.

Examples for each database

Each database has a URL format, then a real example to copy and change. Put the finished URL in DB_URL.

Replace each [PLACEHOLDER] with your own value:

No password? Leave out :[PASSWORD]. No user either? Leave out [USER]:[PASSWORD]@ entirely.

MySQL and MariaDB

Format (usual port 3306):

mysql://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

mariadb://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

Example:

mysql://readonly:secret@localhost:3306/shop

"List the tables in shop." · "Describe the orders table." · "What were last month's top 10 products by revenue?"

PostgreSQL

Format (usual port 5432). Add ?sslmode=require to use TLS:

postgres://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

Example:

postgres://readonly:secret@localhost:5432/myapp

"Which tables are in the reporting schema?" · "Show the foreign keys on invoices." · "Count signups per day this week."

SQLite

Format (three slashes, then the full path to the file):

sqlite:///[PATH_TO_FILE]

Example:

sqlite:///Users/me/data/app.db

The file is opened read-only.

"What tables does this file have?" · "Show 10 rows from notes."

SQL Server (and Azure SQL)

Format (usual port 1433). Add ?trustServerCertificate=true for a local server with a self-signed certificate:

mssql://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

Example:

mssql://readonly:secret@localhost:1433/Sales?trustServerCertificate=true

"List the tables in Sales." · "Show the top 5 customers by order total." (SQL Server uses TOP 5, not LIMIT; the assistant knows.)

ClickHouse

Format (usual port 8123, or 8443 with clickhouse+https):

clickhouse://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

clickhouse+https://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]

Example:

clickhouse://reader:secret@localhost:8123/analytics

"How many events per hour did we have yesterday?" · "What is the sorting key of the events table?"

MongoDB

Format (usual port 27017). Use mongodb+srv for MongoDB Atlas, with no port:

mongodb://[USER]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]?authSource=admin

mongodb+srv://[USER]:[PASSWORD]@[CLUSTER_HOST]/[DATABASE]

Example:

mongodb://reader:secret@localhost:27017/myapp?authSource=admin

"What collections are in myapp?" · "What fields do documents in users have?" · "Find the 5 most recent orders over 100." · "Count users by country."

Redis (and Valkey, KeyDB)

Format (usual port 6379). [DB_NUMBER] is the database number, 0 if left out; rediss means TLS:

redis://[USER]:[PASSWORD]@[HOST]:[PORT]/[DB_NUMBER]

rediss://[USER]:[PASSWORD]@[HOST]:[PORT]/[DB_NUMBER]

Example:

redis://localhost:6379/0

"Which keys start with session:?" · "What's inside user:42?" · "How long until cache:home expires?"

Elasticsearch and OpenSearch

Format (usual port 9200, no database). Add +https for TLS, or ?api_key=[API_KEY] instead of a user and password:

elasticsearch://[USER]:[PASSWORD]@[HOST]:[PORT]

opensearch://[USER]:[PASSWORD]@[HOST]:[PORT]

Example:

elasticsearch+https://elastic:secret@search.example.com:9200

"What indices do we have?" · "Find error logs from the last hour." · "How many documents are in logs-2026.09?"

Detailed notes for every database, including how to create a read-only account, are in the Databases guide.

Using several databases

Give each one a name with DB_PROFILES, and switch by asking ("switch to legacy", "use the cache"):

"env": {

"DB_PROFILES": "{\"app\": \"postgres://readonly@localhost/app\", \"legacy\": \"mysql://readonly@localhost/shop\", \"cache\": \"redis://localhost:6379/0\"}", "DB_DEFAULT_PROFILE": "app" }

You can also connect to a database you didn't list, mid-conversation: *"connect to postgres://readonly@10.0.0.5/reports"*.

Password with special characters (@, /, #)? Give it separately instead of inside the URL: DB_PASSWORD next to DB_URL, or {"url": "...", "password": "..."} inside DB_PROFILES.

Running with Docker

Nothing to install but Docker:

{

"mcpServers": { "databases": { "command": "docker", "args": [ "run", "-i", "--rm", "--add-host", "host.docker.internal:host-gateway", "-e", "DB_URL=postgres://readonly:secret@host.docker.internal:5432/myapp", "shibbirweb/mcp-db-read-only" ] } } }

Inside Docker, use host.docker.internal instead of localhost to reach a database on your own computer. For SQLite, mount the folder: add "-v", "/Users/me/data:/data:ro" and use sqlite:///data/app.db.

Watching what the assistant does

Turn on logging to keep a record of every query the assistant runs, and see them live in your browser.

flowchart LR

S["mcp-db-read-only (in your AI client)"] -->|"one file per call"| F[("Log folder DB_LOG_DIR")] F --> V["viewer command (in a terminal)"] V -->|"live"| B["Your browser"]

1. Save logs to a folder by adding this to the server's env:

"DB_LOG_DIR": "/Users/me/Library/Logs/mcp-db-read-only"

Each query is saved as its own file, one folder per day. Nothing is ever deleted automatically.

2. Open the viewer in a terminal, whenever you want to watch:

npx -y @shibbirweb/mcp-db-read-only viewer --dir /Users/me/Library/Logs/mcp-db-read-only --port 4800

Then open http://127.0.0.1:4800/. You'll see every call: what was asked, the exact query sent, how long it took, and the result. It updates live, shows 20 per page (10, 20, 30 or 50 to choose from), and lets you filter and copy anything. Press Ctrl+C to close it.

The viewer has no password. Anyone who can reach that port on your network can read the log while it runs.

Passwords are never written to the logs. More in the Logging guide.

Is it really read-only?

Yes, in two independent ways, so a mistake in one is caught by the other:

flowchart LR

Q["The assistant writes a query"] --> C{"1. Checked by this server: only a read?"} C -->|"no"| R1["Refused, with the reason"] C -->|"yes"| D["2. Sent to the database in read-only mode"] D -->|"a read"| A["The answer"] D -->|"a write that slipped through"| R2["Refused by the database"]

1. Before anything is sent, every query is checked. Only reads are allowed: SELECT and friends for SQL, read commands for Redis, searches for Elasticsearch, and no $out or $merge for MongoDB.
2. The database is told to refuse writes too, wherever it supports that: read-only sessions on MySQL, read-only transactions on PostgreSQL, a read-only file on SQLite, and so on.

The best protection is still a read-only database account. Then nothing can write through it, whatever happens. The Databases guide shows how to create one for each database.

Keep in mind that the assistant can read whatever the account can see, and what it reads becomes part of your conversation with the AI provider. Only connect accounts that can see data you are happy to share. See PRIVACY.md.

Settings

All optional. Set them in the server's env.

Coming from mcp-mysql-read-only? Its MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE and MYSQL_PROFILES settings st