workflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKFLOW_TEMPLATES_HOME | No | Path to the workflow-templates repository. Defaults to E:\NEMB\workflow-templates. | E:\NEMB\workflow-templates |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesA | 列出 workflow-templates 仓库中所有可用的工作流模板（含版本、描述、是否可执行）。 |
| get_template_infoC | 查看模板的契约：输入/输出 JSON Schema、处理流水线（DAG）概要。 |
| run_templateA | 执行指定工作流模板。input_json 为符合该模板输入契约的 JSON 字符串（如财报分析模板需 company_name / report_path / report_type）。 返回：success、data（结构化输出，含 human_review_required 标记）、report（报告文本）、artifacts（落盘路径）。 注意：自动化执行会标记 review_note，请调用方核验关键数字。 长耗时模板（如含多次 LLM 调用）在带请求超时限制的客户端下请改用 run_template_async。 |
| run_template_asyncA | 异步执行指定模板：立即返回 task_id，执行在后台进行，用 get_task_status 轮询结果。 适用场景：WorkBuddy / Claude Desktop 等客户端对单次工具调用有请求超时限制， 而模板真实执行（多次 LLM 调用）可能超过该限制。 |
| get_task_statusA | 查询异步任务状态：running / done / error；done 时返回完整结果（同 run_template 返回结构）。 |
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 5 tools
Each tool targets a distinct operation: list_templates (enumerate), get_template_info (inspect contract), run_template (sync execute), run_template_async (async execute), get_task_status (poll). The sync/async pair is clearly differentiated by explicit timeout guidance in the descriptions, so no realistic misselection.
All names follow a clean verb_noun snake_case pattern (list/get/run/get). Minor inconsistency: list_templates uses a plural noun while get_template_info uses singular, and 'info'/'status' suffixes differ slightly, but this is readable and predictable.
Five tools is well-scoped for a template-consumer/executor server, with each tool earning its place (discovery, inspection, sync exec, async exec, polling). No redundant or filler tools.
Covers the full discover-inspect-execute-monitor lifecycle, including an async path for long-running templates. Minor gap: no cancel/abort operation for a running async task, which could strand agents waiting on a hung task.