codex-notify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_NOTIFY_CWD | No | Optional. Default working directory. | |
| CODEX_NOTIFY_REPO | No | Optional. Default repository name. | codex-notify-mcp |
| WECOM_WEBHOOK_URL | Yes | Required. Enterprise WeChat bot webhook URL. | |
| CODEX_NOTIFY_ENV_FILE | No | Optional. Path to .env file. | |
| CODEX_NOTIFY_DEFAULT_TITLE | No | Optional. Default notification title. | Codex 任务完成 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notify_wecomB | Send a Codex task notification to a WeCom group robot webhook. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.