Advertise
MCP.so
Sign In

WeCom Bot MCP Server

@MCP-Mirror

Repository

Basic information

Category

Other

Transports

stdio

Author

MCP-Mirror

About WeCom Bot MCP Server

Mirror of

#wecom#bot#server

WeCom Bot MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

WeCom Bot MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is WeCom Bot MCP Server?

A WeCom (WeChat Work) bot server implemented with the FastMCP framework, enabling message sending through a webhook. It is built for developers who need to send notifications from MCP-compatible AI assistants or applications to WeCom group bots.

How to use WeCom Bot MCP Server?

Install via pip or poetry, set the WECOM_WEBHOOK_URL environment variable to your WeCom bot webhook URL, then run the wecom-bot-mcp-server command. Messages can be sent programmatically using the send_message function, and message history can be retrieved with get_message_history.

Key features of WeCom Bot MCP Server

  • Built on the FastMCP framework for easy MCP integration.
  • Supports sending messages in Markdown format.
  • Asynchronous message sending for non-blocking operation.
  • Tracks message history with a built-in function.
  • Full type hints and comprehensive unit tests.

Use cases of WeCom Bot MCP Server

  • Send automated notifications from AI assistants to WeCom group chats.
  • Integrate with MCP-enabled tools to push alerts or updates to WeCom.
  • Use as a simple bot bridge for delivering messages from scripts to WeCom.
  • Enable AI agents to communicate with team members via WeCom groups.

Frequently asked questions

1

What are the runtime dependencies?

Python >= 3.10, FastMCP >= 0.4.1, and httpx >= 0.24.1 are required.

2

How does authentication work?

Authentication is handled via the webhook URL set in the `WECOM_WEBHOOK_URL` environment variable. The URL itself acts as the token.

3

Where is message data stored and for how long?

Message history is tracked in the server’s memory during its runtime. The messages are sent to WeCom servers via webhook; no persistent local storage is documented.

4

Which transport protocol is used?

The server communicates with WeCom via HTTP webhook calls. The MCP protocol is handled by FastMCP over standard I/O for local MCP clients.

5

Can the server be used with Cline?

Yes. The README provides a detailed configuration example for integrating with Cline’s MCP settings, pointing to the `wecom-bot-mcp-server` command and the required webhook URL environment variable.

Comments

More Other MCP servers

Glasswarp

Glasswarp

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

ICSS

chokcoco

不止于 CSS

20.7K

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

DeepMark

DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.

Maestro

mobile-dev-inc

Painless E2E Automation for Mobile and Web

14.8K
Advertise