Zip Hive 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 |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scaffold_from_templateA | Create a complete project from a built-in template. Available templates: react-vite, nextjs-app, node-express, python-fastapi, vanilla-html, monorepo-turborepo. Args:
Returns: A summary of created, skipped, and errored files/folders with the root path. Example:
|
| scaffold_list_templatesA | List all available built-in project templates with their descriptions. Returns: A list of template names and their descriptions. Example:
|
| scaffold_create_projectA | Create a project from a custom structure definition. Pass files and optional folders as JSON. Args:
Returns: A summary of created, skipped, and errored files/folders. Example: scaffold_create_project( project_name="my-api", root_dir="/home/user/projects", files=[ {"path": "src/index.ts", "content": "console.log('hello')"}, {"path": "package.json", "content": "{ "name": "my-api" }"} ], folders=["src/routes", "src/models"] ) |
| scaffold_create_filesA | Add files to an existing project directory. Does not create a new project folder — files are created relative to the given directory. Args:
Returns: A summary of created, skipped, and errored files. Example: scaffold_create_files( target_dir="/home/user/projects/my-app", files=[ {"path": "src/utils/helpers.ts", "content": "export const noop = () => {}"}, {"path": "README.md", "content": "# My App"} ] ) |
| scaffold_create_foldersA | Create empty folder structures within an existing directory. Args:
Returns: A list of created folders. Example: scaffold_create_folders( target_dir="/home/user/projects/my-app", folders=["src/components/ui", "src/hooks", "tests/unit"] ) |
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 5 tools
Tools are mostly distinct: listing templates, creating from a template, creating a custom project, adding folders, and adding files are clearly different operations. However, scaffold_from_template and scaffold_create_project both create a new project, which could cause confusion if an agent isn't careful about template vs. custom structure.
All tools share the scaffold_ prefix, but the verb patterns are inconsistent: list_templates and create_* are verbs, while from_template is not. Three tools use 'create' but with different objects, making the naming somewhat predictable but not uniformly verb_noun.
With 5 tools, the set is well-scoped for a scaffolding server. Each tool covers a distinct function without being redundant or overwhelming, and the count is within the ideal range for a focused utility.
The tool surface covers the core scaffolding lifecycle: list templates, create from template, create custom projects, add folders, and add files. Minor gaps include no template preview or dry-run capability, but the existing operations are sufficient for most scaffolding workflows.