mcp-hello-typescript-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for http transport | 127.0.0.1 |
| PORT | No | Bind port for http transport | 8000 |
| APP_NAME | No | Name reported by server_info | mcp-hello-typescript-server |
| 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Health/status of the server: app name, version, uptime, and supported greeting languages. |
| greetA | Return a friendly greeting in the requested language (default English). language accepts a language name, alternate spelling, or ISO code (english, spanish, french, german, italian, portuguese, japanese, hawaiian). Optional name personalizes the message. Returns {language, greeting, message}. |
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 2 tools
greet and server_info have clearly distinct purposes: one returns a greeting, the other reports server health and supported languages. No overlap or ambiguity exists between them.
The names mix a bare verb (greet) with a noun phrase (server_info), lacking a consistent verb_noun pattern. While both are readable, the convention is not uniform.
Only two tools exist for a hello server, which feels thin even for a minimal purpose. greet could stand alone, making server_info auxiliary rather than essential.
The greeting domain is largely covered: greet handles the core action and server_info exposes supported languages. Minor gaps like customizing greeting templates or batch greetings exist but are not critical.