@orphnet/d1-eloquent-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@orphnet/d1-eloquent-mcp what migrations are pending?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@orphnet/d1-eloquent-mcp
MCP server that gives Claude (and any Model Context Protocol–compatible client) live, context-aware access to your d1-eloquent project - models, migrations, schema, seeders, factories, and the CLI.
bunx @orphnet/d1-eloquent-mcpWhat it gives Claude
24 tools, 6 resources, 2 prompts.
Introspection (read-only)
list_models·read_model·list_migrations·read_migration·migration_statusinspect_schema- querysqlite_masterto see what's actually in your D1query_d1- read-only SQL against the local D1 (SELECT/WITH/EXPLAIN/PRAGMA only)list_seeders·list_factories·read_file·refresh_projectvalidate_model·validate_all- compare declared model shape against the actual schema, report drift
Generation (delegates to the d1-eloquent CLI)
make_model·make_migration·make_seeder·make_factorymake_resource- model + migration + seeder + factory in one gomake_pivot
Execution (delegates to the d1-eloquent CLI, local D1 by default)
run_migrate·run_rollback·run_fresh·run_seedrun_generate- schema-diff: write the migration that closes the gap between your models and the live schema
Resources - Claude can pull these in as background context
d1-eloquent://project/summary- your project's discovered stated1-eloquent://docs/api/base-modeld1-eloquent://docs/api/query-builderd1-eloquent://docs/api/relationshipsd1-eloquent://docs/api/transactionsd1-eloquent://docs/guide/quick-start
Prompts - pre-built multi-step workflows
create-model- scaffold + migrate + verify in one chataudit-schema- compare every model against the actual D1 schema, report drift
Related MCP server: MCP Database Bridge
Install
Claude Code
claude mcp add d1-eloquent -- bunx @orphnet/d1-eloquent-mcpClaude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"d1-eloquent": {
"command": "bunx",
"args": ["@orphnet/d1-eloquent-mcp"]
}
}
}Per-project (Claude Code)
.claude/mcp.json:
{
"mcpServers": {
"d1-eloquent": {
"command": "bunx",
"args": ["@orphnet/d1-eloquent-mcp"]
}
}
}To point at a project that isn't the current directory:
{
"mcpServers": {
"d1-eloquent": {
"command": "bunx",
"args": ["@orphnet/d1-eloquent-mcp", "--project", "/path/to/your/d1-eloquent-project"]
}
}
}Requirements
Node.js ≥ 22
wranglerinstalled and authenticated for D1 access (bun add -D wrangler)An existing
@orphnet/d1-eloquentproject - the server discovers models/migrations/seeders by scanning your file tree
Safety
query_d1rejects anything other thanSELECT/WITH/EXPLAIN/PRAGMA, and rejects multi-statement payloads.read_filerefuses paths containing..or starting with/.Generation tools shell out to your existing d1-eloquent CLI - they don't ship their own writers.
Execution tools (
run_migrate/run_rollback/run_fresh/run_seed) only operate on the local D1 by default. For remote, run via the CLI directly.
License
MIT
Available Tools
24 toolsinspect_schemaA
Query the local D1 sqlite_master to list every table + the column definitions actually applied. Read-only.
Inputs: db, table.
list_factoriesA
List discovered factory files. Read-only.
Inputs: no named parameters.
list_migrationsB
List all discovered migration files with timestamps. Read-only.
Inputs: no named parameters.
list_modelsA
List all discovered BaseModel subclasses in the project, with table names and feature flags (soft deletes, revisions, relationships, casts). Read-only.
Inputs: no named parameters.
list_seedersA
List discovered seeder files. Read-only.
Inputs: no named parameters.
make_factoryB
Scaffold a new factory. Delegates to d1-eloquent make:factory.
Inputs: name (required).
make_migrationB
Scaffold a new migration. Delegates to d1-eloquent make:migration.
Inputs: name (required).
make_modelB
Scaffold a new model file. Delegates to d1-eloquent make:model.
Inputs: name (required), softDeletes.
make_pivotB
Scaffold a pivot table migration. Delegates to d1-eloquent make:pivot.
Inputs: table (required).
make_resourceB
Scaffold model + migration + seeder + factory in one go. Delegates to d1-eloquent make:resource.
Inputs: name (required), softDeletes.
make_seederC
Scaffold a new seeder. Delegates to d1-eloquent make:seeder.
Inputs: name (required).
migration_statusA
Run d1-eloquent status against the local D1 - shows which migrations have run vs pending. Read-only. The CLI resolves the D1 binding from wrangler config automatically.
Inputs: no named parameters.
query_d1A
Run a read-only SQL query (SELECT / WITH / EXPLAIN / PRAGMA only) against the local D1. Multi-statement payloads and writes are rejected.
Inputs: sql (required), db.
read_fileA
Read any project file by path (relative to project root). Read-only.
Inputs: path (required).
read_migrationB
Return the source of a migration file. Read-only.
Inputs: name (required).
read_modelA
Return the full source code of a model file plus parsed metadata (relations, casts, static config). Read-only.
Inputs: name (required).
refresh_projectB
Re-run project discovery, update cached state.
Inputs: no named parameters.
run_freshA
Drop all tables and re-run every migration. Delegates to d1-eloquent fresh --force.
Inputs: no named parameters.
run_generateA
Diff models against the project's migrations (schema diff) and report what a reconciling migration would change. Dry-run by default: prints per-model added/dropped/type-changed columns and writes NOTHING. Pass write=true to emit migration file(s) into the project's migrations directory (review them, then run_migrate). Delegates to d1-eloquent generate.
Inputs: name, model, write.
run_migrateB
Apply pending migrations. Delegates to d1-eloquent migrate against local D1.
Inputs: no named parameters.
run_rollbackA
Roll back the last migration batch. Delegates to d1-eloquent rollback.
Inputs: no named parameters.
run_seedC
Run seeders. Delegates to d1-eloquent seed.
Inputs: seeder.
validate_allA
Run validate_model across every discovered model. Returns per-model issues and a summary count of ok / warn / fail.
Inputs: no named parameters.
validate_modelA
Compare a single model's declared shape (table, casts, softDeletes, timestamps, revisions) against the actual local D1 schema and return any drift as a list of issues.
Inputs: name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Each tool targets a distinct resource and action (list vs read vs make vs run vs validate). Even closely related tools like validate_model and validate_all are clearly differentiated by scope (single vs all). There is no ambiguity in purpose.
The overwhelming majority use verb_noun snake_case (list_*, make_*, run_*, read_*). The only deviation is migration_status, which uses noun_noun instead of a verb prefix, but this is a minor inconsistency that does not hinder readability.
At 24 tools, the set falls in the 16-25 range that feels heavy. While each tool serves a distinct purpose in the D1/Eloquent workflow, the high number may be overwhelming and includes some conveniences (like make_resource) that could be assembled from others.
The tool set covers the full lifecycle: listing/reading artifacts, scaffolding (model, migration, seeder, factory, pivot), running migrations/seeds/rollbacks, schema inspection, validation, and even raw SQL queries. No significant gaps are apparent for the stated scope.
Maintenance
Related MCP Connectors
Hosted SQL Server MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Build, deploy and manage MaShop e-commerce projects from Claude, Cursor or any MCP client.
Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Related MCP Servers
AlicenseAqualityDmaintenanceEnables AI-assisted analysis and optimization of Cloudflare D1 databases through comprehensive schema introspection, relationship mapping, validation, and optimization recommendations. Demonstrates semantic intent patterns with hexagonal architecture for maintainable database development workflows.43MIT- FlicenseNot gradedqualityCmaintenanceA secure, read-only MCP server that empowers Claude Desktop and AI agents to safely query and inspect local SQLite databases.-
- AlicenseNot gradedqualityBmaintenanceA Node.js MCP server that gives Claude Code direct access to file operations, database queries, PHP execution, SFTP deployment, and over 60 specialized tools for development and debugging.1MIT
- AlicenseAqualityCmaintenanceMCP server for Cloudflare D1 database introspection, providing schema analysis, relationship extraction, validation, and optimization suggestions via Semantic Intent patterns.52MIT