wecom-docs-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_EXE | No | Node.js executable name (node on Linux/macOS) | node.exe |
| WECOM_CLI_PATH | No | Full path to wecom.js (override if auto-detect fails) | auto-detected |
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 |
|---|---|
| wecom_read_docA | Read a WeCom document or smartsheet. Returns content as Markdown. Auto-detects URL type: /smartsheet/ URLs return table data, /doc/ URLs return document content. |
| wecom_create_docA | Create a new WeCom document or smartsheet. Returns url and docid — save the docid for subsequent edits. |
| wecom_edit_docB | Write Markdown content to a WeCom document. Supports headings, lists, tables, bold, italic. Use docid (preferred) or url to identify the document. |
| wecom_smartsheet_setup_fieldsA | Initialize a smartsheet's column schema. Renames the default field and adds remaining fields. Must be called before adding records to a new sheet. |
| wecom_smartsheet_add_recordsA | Append rows to a smartsheet. Each record is a plain {column_name: value} dict — cell format conversion is handled automatically. |
| wecom_smartsheet_get_sheetA | List all sheets (sub-tables) in a WeCom smartsheet. Returns sheet IDs and titles. |
| wecom_smartsheet_get_fieldsA | Get column definitions (field names, types, IDs) for a smartsheet sheet. |
| wecom_smartsheet_get_recordsC | Fetch all rows from a smartsheet sheet. Returns structured row data. |
| wecom_get_doc_contentA | Fetch the full content of a WeCom online doc as Markdown. Uses async polling internally. |
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 9 tools
Tools are mostly distinct: docs (create, edit, get, read) vs smartsheets (add_records, get_fields, get_records, get_sheet, setup_fields). However, wecom_get_doc_content and wecom_read_doc overlap in purpose (both fetch content), though read auto-detects smartsheets, creating slight ambiguity.
All tools follow wecom_verb_noun pattern, but verbs vary (create, edit, get, read, add, setup). Consistent snake_case and prefix, but 'get' vs 'read' for similar operations is a minor inconsistency.
With 9 tools covering document and smartsheet operations, the count is well-scoped. Each tool serves a clear purpose without redundancy, appropriate for the domain.
Covers core CRUD for docs (create, edit, read) and smartsheets (schema, records, sheets). Missing delete/update for smartsheets or document deletion, but essential workflows are complete, so minor gaps.