@orphnet/d1-eloquent-mcp
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List all discovered BaseModel subclasses in the project, with table names and feature flags (soft deletes, revisions, relationships, casts). Read-only. |
| read_modelA | Return the full source code of a model file plus parsed metadata (relations, casts, static config). Read-only. |
| list_migrationsB | List all discovered migration files with timestamps. Read-only. |
| read_migrationB | Return the source of a migration file. Read-only. |
| migration_statusA | Run |
| inspect_schemaA | Query the local D1 |
| query_d1A | Run a read-only SQL query (SELECT / WITH / EXPLAIN / PRAGMA only) against the local D1. Multi-statement payloads and writes are rejected. |
| list_seedersA | List discovered seeder files. Read-only. |
| list_factoriesA | List discovered factory files. Read-only. |
| read_fileA | Read any project file by path (relative to project root). Read-only. |
| refresh_projectB | Re-run project discovery, update cached state. |
| 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. |
| validate_allA | Run validate_model across every discovered model. Returns per-model issues and a summary count of ok / warn / fail. |
| make_modelB | Scaffold a new model file. Delegates to |
| make_migrationB | Scaffold a new migration. Delegates to |
| make_seederC | Scaffold a new seeder. Delegates to |
| make_factoryB | Scaffold a new factory. Delegates to |
| make_resourceB | Scaffold model + migration + seeder + factory in one go. Delegates to |
| make_pivotB | Scaffold a pivot table migration. Delegates to |
| 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 |
| run_migrateB | Apply pending migrations. Delegates to |
| run_rollbackA | Roll back the last migration batch. Delegates to |
| run_freshA | Drop all tables and re-run every migration. Delegates to |
| run_seedC | Run seeders. Delegates to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-model | Multi-step walkthrough to scaffold a new model + its migration + seeder + factory, then verify. |
| audit-schema | Compare every model in the project against the actual D1 schema and report drift. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project summary | Discovered project state: models, migrations, seeders, factories, D1 bindings. |
| BaseModel API | |
| QueryBuilder API | |
| Relationships API | |
| Transactions API | |
| Quick start guide |
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.