infra-mcp-template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TOKEN | No | Token used by the tools in stdio mode. The echo example reads API_TOKEN in stdio, while the connector reads the token from the sign-in form. | |
| LOG_LEVEL | No | Log level, e.g. `debug` prints stacks. | |
| PUBLIC_URL | No | The public URL of the hosted connector, used in `serve --http` mode. | http://localhost:8080 |
| AUTH_SECRET | No | Secret for the hosted connector in `serve --http` mode, must be 32 characters or more (e.g. `openssl rand -base64 48`). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoB | Return the message back. An example tool of the template. |
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 1 tool
There is only one tool, so there is no risk of confusing it with another tool. Its purpose as a template echo example is clear.
The single tool name 'echo' is simple and readable. However, with only one tool there is no meaningful naming pattern to evaluate.
A single trivial example tool is far too thin for a server named infra-mcp-template. It does not provide a useful infrastructure tool surface.
The surface contains only an echo example and no actual infrastructure operations. There is no CRUD or lifecycle coverage for any relevant domain.