mern-mcp
Related Servers
Alternatives to mern-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables rapid creation of new projects from predefined templates including React, Node.js, Django, Flask, and more. Provides comprehensive project scaffolding with file system operations, template management, and command execution capabilities.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to scaffold and manage NetSuite apps built with React, including generating script files, retrieving project information, and listing supported script types.GPL 3.0
- AlicenseBqualityDmaintenanceEnables execution of terminal commands, git operations, and automated setup of React, Vue, and Next.js projects with VSCode integration.712 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables scaffolding opinionated MCP project templates with previews, secure policy checks, file generation, and post-generation validation over HTTP or stdio transports.-
- AlicenseNot gradedqualityDmaintenanceEnables generating frontend project scaffolding for multiple frameworks (React, Vue, UmiJS, Electron) via natural language commands.45 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to scaffold production-ready MCP servers with typed tools, resources, prompts, transports, authentication, and database integrations.MIT
TDQS
Scored across 5 tools
list_resources, delete_resource, and add_field are clearly distinct, but scaffold_resource already supports previewing or applying a write plan, making preview_scaffold semantically overlapping. Descriptions help clarify intent, but an agent could easily pick the wrong tool for a preview action.
All five tool names follow a verb_noun snake_case pattern: scaffold/list/preview/delete/add + resource/scaffold/field. The only minor variance is singular vs. plural objects (list_resources vs. delete_resource), but no convention mixing occurs.
Five tools is a reasonable scope for managing MERN scaffolds, not bloated. However, preview_scaffold is arguably redundant with scaffold_resource's preview mode, so the set is slightly looser than ideal.
The main lifecycle is covered: scaffold a resource, list resources, add a field, and delete a resource. There is no counterpart to remove or update fields, leaving add_field as a one-way operation and requiring workarounds like delete-and-rescaffold.