Skip to main content
Glama
wlor0623

codex-notify-mcp

by wlor0623
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to codex-notify-mcp

No user-submitted related servers found.

    Related Servers

    • TelegramMCP

      StandarterDF
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that sends Telegram notifications with project name and completion status via a single tool notify_task_done, supporting StreamableHTTP and stdio transports.
      1
      -

    • wxpush-mcp

      YanQiu0207
      F
      license
      Not graded
      quality
      D
      maintenance
      Wraps WeChat push capability as MCP tools, allowing users to send WeChat template messages and check health via Claude clients.
      -

    • webhook-mcp

      noobnooc
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that sends webhook notifications to a configured URL, enabling AI assistants to notify users when long-running tasks complete.
      54 npm
      3
      -

    • aitools

      Seaborn101
      F
      license
      Not graded
      quality
      B
      maintenance
      A customizable MCP server with auto-registered tools, enabling push notifications via WxPusher and easy addition of custom tools through a decorator-based framework.
      -

    • wecom-crm-mcp

      andyleimc-source
      A
      license
      C
      quality
      C
      maintenance
      MCP server for WeCom customer contact API, enabling LLMs to manage customers, tags, group chats, moments, and mass-send messages.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no risk of confusion between tools.

    Naming Consistency5/5

    With a single tool, naming is trivially consistent, using a clear verb_noun pattern.

    Tool Count2/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources