Skip to main content
Glama
DaBlitzStein

kdeconnect-mcp

by DaBlitzStein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to kdeconnect-mcp

No user-submitted related servers found.

    Related Servers

    • Phone MCP

      mjrafg
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to use a real Android phone with a SIM to retrieve phone numbers, receive SMS verification codes, and manage SMS messages.
      -

    • iMessage MCP

      thenavidm
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents on macOS to securely read and search the local Messages database, catch up on missed messages via a persistent inbox, and send texts or files to allowlisted chats, with optional voice note transcription and text-to-speech.
      MIT

    • whatsapp

      memsjava
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send WhatsApp notifications to their owner and read the owner's replies through a local gateway, without requiring the Meta Business API.
      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

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (pairing, scanning, status, SMS, calls, notifications). The event family (get_activity, get_events, wait_for_events, search_activity, list_active_notifications) overlaps conceptually, but descriptions clarify different consumption modes; a few could be confused by name alone.

    Naming Consistency5/5

    All 16 tools follow a consistent verb_noun snake_case pattern (list_devices, get_status, accept_pairing, sync_sms_history). No mixed conventions or vague verbs are present.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range, but each tool addresses a distinct need in the pairing/event/SMS/call lifecycle. The count is justified by the broad scope, though a few could be consolidated.

    Completeness4/5

    The surface covers the full pairing workflow, event consumption (timeline, cursor, long-poll, acknowledge), SMS/call history, active notifications, and redaction stats. Missing device detail/forget actions and send commands, but core monitoring workflows are complete.

    Resources