Skip to main content
Glama
Trigv

@trigv/mcp

by Trigv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @trigv/mcp

No user-submitted related servers found.

    Related Servers

    • mcp-notify

      box7e7
      A
      license
      A
      quality
      C
      maintenance
      Sends push notifications from AI assistants to your mobile device. Supports Claude, Cursor, Windsurf, and more.
      8
      9 npm
      1
      MIT

    • Claude Code Notification Hooks

      nkyy
      A
      license
      A
      quality
      D
      maintenance
      Provides automatic desktop notifications and contextual sounds for Claude Code operations across macOS, Windows, and Linux. It enhances the development experience by intelligently mapping specific event types to native system alerts and sounds.
      4
      9 npm
      3
      MIT

    • Telegram Notify MCP Server

      NobufumiMurata
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects VS Code Copilot to Telegram for mobile notifications, interactive approval workflows, and remote command input. Enables users to monitor AI agents, approve sensitive operations, and provide follow-up instructions from their smartphone.
      MIT

    • SuprSend MCP Server

      suprsend
      A
      license
      A
      quality
      C
      maintenance
      Manage your entire notification infrastructure using natural language. Trigger workflows, create users, manage preferences, update tenant branding, and access docs — all from Cursor, Claude Desktop, or Windsurf. 24 tools covering email, SMS, push, WhatsApp, Slack, MS Teams, and in-app notifications.
      22
      12
      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

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no ambiguity. The single tool has a clear, distinct purpose.

    Naming Consistency5/5

    With only one tool, naming consistency is perfect as there are no other tools to conflict with. The name 'send_event' follows a clear verb_noun pattern.

    Tool Count3/5

    A single tool is borderline; while it may be sufficient for a very narrow purpose, it feels thin compared to the typical 3-15 tools for a well-scoped server.

    Completeness2/5

    The server only provides a send operation, missing other expected capabilities like event listing, deletion, or configuration, which limits its usefulness for agents.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources