Mcp Wecombot Server

Created By
gotoolkitsa year ago
An MCP server application that sends various types of messages to the WeCom group robot.
Overview

what is Mcp Wecombot Server?

Mcp Wecombot Server is an MCP server application designed to send various types of messages to the WeCom group robot, facilitating communication within WeCom groups.

how to use Mcp Wecombot Server?

To use Mcp Wecombot Server, you can either install it via Smithery or manually clone the repository and build it. After installation, configure the server with your WeCom bot webhook key and use the provided commands to send messages.

key features of Mcp Wecombot Server?

  • Send text, markdown, image, news, and template card messages to WeCom groups.
  • Upload files to WeCom.
  • Easy installation via Smithery or manual setup.
  • Supports various message formats for enhanced communication.

use cases of Mcp Wecombot Server?

  1. Sending automated notifications to WeCom groups.
  2. Sharing updates and news articles in a group setting.
  3. Facilitating team communication through various message types.

FAQ from Mcp Wecombot Server?

  • How do I install Mcp Wecombot Server?

You can install it via Smithery or manually by cloning the repository and building it.

  • What types of messages can I send?

You can send text, markdown, image, news, and template card messages.

  • Is there a configuration guide for WeCom?

Yes, you can refer to the WeCom group robot configuration guide at https://developer.work.weixin.qq.com/document/path/91770.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gotoolkits
Star
22
Language
Go
License
GPL-3.0 license
Tags

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

6 hours ago
Fomox402

7 hours ago