codex-notify-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@codex-notify-mcp Notify wecom: task 'refactor api', status done, summary 'Completed API refactor'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
codex-notify-mcp
Codex 任务完成后发送企业微信通知。这个项目提供两种入口:
MCP 工具:给 Codex 暴露
notify_wecom,让 Codex 在任务完成前主动发通知。CLI 命令:可以被 hook、脚本或手动命令调用,直接向企业微信 webhook 发消息。
效果截图

Related MCP server: webhook-mcp
配置
不要把企业微信 webhook 写进源码。推荐放进本地 .env:
WECOM_WEBHOOK_URL=https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY_HERE
CODEX_NOTIFY_DEFAULT_TITLE=Codex 任务完成
CODEX_NOTIFY_REPO=codex-notify-mcp.env 已加入 .gitignore。如果不想用 .env,也可以直接设置环境变量:
$env:WECOM_WEBHOOK_URL="https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY_HERE"作为 MCP 接入 Codex
在本仓库目录执行:
codex mcp add wecom-notify --env CODEX_NOTIFY_ENV_FILE="E:\code\github\codex-notify-mcp\.env" -- node E:\code\github\codex-notify-mcp\src\server.mjs之后在 Codex 的长期指令或仓库 AGENTS.md 中加入类似规则:
每次任务完成并准备回复用户前,调用 wecom-notify MCP 的 notify_wecom 工具发送企业微信通知。
通知内容包含任务状态、简短摘要、仓库名和当前路径。手动发送测试
node src\cli.mjs --title "Codex 任务完成" --status done --task "通知测试" --summary "企业微信 webhook 已可用"可用环境变量
WECOM_WEBHOOK_URL:必填,企业微信机器人 webhook 地址。CODEX_NOTIFY_ENV_FILE:可选,指定.env文件路径。CODEX_NOTIFY_DEFAULT_TITLE:可选,默认通知标题。CODEX_NOTIFY_REPO:可选,默认仓库名。CODEX_NOTIFY_CWD:可选,默认工作目录。
MCP 工具参数
工具名:notify_wecom
参数:
title:通知标题。status:任务状态,例如done、failed、needs attention。task:任务名。summary:任务摘要。repo:仓库名。cwd:当前路径。
Available Tools
1 toolnotify_wecomB
Send a Codex task notification to a WeCom group robot webhook.
Inputs: cwd, repo, task, title, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion between tools.
With a single tool, naming is trivially consistent, using a clear verb_noun pattern.
A single tool feels too few for a typical MCP server, even for a narrow notification purpose, as there is no room for additional related operations.
The tool covers the core purpose of sending a notification to WeCom, but lacks features like confirmation, delivery status, or support for other notification channels.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP Server for notify to telegram / weixin2194 PyPI29MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that sends webhook notifications to a configured URL, enabling AI assistants to notify users when long-running tasks complete.29 npm3-
- FlicenseNot gradedqualityDmaintenanceWraps WeChat push capability as MCP tools, allowing users to send WeChat template messages and check health via Claude clients.-
- FlicenseNot gradedqualityBmaintenanceA customizable MCP server with auto-registered tools, enabling push notifications via WxPusher and easy addition of custom tools through a decorator-based framework.-