wecom-msg-audit-mcp
by deadmau5v
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY | No | 代理地址 | |
| CORP_ID | Yes | 企业 ID（我的企业 → 企业信息） | |
| MCP_HOST | No | HTTP 模式监听地址 | 127.0.0.1 |
| MCP_PORT | No | HTTP 模式监听端口 | 8331 |
| R2_S3_ID | No | R2 S3 兼容 AccessKey ID | |
| R2_TOKEN | No | 兼容字段（当前未使用） | |
| SEQ_FILE | No | seq 进度文件 | ./wecom_msg_seq.txt |
| R2_BUCKET | No | R2 存储桶 | |
| R2_S3_KEY | No | R2 S3 兼容 AccessKey Secret | |
| FETCH_LIMIT | No | 单次拉取条数，1-1000 | 100 |
| R2_ENDPOINT | No | Cloudflare R2 端点 | |
| SDK_TIMEOUT | No | SDK 请求超时（秒） | 30 |
| OUTPUT_JSONL | No | 解密消息输出文件 | ./wecom_messages.jsonl |
| SDK_LIB_PATH | No | SDK 动态库路径 | ./libWeWorkFinanceSdk_C.so |
| MCP_TRANSPORT | No | stdio 或 http | stdio |
| PROXY_PASSWORD | No | 代理密码 | |
| MSGAUDIT_SECRET | Yes | 会话内容存档 Secret（不是普通应用 Secret） | |
| MCP_BEARER_TOKEN | No | HTTP 模式下的 Bearer 鉴权 Token | |
| PRIVATE_KEY_PATH | No | RSA 私钥路径 | ./private_key.pem |
| R2_CUSTOM_DOMAIN | No | 自定义访问域名 | |
| EXTERNAL_CONTACT_SECRET | No | 客户联系可调用应用 Secret（用于外部客户群） |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/deadmau5v/wecom-msg-audit-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server