Skip to main content
Glama
kevinwatt

MCP Webhook Server

by kevinwatt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP Webhook Server

No user-submitted related servers found.

    Related Servers

    • whatsapp-mcp

      OmarYousef95
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending WhatsApp messages from MCP clients using a personal WhatsApp account via WebSocket protocol, without needing the Business API or browser automation.
      35 npm
      MIT

    • MCP Webhook Server

      siendomiguel
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables sending data to webhooks via HTTP POST for both local and remote team environments. It provides a tool for relaying task descriptions, custom metadata, and automated notifications to external services.
      4 npm
      -

    • discord-mcp

      yone-k
      A
      license
      B
      quality
      D
      maintenance
      Enables MCP clients to interact with Discord servers, allowing operations such as sending messages and reading message history through the Discord API.
      23
      116 npm
      MIT

    • notify_me_mcp

      thesammykins
      A
      license
      B
      quality
      D
      maintenance
      Enables sending rich notifications to Discord and/or Slack webhooks with automatic service detection, retry logic, and support for embeds, blocks, and attachments. Provides secure webhook management with comprehensive input validation and rate limiting.
      3
      TypeScript
      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

    C2.9/5.0

    Scored across 2 tools

    Disambiguation3/5

    Both tools send data to a webhook endpoint, but 'send_json' is specific to JSON objects while 'send_message' is for general messages. Some overlap exists as JSON could be sent via 'send_message', but descriptions help differentiate.

    Naming Consistency5/5

    Both tools follow a clear verb_noun pattern ('send_json', 'send_message'), making the naming consistent and predictable.

    Tool Count2/5

    With only 2 tools, the server feels too minimal for typical webhook interactions. Even basic functionality like managing endpoints or checking delivery status is missing, suggesting the scope is too narrow.

    Completeness2/5

    The tool surface is severely incomplete for a webhook server. There are no tools for configuration, validation, or testing of webhooks, which are essential for real-world use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources