MCP Server Boilerplate
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello-worldB | Say hello to the user |
| get-mcp-docsD | Make an MCP server |
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: 'get-mcp-docs' is for creating MCP servers, while 'hello-world' is for greeting users. There is no overlap or ambiguity between these functions, making tool selection straightforward.
The naming is inconsistent: 'get-mcp-docs' uses kebab-case with a verb-object structure, while 'hello-world' uses kebab-case but is a noun-phrase without a clear verb. This mixed convention lacks a predictable pattern, though both use kebab-case.
With only 2 tools, the server feels under-scoped for a 'boilerplate' purpose, which typically implies a foundational set of utilities. This minimal count may not provide sufficient coverage for common MCP development tasks, making it too thin for its apparent scope.
Given the server name 'MCP Server Boilerplate', there are significant gaps in coverage for typical boilerplate functions, such as setup, configuration, testing, or deployment tools. The two tools provided (documentation and greeting) do not form a complete surface for MCP server development, leading to potential agent failures in broader tasks.