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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
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/development, while 'hello-world' is for user interaction/greeting. There is no overlap or ambiguity in their functions.
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 action verb. This mixing of conventions reduces predictability.
With only 2 tools, this server feels too thin for a 'boilerplate' purpose, which typically implies foundational or example functionality. The count is insufficient to demonstrate meaningful coverage or utility.
For a boilerplate server, there are significant gaps: no tools for configuration, testing, deployment, or common MCP operations like listing resources. The surface is severely incomplete for development or example use cases.