Builder-Proj-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_projectC | Build a new project with specified framework. Supported frameworks: spring-boot, spring, spring-mvc, spring-webflux, react, react-vite, react-cra, vue, vue3, vue-vite, fastapi, fastapi-uvicorn, fastapi-gunicorn, django, django-rest, django-cms, flask, flask-rest, flask-sqlalchemy, vite, vite-vanilla, vite-ts, express, express-ts, express-rest, fastify, fastify-ts, fastify-rest, nestjs, nest, nestjs-rest, nestjs-graphql, next, nextjs, next-app, next-pages, nuxt, nuxt3 |
| list_frameworksA | List all supported frameworks for project creation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: build_project creates a project with a specified framework, while list_frameworks simply lists available frameworks. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: build_project and list_frameworks. The naming is clear and predictable.
With only 2 tools, the server is minimal for its purpose of project scaffolding. While it covers the essential actions (list and build), the tool count feels thin and could benefit from additional tools like delete_project or update_project.
The tool set covers the core workflow: listing available frameworks and building a project. It misses operations like project deletion or configuration, but for a simple scaffolding server, it is reasonably complete.