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 server creation/documentation, while 'hello-world' is for user interaction. 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 lacks a clear verb and is more phrase-like. This mixed convention reduces predictability and readability across the tool set.
With only 2 tools, this server feels too thin for a 'boilerplate' purpose, which typically implies a foundational or example set. The count is insufficient to demonstrate meaningful coverage or utility, making it borderline inadequate for its apparent scope.
For a boilerplate server, there are significant gaps: it lacks core operations like setup, configuration, testing, or deployment tools. The two tools provided do not form a coherent or complete surface for server development, leaving obvious dead ends for agents.