drizzle mcp

    1

    Drizzle Studio for agents. Read the database through the project's own Drizzle schema, safely.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    drizzle mcp

    Example session with this skill installed

    List the columns for the 'users' table and show me 3 recent signups where the email is verified.

    • Read your context and instructions
    • Compiled the drizzle mcp

    I have inspected the users table schema and retrieved the most recent verified signups. The database confirms the schema matches your TypeScript definitions, and I've retrieved the records using the browse tool with a filter on emailVerified.

    Database Inspection: users

    TS PropertySQL ColumnTypeNullableReferences
    ididuuidNo-
    emailemailtextNo-
    emailVerifiedemail_verifiedtimestampYes-
    roleroleuser_roleNo-
    createdAtcreated_attimestampNo-

    Recent Verified Signups

    idemailemailVerifiedrolecreatedAt
    7b2...dev_lead@example.com2024-05-20T10:00:00Zadmin2024-05-20T09:45:00Z
    a1f...tester@acme.org2024-05-19T14:20:00Zuser2024-05-19T14:10:00Z
    e89...ops@infra.net2024-05-19T08:12:00Zuser2024-05-19T08:00:00Z

    Next steps

    1. Would you like me to generate a Drizzle query to fetch all users with the admin role?
    2. I can check for any schema drift if you suspect the user_role enum has changed in production.
    3. Run explain on a count query if you are seeing latency on the users table.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Working with Drizzle ORM often leaves you guessing if your TypeScript schema actually matches the production database state. You waste time debugging failed queries or mismatched migrations when local files drift from the live data.

    What it does

    • Schema inspection shows TypeScript keys alongside SQL names, relations, enums, and default values.
    • Safe data browsing reads rows using JSON-based filters with support for relations, sorting, and pagination.
    • Drift detection identifies discrepancies between your drizzle.config.ts and the physical database tables.
    • Query optimization runs SQL EXPLAIN to verify index usage and diagnose slow-performing queries.
    • Migration tracking lists applied, pending, or edited migrations from your drizzle-kit directory.

    How it works

    1. Initialize the server by running the MCP command in your project root containing drizzle.config.ts.
    2. Audit the schema using the schema command to verify column names and relations before writing code.
    3. Verify data with browse or count to understand the actual shapes and distributions of your records.
    4. Debug issues using drift to find schema mismatches or migrations to check the deployment state.

    Frameworks & tools

    This tool requires Node.js 22 or newer and drizzle-orm 0.45. It supports PostgreSQL (pg, postgres, PGlite) and SQLite (better-sqlite3, libsql).

    Why this beats prompting it yourself

    Generic agents only see your static files and often hallucinate table structures or column types that have changed in the real database. This skill provides live, read-only access to the source of truth, ensuring the code the agent writes actually runs against your specific data.

    Use cases

    • Debugging why a Drizzle query returns undefined for a specific relation.
    • Writing complex db.query.findMany calls with filters that match real-world data.
    • Checking if a new migration was successfully applied to the remote database.
    • Analyzing query plans to determine if a new index is required for performance.

    Known limitations

    Does not support MySQL or Drizzle 1.0 beta. Write operations are disabled by default. Sensitive columns like passwords or secret keys are automatically redacted in tool outputs.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.

    Requires Node.js 22+, drizzle-orm 0.45, and PostgreSQL or SQLite. MySQL and Drizzle 1.0 beta are not supported. Results are capped at 100 rows by default.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    • Free with an Agensi account

    Software
    Node.js

    Permissions

    Read Files
    Network Access

    https://github.com/fredobumma/drizzle-mcp

    Listed11 days ago

    What's inside

    Frequently Asked Questions

    This skill solves 'schema drift' by giving your AI agent live, read-only access to your actual database state, preventing it from hallucinating table structures or column names that might differ from your TypeScript files.

    The tool is compatible with any MCP-enabled environment (like Claude Desktop or Cursor) and supports PostgreSQL (pg, postgres, PGlite) and SQLite (better-sqlite3, libsql) environments.

    No, this skill is designed for safe introspection and debugging; it features read-only access by default and automatically redacts sensitive columns like passwords or secret keys from the AI's view.

    You need Node.js 22+ and drizzle-orm 0.45+; simply run the MCP command in your project root where your `drizzle.config.ts` is located to initialize the server.

    The 'drift' command compares your local `drizzle.config.ts` against the physical database tables, while the 'migrations' command tracks which scripts from your drizzle-kit directory have actually been applied.

    New in Data & Databases

    Free