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/development, while hello-world is for user interaction. There is no overlap in functionality or potential for confusion between these tools.
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. There is no predictable pattern across the tool set.
With only 2 tools, this server feels too minimal for a 'boilerplate' purpose. A boilerplate typically provides foundational operations, but this set lacks basic CRUD or utility functions, making it insufficient for meaningful agent workflows.
For a boilerplate server, there are significant gaps: no create, update, delete, or configuration tools. The tools cover only documentation retrieval and a greeting, missing essential operations needed for building or managing an MCP server.