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 these functions, making tool selection straightforward.
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 action. There is no predictable pattern across the tool set, making it harder to infer functionality from names alone.
With only 2 tools, this server feels thin and under-scoped for a 'boilerplate' purpose, which typically implies a foundational set of utilities. The count is too low to provide meaningful coverage or demonstrate a coherent tool surface for server development.
The server is severely incomplete for a boilerplate MCP server domain. It lacks essential operations like configuration, testing, deployment, or common utilities, leaving obvious gaps that would hinder agent workflows and fail to support typical development tasks.