confluence-wiki-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| fetch_wiki_pageA | 获取指定 Confluence Wiki 页面并返回 Markdown、HTML 或纯文本正文。 |
| search_wikiA | 按关键词检索 Confluence Wiki，返回标题、pageId 和页面 URL。 |
| get_wiki_attachmentsB | 列出指定 Confluence 页面附件，适合查找原型图、截图等文件。 |
| wiki_health_checkA | 返回本地托管认证状态并列出可用工具，不访问网络。 |
| get_wiki_page_contextC | 获取 Wiki 页面证据上下文：正文、标题结构、表格、链接、图片、删除线和不确定关键词信号。不做需求裁决。 |
| get_wiki_commentsC | 获取 Confluence 页面评论列表，返回评论正文、作者、时间和 evidence signals。 |
| get_wiki_referencesC | 获取 Wiki 页面引用的其他页面链接，可选抓取被引用页面的标题和摘要。 |
| get_wiki_assetsC | 列出 Wiki 页面的内嵌图片和附件，返回 URL、媒体类型和文件大小。 |
| download_wiki_assetB | 下载 Wiki 附件或图片到本地目录。仅支持 wiki.imgo.tv 域名。 |
| get_wiki_requirement_bundleB | 聚合获取 Wiki 页面的完整 evidence bundle：上下文、评论、引用、资产和权限问题。不做需求裁决。 |
| wiki_auth_loginA | 打开专属 Chrome Profile 进行交互式 Wiki 登录。 |
| wiki_auth_statusA | 探测并报告托管认证状态，不返回凭据值。 |
| wiki_auth_logoutA | 登出并删除托管 Profile，需要 confirm=true 确认。 |
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
Most tools have distinct purposes (search, fetch, get comments, etc.), but there is minor overlap between `get_wiki_attachments` and `get_wiki_assets`, both listing files, which could cause confusion.
Tools follow a verb_noun pattern (e.g., `fetch_wiki_page`, `search_wiki`), but `wiki_auth_login`, `wiki_auth_logout`, and `wiki_health_check` deviate from the standard prefix, mixing `wiki_` with verbs inconsistently.
With 13 tools, the scope is well-balanced for a Wiki MCP server, covering necessary functions like search, retrieval, authentication, and asset management without being bloated.
The server excels at read and evidence-gathering operations but lacks write capabilities (e.g., create, update, delete pages or attachments), limiting its completeness for full Wiki lifecycle management.