Line Chrome MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINE_GATEWAY_URL | Yes | The base URL of the running LINE gateway that the stdio MCP proxy connects to. | |
| LINE_GATEWAY_TOKEN | No | Optional bearer token for the gateway when it is configured to require authentication (e.g., when bound to a non-loopback address). |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| line_get_statusA | Get the LINE gateway, Chrome CDP, and active LINE page status. |
| line_get_capabilitiesA | Get capabilities currently implemented by the active LINE adapter. |
| line_search_chatsB | List or search LINE chats. Chat IDs returned here are used by message tools. |
| line_get_messagesA | Read messages from a LINE chat. Use before as a cursor for older history. |
| line_send_messageA | Queue a text message to a LINE chat. Returns an operation that can be polled with line_get_operation. |
| line_get_operationB | Get the current state and result of an asynchronous gateway operation. |
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
Each tool targets a distinct concern: status, capabilities, chat search, message reading, message sending, and async operation polling. Even get_status and get_capabilities are clearly separated by describing gateway/CDP state versus adapter feature implementation.
All tools share the line_ prefix and follow a consistent verb_noun snake_case pattern: get_status, get_capabilities, search_chats, get_messages, send_message, get_operation. This makes the toolset highly predictable.
Six tools is well-scoped for a LINE automation adapter: status, capabilities, chat discovery, message retrieval, sending, and async operation tracking. Each tool earns its place without redundancy or bloat.
The toolset covers the core LINE automation workflow: discover chats, read messages, send messages, and track async operations. Minor gaps exist around live message subscription/streaming and cancellation of queued operations, but these are not fatal for the apparent purpose.