project-scaffold
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesA | List all available project template combinations and their descriptions. |
| configure_projectA | Returns structured questions for configuring a new project. Call this FIRST when a user wants to create a project. Present the questions to the user, collect their answers, then call create_project with the full configuration. |
| create_projectA | Scaffold a complete new project with API, frontend, database config, Docker setup, and CI/CD pipeline. Returns a summary of created files and next steps. Set use_current_dir=True to scaffold directly into output_dir instead of creating a new subdirectory. |
| add_componentA | Add a new component to an existing scaffolded project. Supports adding API routers, database models with matching schemas, frontend pages, GitHub Action workflows, or Docker services. |
| validate_projectA | Validate that a scaffolded project has all expected files and correct structure. Reports missing files and suggests fixes. |
| get_project_infoA | Read an existing scaffolded project and return its configuration, including project type, frontend type, deployment target, and list of components. |
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 6 tools
Each tool targets a distinct phase or aspect of project scaffolding: configure_project gathers requirements, list_templates shows options, create_project generates the project, add_component extends it, validate_project checks structure, and get_project_info inspects configuration. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: configure_project, list_templates, create_project, add_component, validate_project, get_project_info. This makes the tool set predictable and easy to navigate.
With 6 tools, the server is well-scoped for its purpose. Each tool covers a necessary step in the scaffolding workflow without redundancy or bloat.
The tool set covers the full scaffold lifecycle: template discovery, project configuration, creation, component addition, validation, and inspection. While update/delete operations are missing, they are not expected for a scaffold generator, making the surface complete for its domain.