template-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (only for http transport) | 3000 |
| NODE_ENV | No | Environment (development, production, etc.) | development |
| LOG_LEVEL | No | Pino log level | info |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'http' | stdio |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetA | Generates a personalized greeting message. Use this tool when you need to greet someone by name with an optional custom greeting style. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize | Creates a prompt that asks the model to summarize the given text in a specific style and length. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info | Returns metadata about this MCP server |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity in choosing between tools.
With only one tool, consistency is not applicable, but the name 'greet' is clear and follows a common verb pattern.
A single tool for a server called 'template-mcp' suggests an extremely narrow scope, which is likely insufficient for meaningful tasks.
The server only offers a greeting function, which is too limited for any substantial workflow; missing any broader functionality.