WeCom Mail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORPID | No | Your enterprise ID, alias for WECOM_CORP_ID. | |
| CORPSECRET | No | Your application secret, alias for WECOM_CORP_SECRET. | |
| WECOM_CORP_ID | No | Your enterprise ID (WeCom Corp ID), alias for CORPID. | |
| WECOM_API_BASE | No | Base URL for WeCom API. | https://qyapi.weixin.qq.com |
| WECOM_MCP_HOST | No | Host for HTTP transport. | 127.0.0.1 |
| WECOM_MCP_PORT | No | Port for HTTP transport. | 8000 |
| WECOM_LOG_LEVEL | No | Logging level. | INFO |
| WECOM_CORP_SECRET | No | Your application secret (WeCom Corp Secret), alias for CORPSECRET. | |
| WECOM_MCP_TRANSPORT | No | MCP transport type. | stdio |
| WECOM_REQUEST_TIMEOUT | No | Request timeout in seconds. | 20 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailB | 通过企业微信官方邮件 API 发送普通邮件。发件人固定为当前应用邮箱账号。如果发送 HTML 邮件，请显式传 content_type=html，并只使用邮件兼容写法：优先用 table/tbody/tr/td 做布局，样式尽量写 inline style。稳定标签：table、tbody、tr、td、p、br、span、strong、b、em、i、h1-h4、a、img。避免 script、iframe、form、video、audio、canvas、svg、外链 CSS、flex、grid、position、web font、相对路径和网页式复杂模板。图片请使用公网 https 绝对地址。 |
| get_mailbox_infoA | 查询当前应用邮箱账号与别名邮箱，用于确认实际发件人地址。 |
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 2 tools
The two tools have clearly distinct purposes: one sends email, the other retrieves mailbox information. There is no overlap or ambiguity that could lead to misselection.
Both names use a verb_noun pattern (send_email, get_mailbox_info), which is consistent and predictable. Minor deviation in specificity but acceptable.
With only 2 tools, the set feels thin for an email MCP server. Common operations like listing, reading, or managing emails are absent, making the count borderline inadequate.
The server only supports sending email and checking mailbox info. Critical lifecycle operations such as reading, replying, forwarding, or managing folders are missing, significantly limiting its usefulness for email workflows.