LINE Local MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINE_MCP_DB_PATH | No | Specify the database file; use when multiple accounts are present. | |
| LINE_MCP_KEYCHAIN_SERVICE | No | Change the Keychain service name. | |
| LINE_MCP_REDACT_SENSITIVE | No | Set to false to disable sensitive string redaction (not recommended). | true |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| line_statusA | Check whether the local LINE Desktop database is readable and how fresh it is. |
| list_chatsA | Find recent LINE conversations and their stable chat IDs. Use before get_messages when the chat ID is unknown. Official accounts are excluded unless explicitly requested. |
| get_messagesA | Read both sides of one LINE conversation by chat ID, ordered oldest to newest. |
| search_messagesA | Search message text across both sent and received LINE messages. Optionally restrict by chat and time. Official accounts are excluded by default. |
| get_recent_activityA | Return recent conversations with both sides of their messages, grouped by chat. Use this for daily or weekly briefs. Official accounts are excluded by default. |
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 5 tools
Most tools are clearly distinct, but get_messages and get_recent_activity overlap in returning message content, differing mainly in scope (single chat vs. grouped recent conversations). Descriptions help clarify use cases, so ambiguity is low.
Four tools follow a clear verb_noun pattern (get_messages, list_chats, search_messages, get_recent_activity). line_status deviates by using a noun phrase rather than an action verb, breaking the pattern slightly.
Five tools is well-scoped for a local LINE database reader. Each tool covers a distinct core need: status, listing chats, reading messages, searching, and recent activity.
The toolset covers the main read-only workflows for LINE messaging: discovering chats, retrieving conversations, searching message text, and checking recent activity. No significant gaps are apparent for the stated purpose.