line-selfbot-mcp
Related Servers
Alternatives to line-selfbot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to read and send messages through LINE Desktop via MCP, supporting manual or automatic sending without official LINE API tokens.137 npm127MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to operate a personal LINE account through MCP, listing friends and groups, retrieving and searching message history, and sending text, mentions, and registered media. Also supports group creation, display-name changes, and reply drafting based on owner-approved conversation history.MIT
- AlicenseNot gradedqualityDmaintenanceGives Claude Desktop read-only access to your WhatsApp chats and message history via a local MCP server.2 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending LINE messages (push, multicast, broadcast), retrieving user profiles, checking quotas, and sending flex messages via Claude using the LINE Messaging API.62 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read WhatsApp Desktop chats on a Mac, including messages, images, documents, and locally transcribed audio, through a local MCP server. Everything runs on the Mac with read-only access and no messages sent.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
TDQS
Scored across 14 tools
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.
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.
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.
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.