line-desktop-mcp
Related Servers
Alternatives to line-desktop-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets MCP clients automate a logged-in LINE Chrome extension, enabling chat search, message reading, text sending, and live event streaming for messages and chat updates.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to read and send messages through LINE Desktop via MCP, supporting manual or automatic sending without official LINE API tokens.131MIT
- AlicenseNot gradedqualityCmaintenanceEnables a single LINE account to be managed over MCP, with status checks, chat listing, recent message retrieval, and two-step text message sending.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to manage personal LINE connections via QR authentication, select one-to-one or group chats, inspect stored message history and send status, and queue user-approved text messages.3MIT
- 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
- AlicenseCqualityCmaintenanceMCP server for browser automation that drives Chrome via an extension, preserving login state and offering 45 tools for navigation, interaction, scraping, and screenshots.535MIT
TDQS
Scored across 6 tools
login/logout, list_chats, get_messages and search_messages each target a distinct action, but `unread` overlaps with `list_chats` (chat listing) and `get_messages` (newest messages per chat). The descriptions do a good job distinguishing the digest use case from full reads, so misselection is unlikely but possible.
The core read tools follow a clean verb_noun pattern (list_chats, get_messages, search_messages), but `login`, `logout` and especially `unread` break it — `unread` is an adjective with no verb and gives no hint of the action performed. Mixed conventions, though still readable.
Six tools is well-scoped for a LINE client: session handling, chat listing, message reading, search and an unread digest. Each tool earns its place with no redundancy padding the surface.
The surface is deliberately read-only: there is no send_message, no reply/react, no mark-as-read, and no way to act on what is read. Coverage of the reading/archiving lifecycle is excellent, but for a messaging domain the write side is a notable gap that will dead-end agents asked to respond.