wecom-crm-mcp
WeCom (企业微信) 客户联系 / External Contact MCP Server — Python SDK + Model Context Protocol server covering the full customer-contact API surface.
Why
GitHub has plenty of WeCom group-bot webhook MCP servers, but none covers the full 客户联系 API: customer management, tags, group chats, customer moments (朋友圈), mass-send (群发), transfer-on-handover, statistics. This does.
Coverage
11 modules, mapping 1:1 to the official 客户联系 docs:
| Module | MCP tool | What it does |
|---|---|---|
| 客户管理 | wecom_customer |
list / get / batch_get / remark |
| 客户标签 | wecom_tag |
list / create / edit / delete / mark |
| 在职继承 | wecom_transfer_active |
transfer customers/groups between active employees |
| 离职继承 | wecom_transfer_resigned |
reassign resigned employees' customers/groups |
| 客户群 | wecom_group_chat |
list / detail / opengid convert |
| 联系我 / 入群 | wecom_contact_way |
manage 「联系我」 and 「加入群聊」 QR codes |
| 客户朋友圈 | wecom_moment |
publish / cancel / list moments |
| 获客助手 | wecom_acquisition |
acquisition links / quota / stats |
| 消息推送 | wecom_msg_template |
mass-send / welcome / group-welcome |
| 统计管理 | wecom_statistics |
follow / group-chat data |
| 附加功能 | wecom_misc |
media upload / product album / sensitive words |
Plus two helpers: wecom_upload_media and wecom_describe_action.
Install
pip install wecom-crm-mcp
Configure
export WECOM_CORPID=ww...
export WECOM_CORPSECRET=... # the External Contact secret, not app secret
export WECOM_AGENTID=1000001 # optional, needed for mass-send
Claude Desktop / Claude Code ~/.claude.json:
{
"mcpServers": {
"wecom-crm": {
"command": "wecom-crm-mcp",
"env": {
"WECOM_CORPID": "ww...",
"WECOM_CORPSECRET": "..."
}
}
}
}
Example
User: 帮我给所有带 "VIP" 标签的客户发一条朋友圈,内容"春节快乐"
Claude: [calls wecom_tag action=list] [wecom_customer action=batch_get]
[wecom_upload_media] [wecom_moment action=add_moment_task]
License
MIT
Metadata
Release files for wecom-crm-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wecom_crm_mcp-0.1.0.tar.gz | 16.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wecom_crm_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.8 kB
Release files / wecom_crm_mcp-0.1.0.tar.gz
| Download URL | wecom_crm_mcp-0.1.0.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0ed582ebb5769154c0995b31a08f4dddf81648e07b6a6a035d292aa894d6b1e
|
|
BLAKE2b-256 checksum How to use checksums |
63d4f0815091a21d1a805881bc5dbe19113804a6e6f28ca1c8ab8bfd57f715d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / wecom_crm_mcp-0.1.0-py3-none-any.whl
| Download URL | wecom_crm_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9fe6f1b1f8cda93d138480c8dde45ef401ebeb168347b042287ff1b10b31eb1
|
|
BLAKE2b-256 checksum How to use checksums |
06b92dd8e7db3cfbdd15147c7d6f5680e78b030d8ac4f6b773ab4de6381a0f0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for wecom-crm-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.