Skip to main content
Glama
um1981

line-selfbot-mcp

by um1981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to line-selfbot-mcp

No user-submitted related servers found.

    Related Servers

    • line-desktop-mcp

      dtwang
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to read and send messages through LINE Desktop via MCP, supporting manual or automatic sending without official LINE API tokens.
      59 npm
      121
      MIT

    • line-mcp-server

      iamsamitdev
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables sending LINE messages (push, multicast, broadcast), retrieving user profiles, checking quotas, and sending flex messages via Claude using the LINE Messaging API.
      -

    • line-render-mcp

      pdasource
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables sending LINE text messages and Flex Messages to user or group IDs, checking message quota, and receiving group webhooks via a remote MCP endpoint for ChatGPT integration.
      -

    • LINE Local MCP

      DforDennies
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable AI clients to search both sides of a user's own macOS LINE Desktop chat history — listing chats, reading messages, searching text, and pulling recent activity from local read-only database snapshots. It never sends messages, marks chats read, clicks through the UI, or requires a LINE Official Account.
      MIT

    • line-desktop-mcp

      onlygummy
      A
      license
      A
      quality
      B
      maintenance
      Enables automation of LINE messaging through the Chrome extension, allowing users to check status, list chat rooms, read messages, search conversations, and manage login sessions via MCP tools.
      9
      40 PyPI
      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.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets (profile, friends, chats, sending by media type). The only mild overlap is between get_new_messages and wait_for_message (both retrieve incoming messages, differing only in blocking behavior), plus a slight image-specific vs generic download split (get_message_image vs download_message_file), but descriptions differentiate them adequately.

    Naming Consistency5/5

    All 14 names follow a consistent snake_case verb_noun pattern (get_my_profile, list_chats, send_message, download_message_file, etc.). Even the less common verbs (wait_for, rename) fit the same predictable scheme.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and each maps to a concrete messaging operation. Nothing feels redundant or bloated for a LINE automation server.

    Completeness4/5

    The surface covers the core lifecycle: read/update own profile, list chats/friends/members, read history, retrieve media, send text/image/file, and receive messages (blocking and polling). Minor gaps exist (no delete/recall message, message search, or friend add/block), but agents can accomplish the primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources