Orm Mcp
Generate, lint with 24 rules, and migrate @mostajs/orm EntitySchemas from your agent during backend modeling.
Overview
orm-mcp is a MCP server for the Build phase that generates, lints (24 rules), and migrates @mostajs/orm EntitySchemas for agents.
What is this MCP server?
- MCP wrapper for @mostajs/orm EntitySchema workflows
- Lint pass with 24 documented rules for schema quality
- Generate and migrate commands exposed as agent tools
- npm @mostajs/orm-mcp v0.1.1 with stdio transport
- Repository: github.com/apolocine/mosta-orm-mcp
- 24 lint rules (catalog description)
- npm @mostajs/orm-mcp version 0.1.1, stdio transport
- Tools: generate, lint, migrate EntitySchemas (catalog description)
What problem does it solve?
Hand-rolling ORM schemas and migrations in chat leads to drift and missed validation rules on small teams.
Who is it for?
Builders committed to @mostajs/orm who want generate/lint/migrate in the same agent session as coding.
Skip if: Projects on Prisma, Drizzle, or other ORMs without adopting mostajs/orm.
What do I get? / Deliverables
Your agent can produce linted EntitySchemas and migration steps through a single ORM-focused MCP toolchain.
- Generated EntitySchema artifacts from agent prompts
- Lint feedback against 24 ORM rules before merge
- Migration-oriented outputs aligned with @mostajs/orm workflows
Recommended MCP Servers
Journey fit
How it compares
ORM schema MCP with 24 lint rules, not a general-purpose 13-database query gateway.
Common Questions / FAQ
Who is orm-mcp for?
Solo developers using @mostajs/orm who want MCP tools for EntitySchema generation, linting, and migrations.
When should I use orm-mcp?
Use it while defining or changing backend models during build, especially before applying migrations to shared databases.
How do I add orm-mcp to my agent?
Install @mostajs/orm-mcp from npm, add a stdio MCP server entry in your client, and ensure @mostajs/orm is available in the project workspace.