WeCom Bot MCP Server

MCPOpen SourceMIT54.4

by loonghao • Messaging & Collaboration

An MCP server implementation for managing WeCom bot interactions.

Example Use Cases

1
Send and manage different types of messages via WeCom bots
2
Track and log WeCom bot message history
3
Integrate WeCom messaging capabilities into AI applications

Description

The WeCom Bot MCP Server is a Model Context Protocol compliant server designed to facilitate automated interaction with WeCom bots. It supports multiple message types, user mention capabilities, and maintains a message history. This server is ideal for integrating WeCom messaging features into AI-driven applications, providing full type annotations and utilizing Pydantic for data validation.

Capabilities(10 total)

Tools (6)

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

file_path:string*bot_id:any

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

image_path:string*bot_id:any

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

content:string*msg_type:stringmentioned_list:arraymentioned_mobile_list:arraybot_id:any

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.

template_card_source:object*template_card_main_title:object*template_card_card_action:object*template_card_emphasis_content:anytemplate_card_quote_area:anytemplate_card_sub_title_text:anytemplate_card_horizontal_content_list:anytemplate_card_jump_list:anybot_id:any

send_wecom_template_card_news_notice

MCP tool wrapper for sending a news_notice template card.

template_card_source:object*template_card_main_title:object*template_card_card_action:object*template_card_image:anytemplate_card_image_text_area:anytemplate_card_quote_area:anytemplate_card_vertical_content_list:anytemplate_card_horizontal_content_list:anytemplate_card_jump_list:anybot_id:any

Prompts (1)

wecom_message_guidelines

High-level guidelines for planning WeCom messages. This prompt explains how to choose between `markdown` and `markdown_v2` message types, when to call the image/file tools, and how to use multiple bots.

Resources (3)

get_message_history_resource

Resource endpoint to access message history. Returns: str: Formatted message history

URI: history://messagesMIME: text/plain

get_multi_bot_instructions_resource

Resource endpoint providing multi-bot usage instructions. Returns: str: Instructions for using multiple bots

URI: wecom://multi-bot-instructionsMIME: text/plain

get_markdown_capabilities_resource

Resource endpoint describing WeCom markdown capabilities. This can be used by MCP clients or models to decide which message type to use based on the desired formatting (tables, images, colors, mentions, etc.).

URI: wecom://markdown-capabilitiesMIME: text/plain

Quick Actions

View on GitHub

Security

Scanned 2 month(s) ago

Risk Level

MODERATE

Can modify files, state, or send data externally

Trust Score

C55/100

5/17 checks passed

Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.

Quick Stats

Service TypeMCP

Pricing ModelFree

Capabilities6 Tools / 1 Prompts / 3 Resources

Ownerloonghao

CategoryMessaging & Collaboration

DependenciesStandalone

Set Your Username