LINE Bot MCP Server (SSE Support)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for SSE transport. Default: 3000 | 3000 |
| MCP_TRANSPORT | No | Transport protocol to use. Options: stdio (default), sse | stdio |
| DESTINATION_USER_ID | No | The default user ID of the recipient. If the Tool's input does not include user_id, DESTINATION_USER_ID is required. | |
| CHANNEL_ACCESS_TOKEN | Yes | Channel Access Token. You can confirm this by following the instructions in the LINE Developers documentation. |
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 |
|---|---|
| push_text_messageB | Push a simple text message to a user via LINE. Use this for sending plain text messages without formatting. |
| push_flex_messageC | Push a highly customizable flex message to a user via LINE. Supports both bubble (single container) and carousel (multiple swipeable bubbles) layouts. |
| broadcast_text_messageA | Broadcast a simple text message via LINE to all users who have followed your LINE Official Account. Use this for sending plain text messages without formatting. Please be aware that this message will be sent to all users. |
| broadcast_flex_messageA | Broadcast a highly customizable flex message via LINE to all users who have added your LINE Official Account. Supports both bubble (single container) and carousel (multiple swipeable bubbles) layouts. Please be aware that this message will be sent to all users. |
| get_profileB | Get detailed profile information of a LINE user including display name, profile picture URL, status message and language. |
| get_message_quotaA | Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage. |
| get_rich_menu_listB | Get the list of rich menus associated with your LINE Official Account. |
| delete_rich_menuC | Delete a rich menu from your LINE Official Account. |
| set_rich_menu_defaultC | Set a rich menu as the default rich menu. |
| cancel_rich_menu_defaultB | Cancel the default rich menu. |
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 10 tools
Most tools have distinct purposes, such as broadcast vs. push for mass vs. individual messaging, and flex vs. text for message types. However, cancel_rich_menu_default and delete_rich_menu could be slightly confusing as both involve removing rich menus, though their descriptions clarify one cancels a default setting while the other deletes the menu entirely.
All tool names follow a consistent verb_noun pattern with snake_case, such as broadcast_flex_message, get_profile, and set_rich_menu_default. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 10 tools, the count is well-scoped for a LINE Bot server, covering core messaging, user profile management, rich menu operations, and quota checking. Each tool serves a clear purpose without redundancy or bloat.
The tool set covers essential LINE Bot operations, including message broadcasting/pushing, user profile retrieval, rich menu management, and quota monitoring. A minor gap is the lack of tools for creating or updating rich menus, which might limit full lifecycle management, but agents can still handle common workflows effectively.