Skip to main content
Glama
Sign In
mcp-macos-popup

mcp-macos-popup

by vakandi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-macos-popup

No user-submitted related servers found.

    Related Servers

    • mcp-macos-cua

      bradthebeeble
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control macOS desktop apps via screenshots, mouse clicks, keyboard input, accessibility queries, and AppleScript.
      11
      12 npm
      MIT

    • macos-desktop-control

      d-wwei
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides native macOS desktop automation for AI agents, enabling screen capture, mouse/keyboard control, window management, and iOS/Android simulator control in both foreground and background modes without focus stealing.
      5
      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
      28 npm
      1
      MIT

    • control-mouse-mac-mcp

      wwwang176
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI MCP clients to control macOS through screenshots, mouse clicks, scrolling and dragging, Unicode keyboard input and shortcuts, clipboard access, and window management, with multi-monitor and Retina coordinate handling plus visual action feedback.
      MIT

    • Automation MCP

      ashwwwin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automate macOS desktop tasks including mouse control, keyboard input, screenshots, window management, and UI interaction.
      10 npm
      415
      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 5 tools

    Disambiguation4/5

    show_popup vs show_docs are the closest pair, but descriptions clearly separate them by content type (quick notification vs markdown) and duration. list_screens and get_focused_screen overlap since list_screens already reports focus, making the focused-only tool somewhat redundant, but each still has a distinct intent.

    Naming Consistency5/5

    All five tools follow a clean snake_case verb_noun pattern (list_screens, get_focused_screen, dismiss_all_popups, show_popup, show_docs). No mixed conventions or camelCase deviations.

    Tool Count5/5

    Five tools is well-scoped for a popup-display server: enumerate screens, get the active screen, show a quick popup, show a rich popup, and dismiss all. Each earns its place with no filler.

    Completeness4/5

    Core lifecycle is covered: discover screens, target the focused one, show two popup styles, and clear them. Minor gaps exist—no individual popup dismissal (only dismiss_all_popups) and no way to list currently active popups.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources