mcp-hello-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for http/sse transport | 127.0.0.1 |
| PORT | No | Bind port for http/sse transport | 8000 |
| APP_NAME | No | Name reported by server_info | mcp-hello-server |
| MCP_TRANSPORT | No | Transport mode: stdio, http, or sse | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
A minimal demo MCP server. Use server_info for a health/status check, and greet to get a friendly greeting in a given language (english, spanish, french, german, italian, portuguese, japanese, or hawaiian; defaults to english). For example, 'greet in French' returns 'Bonjour!'.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoB | Health/status of the server. |
| greetA | Return a friendly greeting in the requested language (default English).
|
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
server_info and greet have clearly distinct purposes: one reports server status, the other returns personalized greetings. There is no overlap or ambiguity between them.
The two tool names are clear and readable, though one uses a noun-based name (server_info) and the other uses a verb-based name (greet). The mild inconsistency is not confusing at this scale.
Two tools is minimal but well-suited to a simple hello server. While it borders on thin, each tool serves an obvious purpose and the scope is intentionally narrow.
The tool set fully covers the apparent domain of a hello server: checking server health and returning greetings. It supports language selection, personalization, and multiple languages, leaving no obvious dead ends.