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 between them, making it easy for an agent to select the correct tool.
The naming is inconsistent: get-mcp-docs uses kebab-case with a verb-noun structure, while hello-world uses kebab-case but is a phrase rather than a clear verb-noun pattern. This mixed style reduces predictability and readability.
With only 2 tools, this server feels too thin for a boilerplate purpose, which typically implies a foundational set of utilities. The scope seems limited, lacking coverage for common operations like setup, configuration, or testing that might be expected in a boilerplate.
Inferred domain is MCP server development, but the tool surface is severely incomplete: it includes a documentation tool and a greeting, but misses essential CRUD/lifecycle operations (e.g., initialize, configure, deploy, test). This will likely cause agent failures in practical workflows.