MCP Server Boilerplate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind address | 127.0.0.1 |
| PORT | No | HTTP port | 3000 |
| NODE_ENV | No | production emits plain JSON logs | development |
| LOG_LEVEL | No | fatal…trace/silent | info |
| AUTH_TOKENS | No | Comma-separated tokens accepted by the example verifier. | |
| AUTH_ENABLED | No | Require a bearer token on /mcp (HTTP transport). | false |
| CORS_ORIGINS | No | Comma-separated CORS origins for browser clients. Empty disables CORS. | |
| ALLOWED_HOSTS | No | Allowed Host hostnames (port-agnostic). Empty disables protection. | 127.0.0.1,localhost |
| MCP_TRANSPORT | No | stdio or http (CLI --transport wins) | stdio |
| AUTH_REQUIRED_SCOPES | No | Comma-separated scopes every token must carry. | |
| AUTH_RESOURCE_METADATA_URL | No | Protected Resource Metadata URL advertised in 401 responses. |
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
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo a message back to the caller, optionally upper-cased. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize | Build a prompt asking the model to summarize the provided text. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info | Name, version and runtime information for this MCP server. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool named 'echo', naming is consistent by default; it follows a simple verb pattern.
A single trivial 'echo' tool is an extreme mismatch for a server implied to be a boilerplate; it provides minimal functionality.
For the simple task of echoing messages, the tool is sufficient, but the server lacks any additional features that might be expected from a functional MCP server.