Drizzle MCP

drizzle-mcp

Drizzle Studio for agents. An MCP server that lets Claude Code, Cursor and other coding agents see your database through your Drizzle schema.

A generic database MCP sees tables and columns. This one reads the schema your code uses: TypeScript names next to SQL names, relations, enums and defaults. An agent can then answer "what's actually in the database?" and write Drizzle code that matches it.

For migrations, use Drizzle's own drizzle-kit mcp (drizzle-kit 1.0): it generates, pushes and checks them. drizzle-mcp reads what's in the database, read-only by default, so the two work side by side.

If it's useful to you, a star on GitHub helps other people find it. Questions, bug reports and ideas are welcome in the issues, and so are pull requests.

Here is what an agent gets back when it asks about a posts table:

## posts

SQL table posts, exported as posts from src/db/schema.ts.

Relations (for browse with with, or db.query in code):

• author: one users on posts.authorId = users.id
• comments: many comments on posts.id = comments.postId

Set up

Run it from the folder with drizzle.config.ts.

Claude Code

claude mcp add drizzle -- npx -y drizzle-mcp

Cursor (.cursor/mcp.json) and VS Code (.vscode/mcp.json, with "servers" instead of "mcpServers"):

{

"mcpServers": { "drizzle": { "command": "npx", "args": ["-y", "drizzle-mcp"] } } }

For clients that don't start servers in your project folder, such as Claude Desktop, add "--config", "/path/to/drizzle.config.ts" to args.

drizzle-mcp loads your config the way drizzle-kit does, including your .env. It connects with the database driver and the drizzle-orm version your project already has installed.

Tools

Filters are JSON, so values are always bound as parameters, never pasted into SQL:

{ "published": true, "createdAt": { "gte": "2026-01-01" }, "or": [{ "title": { "ilike": "%drizzle%" } }, { "rating": { "gte": 4.5 } }] }

If you edit the schema, the server picks up the change on the next call; no restart needed.

Safe by default

An agent shouldn't be able to wreck a database by accident, or because something it read told it to.

• Read-only. Every statement runs in a read-only transaction. SQLite reads use a read-only connection.
• One statement at a time. select 1; commit; drop table users is refused before it reaches the database. The Postgres drivers and better-sqlite3 would refuse it again on their own; libsql would silently drop everything after the first statement.
• Bounded. Statements time out after 15 seconds. Results are capped at 100 rows and fetched through a cursor, so a large table is never pulled into memory. Long values are cut short.
• Secrets hidden. Values in columns named like password, token, secret or apiKey are shown as [redacted].
• Writes are opt-in. --allow-writes adds the execute tool. query stays read-only either way.

Requirements

MySQL isn't supported yet.

drizzle-mcp needs Node.js 22 or newer. It's tested with drizzle-orm 0.45, the current stable release. Drizzle 1.0, now in release candidates, defines relations differently and isn't supported yet.

Options

--config <path>     The Drizzle config (default: drizzle.config.ts in the current folder)

--url Connect here instead of the config's dbCredentials --driver pg, postgres, pglite, better-sqlite3 or libsql (default: the one installed) --allow-writes Add the execute tool --max-rows The most rows a tool returns (default: 100) --timeout Statement time limit (default: 15000) --max-text Cut strings longer than this (default: 500) --redact Hide columns whose names match (default: password, secret, token…) --show-secrets Don't hide any columns

How it works

1. It loads drizzle.config.ts and your .env, then imports the schema files the config points to (a file, a folder or a glob). Imports go through jiti, so TypeScript works without a build step.
2. It reads tables, columns and relations from drizzle-orm's own metadata. This is the same information drizzle-kit and relational queries use. That's where the TypeScript names and relations come from.
3. It connects with your project's driver. browse and count build relational queries with your schema objects. query runs plain SQL through the safeguards above.

Development

pnpm install

pnpm check # types, lint and 145 tests

The tests run every tool against every driver. Postgres runs as PGlite, which is real Postgres compiled to WebAssembly. pg and postgres.js reach it over the Postgres wire protocol, so no Docker is needed.

Pull requests are welcome. Run pnpm check before opening one, and for anything large, open an issue first so we can agree on the approach.

License

MIT