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 or ambiguity between them, making it easy for an agent to select the correct tool based on the task.
The naming is inconsistent: 'get-mcp-docs' uses kebab-case with a verb-object structure, while 'hello-world' uses kebab-case but is a phrase rather than a clear action. There is no predictable pattern across the tools, making the set chaotic and hard to interpret systematically.
With only 2 tools, this server feels thin for a 'boilerplate' purpose, which typically implies a foundational or example set. The count is too low to adequately cover even basic MCP server operations, suggesting an incomplete or minimal implementation.
The server is severely incomplete for a boilerplate domain: it lacks essential tools for MCP server development (e.g., configuration, testing, deployment) and only includes a trivial 'hello-world' tool. There are significant gaps that would prevent agents from performing meaningful tasks.