servers / wecom-bot-mcp-server

wecom-bot-mcp-server

communitystdiolocalwrite capablehealthy

A Python server implementation for WeCom (WeChat Work) bot that follows the Model Context Protocol (MCP). This server provides a standardized interface for handling automated messaging and context-aware interactions within enterprise WeChat environments.


01Tools · 6

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
send_message
Send message to WeCom with optional @mentions. MENTION USERS: When users want to notify/remind/cc someone, convert their intent to <@userid> syntax: - "remind Zhang San" → Add <@zhangsan> in content, use msg_type='markdown' - "notify @alice and @bob" → Add <@alice> <@bob> in content, use msg_type='markdown' - "let everyone know" → Add <@all> in content, use msg_type='markdown' User ID conventions: - Chinese names → pinyin: "张三" → "zhangsan", "李四" → "lisi" - English names → lowercase: "Alice" → "alice" - Explicit usernames → preserve: "@zhangwei" → "zhangwei" Args: content: Message content. Include <@userid> for mentions in markdown mode. Examples: "Hi <@zhangsan>, please review!" or "<@all> Team meeting at 3 PM" msg_type: Message type. Use 'markdown' for @mentions, 'markdown_v2' for general content. mentioned_list: User IDs to mention (only for text messages). mentioned_mobile_list: Mobile numbers to mention (only for text messages). bot_id: Bot identifier for multi-bot setups. If None, uses the default bot. Returns: dict: Response with status and message Raises: WeComError: If sending message fails
writetrueunknown
send_wecom_file
Send file to WeCom. Args: file_path: Path to the file to send bot_id: Bot identifier for multi-bot setups. If None, uses the default bot. Returns: dict: Response with file information and status Raises: WeComError: If file sending fails
writetrueunknown
send_wecom_template_card_news_notice
MCP tool wrapper for sending a news_notice template card.
writetrueunknown
send_wecom_image
Send image to WeCom. Args: image_path: Path to the image file to send bot_id: Bot identifier for multi-bot setups. If None, uses the default bot. Returns: dict: Response with image information and status Raises: WeComError: If image sending fails
writetrueunknown
send_wecom_template_card_text_notice
MCP tool wrapper for sending a text_notice template card. The structure of the template card fields follows the WeCom template_card documentation and notify-bridge examples.
writetrueunknown
list_wecom_bots
List all configured WeCom bots. Use this tool to discover available bots before sending messages. Each bot has an id, name, and optional description. Returns: dict: Contains 'bots' list and 'count' of available bots. Each bot entry has: id, name, description, has_webhook
readfalseunknown

02Install & source
uvx wecom-bot-mcp-server
uvx

03Access granted
Send chat messages · write

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesGitHub repo search [p4]
last_checked2026-07-14 08:17Z
next_check2026-07-15 12:55Z
cadenceevery 29h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex9 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. wecom-bot-mcp-server MCP — as seen on mcpexplorer.com

[![wecom-bot-mcp-server MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/wecom-bot-mcp-server.svg)](https://mcpexplorer.com/servers/wecom-bot-mcp-server)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →
wecom-bot-mcp-server — MCPExplorer