Skip to main content
Glama
Heartran

phonelink-mcp-server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to phonelink-mcp-server

No user-submitted related servers found.

    Related Servers

    • openmessage

      MaxGhenis
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for a local-first messaging workspace that integrates Google Messages, WhatsApp, and Signal. It enables reading, sending, searching messages, and managing conversations through MCP tools.
      63
      -

    • winauto-mcp

      PingPong2534
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that lets an LLM see and drive any running Windows app: attach a window, screenshot it, read its UI Automation tree, and send clicks, typed text, and key presses with pixel coordinates.
      -

    • DSHcontroller

      jgbrzzh
      A
      license
      Not graded
      quality
      B
      maintenance
      A Windows-local MCP server that enables MCP clients to discover and attach to existing DeepSeek Harness instances, manage sessions, send/observe/cancel tasks, select models, adjust settings and plugins, and automate the DSHL native Windows UI through UI Automation.
      1
      GPL 3.0

    • umbriel

      ObscuritySRL
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for driving any Windows app through five layers including OCR, UI Automation, and direct OS operations. Enables AI agents to control Windows desktop and OS cursor-free, even on background/locked windows.
      63 npm
      2
      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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct Phone Link surface or action: status, photos, messages, calls, notifications, UI inspection, send, call, and launch. There is no meaningful overlap between get_messages and get_calls or between send_message and make_call, and the debug tool is clearly differentiated as a troubleshooting utility.

    Naming Consistency5/5

    All tools share the phonelink_ prefix and use consistent snake_case verb_noun patterns: get_* for read operations and send_message, make_call, and launch_app for actions. This makes it easy to predict a tool's behavior from its name.

    Tool Count5/5

    Nine tools is well-scoped for a Phone Link automation server: it covers the main phone data surfaces plus two user-initiated actions and a launcher/debug aid. Each tool earns its place without bloat or obvious omissions.

    Completeness4/5

    The set covers the main Phone Link workflows: connection status, launching the app, reading photos/messages/calls/notifications, sending an SMS, and making a call. Minor gaps exist—photos are not downloadable and notification actions are absent—but these are reasonable boundaries for a UI-automation MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources