Skip to main content
Glama
onlygummy

line-desktop-mcp

by onlygummy

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
line_statusA

Check the 5 readiness steps: Chrome, attach, extension, page, login.

Call this first when unsure the setup works. On failure the result carries a next field telling the user what to do.

wait_loginA

Open Chrome and wait until the user finishes LINE login.

list_roomsA

List chat rooms with unread counts and last-message preview.

Prefer data-mid or name from the result when calling other tools: index values shift when rooms reorder.

get_messagesA

Read latest messages, opening a room first when room is given.

Side-effect free: no files written. Only rows rendered on screen are visible (virtualized list), so deep history still returns just what the DOM holds.

unread_digestA

Unread rooms with latest preview in one call.

Cheapest "what is unread" check. For full message bodies use unread_full instead.

unread_fullA

Unread rooms with their message bodies, one room at a time.

Opens each unread room, so cost grows with unread count. Progress is reported per room.

search_messagesA

Search a keyword inside the given rooms only.

Returns only rooms with matches, plus error entries for refs that match no room (a bad ref never fails the whole search). Sequential, roughly seconds per room, with progress reported per room.

probe_sessionA

Check login state and redacted storage without changing anything.

Call this before clear_session, or when login looks flaky. Returns key names with type and length only, never secrets.

clear_sessionA

Wipe the LINE login only; extension install stays.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools target a distinct concern: setup status, login, rooms, messages, unread digests, search, and session probing/reset. A few pairs overlap slightly—line_status vs probe_session and list_rooms vs unread_digest—but the descriptions give clear guidance on when to use which.

Naming Consistency4/5

The set mostly follows a verb_noun snake_case pattern like list_rooms, get_messages, clear_session, and search_messages. The deviations are minor: line_status, unread_digest, and unread_full are noun/adjective-led rather than verb-led, but the overall style is consistent and readable.

Tool Count5/5

Nine tools is well within the ideal range for this server's scope. Each tool covers a meaningful piece of the LINE desktop workflow without redundancy or bloat.

Completeness4/5

The surface is complete for a read-focused LINE automation workflow: setup, login, room listing, message retrieval, unread digest/full views, search, and session clearing are all present. The only notable gaps are send_message and mark-as-read, which suggest the toolset is intentionally read-only but would be needed for broader chat interaction.

Maintenance

ActivityMaintained
ResponsivenessNo issues