bridge-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE | No | PATH 上的 bridge 命令，作为 BRIDGE_EXE 的备选。 | |
| BRIDGE_EXE | No | 桥可执行文件路径（dist/bridge），用于多端链。若不设置，多端工具将报错。 | |
| BRIDGE_MCP_CACHE | No | 单端克隆缓存根目录。 | ~/.cache/bridge-mcp-server |
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_templatesB | 单端候选菜单（L1）：离线读注册表过滤，kind/stack/form 可选（子串匹配； 受控值/同义词见 templates://catalog 词表提示）。 |
| get_template_paramsD | 单端参数内省 = 落参与选择地基：clone 底座读 params.json 两区（native/derived/selection）。 |
| generate_singleB | 单端直生成：clone → 读协议 → spec 校验 → copier copy（零注册，target_dir 须为空/不存在）。 |
| list_combosD | 多端菜单（L1/L2 地基）：units/edges + 合并 selection（经桥 list-combos）。 |
| get_combo_paramsC | 多端参数基线（经桥 show-combo）：params（可问）/ internal（勿传）/ derived（只读）/ selection。 |
| generate_multiC | 多端组合生成（shell-out 桥 generate）：combo 须在注册表内，params ⊆ 原生参数集。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate_project_guide | 双路径生成玩法：判定形态 → L1/L2/L3 → 落参 → 生成。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| templates_resource | 单端候选注册表（自持 templates.yaml，薄菜单）。 |
| combos_resource | 多端注册表视图（桥 list-combos 物化，只读）。 |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: list_templates and list_combos separately list single-end and multi-end options; get_template_params and get_combo_params separately introspect parameters; generate_single and generate_multi separately perform generation. The descriptions reinforce the single vs multi distinction, leaving no ambiguity about which tool to call for a given task.
All names use snake_case with a consistent verb-first pattern (list_, get_, generate_) and parallel structure for single vs multi (templates/combos, template_params/combo_params). The only minor deviation is that generate_single and generate_multi use mode adjectives rather than nouns, but the set remains highly predictable.
Six tools cleanly cover the two modalities (single-end and multi-end) with three operations each (list, get params, generate). This is well-scoped and every tool earns its place without redundancy.
The surface covers discovery, parameter introspection, and generation for both single and multi templates, forming a complete lifecycle for the bridge's purpose. Minor gaps exist: no standalone validation or preview tool, and list_combos lacks the filtering options that list_templates provides.