Production MCP Template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TEMPLATE_AUTH_MODE | No | Authentication mode (none / static-bearer / jwt) | |
| MCP_TEMPLATE_JWT_JWKS_URL | No | The URL for JWT JWKS verification | |
| MCP_TEMPLATE_JSON_RESPONSE | No | Whether to return JSON responses for Streamable HTTP | |
| MCP_TEMPLATE_STATELESS_HTTP | No | Whether to enable stateless HTTP mode | |
| MCP_TEMPLATE_AUTH_ISSUER_URL | No | The URL of the authentication issuer | |
| MCP_TEMPLATE_ENABLED_MODULES | No | List of capability modules to enable | |
| MCP_TEMPLATE_EVENT_STORE_PATH | No | The file path for the SQLite event store database | |
| MCP_TEMPLATE_DEFAULT_TRANSPORT | No | Default transport protocol to use (stdio / sse / streamable-http) | |
| MCP_TEMPLATE_EVENT_STORE_BACKEND | No | The backend for event storage (none / sqlite) | |
| MCP_TEMPLATE_AUTH_RESOURCE_SERVER_URL | No | The URL of the resource server |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_health_checkA | Return current server health, transport mode, and module state. |
| system_echoA | Echo structured payloads with request metadata for client integration tests. |
| system_capability_catalogA | List all registered modules and the capability surface each one exposes. |
| workspace_inventoryB | Inspect the configured workspace root and return a bounded inventory summary. |
| workspace_read_textB | Read a UTF-8 text file under the workspace root with traversal protection. |
| jobs_submit_blueprintC | Submit a demo background job that models long-running orchestration work. |
| jobs_get_statusA | Fetch a specific background job status. |
| jobs_listB | List recent background jobs with current status and results. |
| design_collect_feature_briefA | Collect missing design inputs, optionally using MCP elicitation, and return a normalized brief. |
| design_tool_contractC | Generate a design-time contract preview for a future MCP tool. |
| design_refine_with_samplingC | Use host sampling when available to draft a richer rollout or feature brief. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| system_triage_incident | |
| workspace_plan_integration | |
| jobs_postmortem | |
| design_rollout_plan |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_build_info | |
| server_health | |
| server_instructions | |
| workspace_inventory_resource | |
| production_readiness |
TDQS
Scored across 11 tools
All tools have clearly distinct purposes grouped by domain: design, jobs, system, and workspace. No overlap in functionality.
All tools follow a consistent domain_action snake_case pattern (e.g., design_collect_feature_brief, jobs_get_status).
11 tools is well-scoped for a template covering design, jobs, system, and workspace with no redundancy.
Covers core workflows for each domain but lacks write operations for workspace and update/delete for jobs; acceptable for a template.