boilerforge
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 |
|---|---|
| list_boilerplatesA | List all available boilerplates in the registry |
| get_boilerplateB | Get all files for a specific boilerplate |
| search_boilerplatesA | Search boilerplates by name, stack, or tags |
| scaffold_projectB | Scaffold a boilerplate into a target directory |
| check_project_updatesA | Check whether a scaffolded project has boilerplate updates available |
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
Each tool targets a distinct operation: listing all, getting files, searching, scaffolding, and checking updates. The descriptions make it easy to distinguish list from search and get from scaffold, eliminating ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (list_, get_, search_, scaffold_, check_), making the API predictable and easy to navigate.
With 5 tools, the server is well-scoped and each tool serves a clear purpose in the boilerplate workflow, avoiding bloat while providing essential functionality.
The set covers the main consumer workflow: discover, retrieve, scaffold, and check updates. Missing create/update/delete for boilerplates themselves, but that appears outside the server's intended read-only registry scope.