ONES Doc MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONES_COOKIE | No | 浏览器会话里的 Cookie，会话复用模式可选但建议提供 | |
| ONES_ORIGIN | No | 请求使用的 Origin，可选，默认回落到 ONES_BASE_URL | |
| ONES_REFERER | No | 请求使用的 Referer，可选，默认回落到 ${ONES_BASE_URL}/project/ | |
| ONES_BASE_URL | No | ONES 内网根地址 | |
| ONES_PASSWORD | No | 登录密码，账号密码模式必填 | |
| ONES_USERNAME | No | 登录账号，账号密码模式必填 | |
| ONES_AUTH_TOKEN | No | 浏览器会话里的 Bearer token，会话复用模式可选但建议提供 | |
| ONES_TIMEOUT_MS | No | 请求超时，可选，默认 15000 | |
| ONES_USER_AGENT | No | 请求使用的 User-Agent，可选；账号密码模式下未配置时默认使用企微风格 UA | |
| ONES_OCR_API_KEY | No | OCR 服务鉴权 token，可选 | |
| ONES_OCR_ENDPOINT | No | OCR 服务地址，可选 | |
| ONES_OCR_PROVIDER | No | OCR 提供方，可选，当前支持 http | |
| ONES_OCR_TIMEOUT_MS | No | OCR 请求超时，可选，默认 15000 | |
| ONES_MAX_CONTENT_CHARS | No | 正文最大长度，可选，默认 20000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsC | Search ONES docs by keyword |
| get_doc | Get ONES doc by context ref (URL or #requirement) and return markdown content. |
| get_doc_outline | Return section outline and size metadata for a ONES doc ref. |
| get_doc_sectionB | Return one outline section from a ONES doc ref, optionally including descendants. |
| get_doc_chunksA | Return one cursor-based chunk from a ONES doc ref using a character budget. |
| get_doc_contextB | Automatically select sections or chunks for a ONES doc ref based on a question. |
| get_requirement_detail_by_ref | Get requirement body, fields, and related task facts by requirement number, task id, or task URL. |
| get_execution_tasks_by_refB | Get execution-task candidates by requirement number, task id, or task URL. |
| extract_requirement_materials_by_ref | Extract wiki pages, external links, rich resources, and completeness hints by requirement number, task id, or task URL. |
| list_requirement_bugs_by_ref | List bugs under a requirement by requirement number, task id, or task URL when explicitly requested. |
| get_task_messages_by_refB | Get task comments/messages by task number, task id, or task URL. |
| get_related_wiki_pages_by_refA | Discover wiki page references by requirement number, task id, or task URL. |
| get_task_rich_resources_by_refA | Extract rich-text image resources by task number, task id, or task URL. |
| get_bug_detail_by_refA | Get bug body, fields, and related task facts by bug number, task id, or task URL. |
| get_bug_parent_requirement_by_refA | Resolve the parent requirement by bug number, task id, or task URL. |
| resolve_requirementC | Resolve an ONES requirement by number, task id, or task URL. Prefer *_by_ref tools for normal workflow reads. |
| get_requirement_detailA | Get requirement body, fields, and related task facts by task id. Prefer get_requirement_detail_by_ref when starting from a requirement number or URL. |
| get_execution_tasksA | Get execution-task candidates related to a requirement by task id. Prefer get_execution_tasks_by_ref when starting from a requirement number or URL. |
| resolve_bug | Resolve an ONES bug by number, task id, or task URL. Prefer *_by_ref tools for normal workflow reads. |
| get_bug_detailA | Get bug body, fields, and related task facts by task id. Prefer get_bug_detail_by_ref when starting from a bug number or URL. |
| get_bug_parent_requirementA | Resolve the parent requirement for a selected bug by task id. Prefer get_bug_parent_requirement_by_ref when starting from a bug number or URL. |
| list_requirement_bugsA | List bugs under a requirement by task id when explicitly requested. Prefer list_requirement_bugs_by_ref when starting from a requirement number or URL. |
| get_task_messagesA | Get task comments/messages by task id for requirement workflow context. Prefer get_task_messages_by_ref when starting from a number or URL. |
| extract_requirement_materialsA | Extract wiki pages, external links, rich resources, and completeness hints from a requirement task id. Prefer extract_requirement_materials_by_ref when starting from a requirement number or URL. |
| get_related_wiki_pagesA | Discover wiki page references attached to or linked from a requirement task id. Prefer get_related_wiki_pages_by_ref when starting from a requirement number or URL. |
| get_task_rich_resources | Extract rich-text image resources from a requirement, task, or bug body by task id. Prefer get_task_rich_resources_by_ref when starting from a number or URL. |
| download_ones_resourceA | Download an ONES-authenticated image or file resource by URL using the current MCP login session. |
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 20 tools
Many tools come in pairs with and without '_by_ref' suffix, doing essentially the same operation but accepting different parameter types. While descriptions clarify the intended input, the overlap increases risk of misselection for an agent.
Naming follows a consistent verb_noun pattern with underscore, and the '_by_ref' suffix is applied uniformly. However, the presence of both variants for multiple functions creates slight inconsistency.
20 tools is on the high side but still reasonable for a comprehensive documentation and task management server. Could be streamlined by merging the '_by_ref' variants, but the count is not excessive.
Covers search, retrieval of docs, tasks, bugs, requirements, and related resources. Missing write operations and a generic listing function for requirements/bugs, but read coverage is good for the domain.