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: one is for creating MCP servers (get-mcp-docs), and the other is for greeting users (hello-world). There is no overlap or ambiguity in their functions, making it easy for an agent to choose the correct tool.
The naming is inconsistent: get-mcp-docs uses kebab-case and a verb-object structure, while hello-world uses kebab-case but is a noun-phrase without a clear verb. This mix of conventions lacks a predictable pattern, though both use kebab-case.
With only 2 tools, the server feels thin and under-scoped for a 'boilerplate' purpose, which typically implies a foundational set of utilities. This minimal count limits functionality and may not adequately cover common boilerplate needs.
For a boilerplate server, there are significant gaps: it lacks tools for configuration, testing, deployment, or other common boilerplate tasks. The two tools provided (documentation and greeting) do not form a complete surface for building or managing MCP servers.