Skip to main content
Glama
Lakphy

Dot MCP

by Lakphy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Dot MCP

No user-submitted related servers found.

    Related Servers

    • kweenkl MCP Server

      antoinedelorme
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send push notifications through the kweenkl service. Allows users to receive contextual notifications from their AI when tasks are complete or important events occur.
      1
      7 npm
      MIT

    • BotBell MCP Server

      qq418716640
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.
      2
      10 npm
      1
      MIT

    • Notifications MCP Server

      ohqay
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to send native macOS notifications for task completion alerts and reminders. Supports interactive features like custom system sounds, action buttons, and user replies directly from the notification center.
      201 npm
      MIT

    • MCPing

      toolprint
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send desktop notifications on macOS with rich formatting, urgency levels, and sound options.
      1
      15 npm
      1
      MIT

    • mcp-win-toast

      ShigeruWakida
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send Windows toast notifications and dialog boxes, allowing them to actively notify users and request confirmations through native Windows UI.
      2
      1
      ISC
    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

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'send_text' has a clear and distinct purpose of sending text to a Dot device, leaving no room for misselection by an agent.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'send_text' follows a clear verb_noun pattern, and there are no other tools to create inconsistency or mixed conventions.

    Tool Count2/5

    A single tool is too few for a server's purpose, as it limits functionality to basic notifications without supporting other potential operations like device management or status checks. This feels thin and incomplete for a device interaction domain.

    Completeness2/5

    The tool surface is severely incomplete for interacting with an e-ink display device. While 'send_text' covers notification sending, there are obvious gaps such as retrieving device status, managing display settings, or handling other device-specific operations, which could lead to agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources