prompts-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Target project root directory | process.cwd() |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_promptsA | 【初始化】扫描目标项目,自动生成原始 prompts 体系(context.md / workflow-log.md / recent-5.md / summary-10.md / todos.md / dev-rules.md / modules/)。已有文件不会覆盖。 |
| bootstrapA | 【一键启动】自动读取传递链(context.md + daily + recent-5 + summary-10 + todos + 模块记录)。智能体启动时第一步调用。 |
| check_requirementsA | 【需求澄清】执行 5 项需求明确标准检查。不明确时生成追问问题,禁止猜测执行。 |
| make_planA | 【生成计划】在需求已澄清(check_requirements 全部 ✅)后,生成可行执行计划,等待用户确认。 |
| log_dialogB | 【记录日志】记录一次对话到传递链(daily + recent-5 + summary-10 + log-state.json)。 |
| log_moduleA | 【模块记录】按模块记录一次修改(目录式)。修改功能前先 read_module,修改后调用此工具。 |
| read_moduleB | 【读取模块记录】修改功能前调用,读取对应模块的历史修改记录。 |
| update_todosB | 【更新待办】更新 todos.md 中的待办事项。 |
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 8 tools
Each tool has a clearly distinct purpose: bootstrap for startup, check_requirements for requirement clarity, init_prompts for initializing prompt files, log_dialog and log_module for different logging scopes, make_plan for planning after requirements, read_module for reading module history, and update_todos for todo updates. No overlap.
All tool names follow a consistent snake_case pattern with imperative verbs (bootstrap, check, init, log, make, read, update). No mixing of styles or ambiguous terms.
With 8 tools, the set is well-scoped for a development workflow assistant. Each tool addresses a specific step in the workflow without being too few or too many.
The tools cover the core workflow: initialization, requirement clarification, logging (dialog and module), planning, and todo management. Missing explicit tools for viewing summaries or resetting, but the existing tools update these automatically, so gaps are minor.