mcp-for-programmer
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| code-explainerC | 帮助新手程序员理解代码，分析技术栈和最佳实践 |
| gen_prd_prototype_htmlA | 基于用户提供的产品概念，自动生成结构完整的产品需求文档(PRD)和高保真交互原型，二者深度融合于一个单页HTML中，适合产品团队评审、路演和开发落地。 |
| typescript-challenge-analyzerC | 我正在刷typescript-challenge，根据我提供的ts代码段，分析这段TypeScript代码中使用的高级类型技术，提供最佳实践和使用场景示例，适合正在学习TypeScript类型系统的开发者 |
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 3 tools
Each tool targets a clearly different task: code explanation, PRD/prototype generation, and TypeScript challenge analysis. There is no overlap or ambiguity between them.
Naming conventions are mixed: 'code-explainer' and 'typescript-challenge-analyzer' use hyphens, while 'gen_prd_prototype_html' uses underscores and an abbreviation, breaking consistency.
With only 3 tools, the server feels minimal. The name 'mcp-for-programmer' suggests broader functionality, but the small set may be acceptable for a niche specialization.
The tools cover only three specific scenarios with no common programmer tasks (e.g., search, lint, refactor). The surface is incomplete for the implied domain.