line-desktop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Reads your own LINE chats. Call login first: it returns at once when the saved session still works, and only opens a QR window when it does not. Then use list_chats to find the chat and get_messages to read it, or search_messages to look for text across what has already been read. For what needs attention, call unread once instead of reading every chat. Every message read is stored in a local SQLite archive and every image is saved as a backup; nothing is sent to LINE and nothing is marked as read. logout ends the session and deletes the saved login, not the archive.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Log in by scanning a QR code in a window on this machine. Call this first. It returns at once when the saved session still works,
so it is safe to call on every start. Otherwise it opens the
'Line Desktop MCP' window, shows the QR, and waits up to The window appears on this machine, so the login cannot be completed from a different host. Keep the session file private: it holds the access token and the Letter Sealing keys. |
| logoutA | Log this device out of LINE and delete the saved session. LINE is asked to invalidate the session first. If that request fails,
the local file is deleted anyway, because the stored token is what
matters. Your phone stays logged in: only this server's device is
signed out, and the next The archive and the image backups are kept, so nothing that was already read is lost. Every tool still needs a login before it can reach LINE again, because the session file is what they run on. |
| list_chatsA | List your LINE chats with name, kind, unread count and last preview. Call this before |
| get_messagesA | Read the newest messages of one LINE chat, oldest first. Pass Pass Returns a JSON result plus the images those messages contain. Messages
are decrypted when the saved session holds the Letter Sealing keys; a
sealed message that cannot be opened has Pass Check |
| search_messagesA | Search archived messages for text, or for a message kind. Pass Searches the local archive, which holds only the messages this server
has read. Read Narrow the search with
Text search only sees messages that have text: images, stickers, and
sealed messages that could not be decrypted never match a
|
| unreadA | List chats with unread messages and the newest messages in each. One call instead of one It costs one LINE request per chat, so the caps are low on purpose.
Images are downloaded only with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.