expert-router
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| braveExe | Yes | Absolute path to the Brave executable on this machine. | |
| debugPort | Yes | CDP debug port used to talk to the dedicated Brave instance (default 9333). | 9333 |
| bridgeBinary | Yes | Absolute path to the ai-browser-bridge dist/bridge.js that the router spawns. | |
| routerBinary | Yes | Absolute path to this repository's dist/index.js (the MCP server entry point). |
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 |
|---|---|
| expert_consultA | 本地调查之后，把难题交给 ChatGPT 极高档。仅在本仓库已开通时可用（标记文件 .claude/expert-consult.json）。reason 必须是闭集之一。已有咨询在进行时不要重试。briefing 用英文填写，源码保持原样。 |
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 1 tool
With only a single tool, there is no possibility of confusion or ambiguous overlap between tools. The purpose of expert_consult is clearly distinct by virtue of being the only operation exposed.
The single tool name 'expert_consult' follows a clean verb_noun convention. With no other tools to compare against, naming consistency is trivially maintained.
One tool feels thin for a server named 'expert-router', which implies a broader routing or expert-selection purpose. However, the tool is domain-specific and non-trivial, so it falls in the borderline range rather than being an extreme mismatch.
The server exposes only a single consult action with no way to inspect active consultations, list available experts, or manage the feature flag. The description references state ('已有咨询在进行时不要重试') and an enumeration ('reason 必须是闭集之一') but provides no supporting tools, leaving significant workflow gaps.