WeCom

**Quick judgement**: A focused, practical MCP skill for sending text and markdown messages into WeCom via webhook. It’s well-suited for notifications, status reports, and basic ChatOps-style integrations from Claude Code and other MCP clients. **Strengths & advantages** - Clean, minimal surface: two tools (`send_wecom_message`, `send_wecom_markdown`) that map directly to common WeCom usage. - Good for automation: easy to wire into workflows for alerts, CI/CD notifications, or scheduled reports. - WeCom-flavored markdown support enables rich message formatting (mentions, links, images, colors). - Environment-based configuration (webhook URL and timeout) aligns with typical deployment practices. **Risks & limitations** - Outbound-only: this is a one-way push to WeCom; you can’t read messages or build interactive flows. - Misconfiguration risk: incorrect or leaked `WECOM_WEBHOOK_URL` could send messages to the wrong channel or expose a spam vector if someone else gets the URL. - Reliability is dependent on WeCom’s webhook availability and network stability; documentation doesn’t mention retries, backoff, or structured error handling. - WeCom-specific markdown quirks may require some trial-and-error to get formatting exactly right. **Recommended scenarios** - Teams already using WeCom who want their MCP-based assistants or tools to post notifications into existing group chats. - Engineering or ops teams needing quick integration for deployment/alerting messages into WeCom. - Product or project teams wanting automated daily/weekly reports in a WeCom channel, formatted via markdown. - Any MCP setup where the main requirement is **simple, reliable outbound messaging** to WeCom rather than full bi-directional bot behavior.