Drizzle MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| drizzle_generate_migrationB | Generate a new migration file using drizzle-kit |
| drizzle_run_migrationsA | Run pending migrations using drizzle-kit |
| drizzle_introspect_schemaB | Introspect database schema using drizzle-kit |
| execute_queryB | Execute a raw SQL query on the database |
| initialize_databaseC | Initialize database connection |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Database Tables | List all tables in the database |
| Database Schema | Complete database schema information |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: generating migrations, running migrations, introspecting schema, executing raw SQL, and initializing the connection. There is no overlap or ambiguity among them.
The three drizzle-kit related tools use the 'drizzle_' prefix (e.g., drizzle_generate_migration) while the other two tools (execute_query, initialize_database) do not follow this prefix pattern. This creates a minor inconsistency, though all names are still snake_case and readable.
With only 5 tools, the server is well-scoped for its purpose of handling Drizzle migrations and database interactions. Each tool is essential and the count is neither too sparse nor overwhelming.
The server covers the core lifecycle of Drizzle migrations (generate, run, introspect) and provides raw query access for additional operations. A minor gap is the lack of a dedicated migration rollback or status tool, but raw SQL and introspection can compensate.