TypeScript MCP Server Boilerplate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greetB | 이름과 언어를 입력하면 인사말을 반환합니다. |
| generate-imageC | 텍스트 프롬프트로 이미지를 생성합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code-review | 코드를 입력하면 코드리뷰 기준에 맞는 리뷰 프롬프트를 반환합니다. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes with no overlap: one generates images from text prompts, while the other returns greetings based on name and language. An agent would never confuse these tools as they operate in entirely different domains.
The naming is mixed but readable: 'generate-image' follows a verb-noun pattern, while 'greet' is just a verb. There's no consistent pattern across both tools, but the names are clear and descriptive enough to understand their functions.
With only 2 tools, this server feels extremely thin for a 'TypeScript MCP Server Boilerplate' which suggests a broader utility scope. The tools provided (image generation and greeting) don't align well with typical boilerplate functionality like code generation or project setup.
For a server labeled as a 'TypeScript MCP Server Boilerplate', there are severe gaps: no tools for generating TypeScript code, setting up projects, configuring MCP servers, or any other boilerplate-related tasks. The existing tools feel like random examples rather than a coherent surface for the stated purpose.