bwiki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BWIKI_BASE_URL | No | BWIKI 基础 URL | https://wiki.biligame.com/gc |
| BWIKI_HEADLESS | No | 无头模式 | false |
| BWIKI_USER_DATA_DIR | No | 浏览器用户数据目录（持久化登录） |
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 |
|---|---|
| bwiki_navigateA | 导航到BWIKI页面。可以指定完整URL或页面名称。 |
| bwiki_edit_pageB | 编辑BWIKI页面内容。自动处理CodeMirror编辑器，支持追加模式。 |
| bwiki_add_categoryA | 为BWIKI页面添加分类标记。智能插入到正确位置，避免重复。 |
| bwiki_get_contentA | 获取BWIKI页面的Wiki源码内容。 |
| bwiki_get_categoriesA | 获取BWIKI页面已有的分类列表。 |
| bwiki_get_file_infoA | 获取BWIKI文件信息，包括URL、描述和分类。 |
| bwiki_clickC | 在BWIKI页面上点击元素。 |
| bwiki_evaluateA | 在BWIKI页面上执行JavaScript代码。用于高级操作如直接操作CodeMirror。 |
| bwiki_screenshotC | 截取BWIKI页面截图。 |
| bwiki_snapshotA | 获取BWIKI页面的HTML快照，用于元素定位。 |
| bwiki_get_urlA | 获取当前页面URL。 |
| bwiki_wait_for_selectorB | 等待特定元素出现在页面上。 |
| bwiki_typeC | 在输入框中输入文本。 |
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 13 tools
Each tool has a clear, distinct purpose: navigation, content retrieval/editing, category management, file info, and browser interaction primitives. The only potentially confusing pair is snapshot vs. screenshot, but the descriptions clearly distinguish HTML source from image capture.
All tools share the 'bwiki_' prefix and follow a verb-based naming pattern. Getter functions use 'get_<noun>', while actions are single verbs like 'click', 'type', 'evaluate', 'navigate'. This makes tool names predictable and easy to remember.
13 tools is well-scoped for a wiki automation server, covering content operations, category management, file lookup, and page interaction. It is neither too sparse nor overloaded, with each tool earning its place.
The surface covers the core wiki editing workflow: navigate, read, edit, add categories, and get file info. Browser automation tools (click, type, evaluate, wait, screenshot) enable advanced interactions. Missing page creation/deletion may be a minor gap, but edit_page likely handles page creation and the absence of delete is not critical for typical wiki editing.