MCP Server Template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTEL_ENABLED | No | Enable OpenTelemetry tracing | false |
| MCP_SERVER_HOST | No | HTTP host (when transport=http) | 127.0.0.1 |
| MCP_SERVER_NAME | No | Server name | mcp-server-template |
| MCP_SERVER_PORT | No | HTTP port (when transport=http) | 3000 |
| MCP_SERVER_DEBUG | No | Debug mode (skips auth) | false |
| MCP_SERVER_DB_PATH | No | SQLite database path | .data/cache.db |
| MCP_SERVER_TIMEOUT | No | Request timeout (ms) | 30000 |
| MCP_SERVER_VERSION | No | Server version | 0.1.0 |
| MCP_SERVER_CACHE_TTL | No | Default cache TTL (seconds) | 3600 |
| MCP_SERVER_LOG_LEVEL | No | Log level: debug, info, warning, error | info |
| MCP_SERVER_TRANSPORT | No | Transport: stdio or http | stdio |
| MCP_SERVER_SENTRY_DSN | No | Sentry DSN for error tracking | |
| MCP_SERVER_CACHE_ENABLED | No | Enable/disable caching | true |
| OTEL_EXPORTER_OTLP_ENDPOINT | No | OTLP collector endpoint |
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 |
|---|---|
| echoC | Echo a message back, optionally in uppercase |
| addA | Add two numbers together |
| cacheB | Get or set a cached value. Provide only key to get, provide key and value to set. |
| statusB | Get server status and cache statistics |
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 4 tools
Each tool has a clearly distinct purpose: add performs arithmetic, cache handles key-value storage, echo returns input with optional transformation, and status provides server metadata. There is no overlap or ambiguity between these functions.
All tool names follow a consistent, simple verb-based pattern (add, cache, echo, status) without mixing conventions like snake_case or camelCase. This uniformity makes the set predictable and easy to understand.
With 4 tools, the count is reasonable for a template server, covering basic utilities like arithmetic, caching, echoing, and status checks. It's slightly minimal but well-scoped for demonstration purposes, lacking only minor expansions.
As a template server, it covers fundamental operations but has notable gaps for a more robust utility set, such as missing tools for deletion, advanced caching operations, or error handling. However, it provides a complete basic workflow for its intended scope.