LINE Bot MCP Server (SSE Support)
Integrates the LINE Messaging API to connect AI agents to LINE Official Accounts, enabling tools to send text and flex messages (push or broadcast), retrieve user profiles, manage message quotas, and configure rich menus.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LINE Bot MCP Server (SSE Support) send 'Your reservation is confirmed!' to user U123456789"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LINE Bot MCP Server (with SSE Support)
Model Context Protocol (MCP) server implementation that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.

This repository is afork of the official LINE Bot MCP Server with additional SSE (Server-Sent Events) transport support. The original repository only supports stdio transport.
🔄 Fork Information
Original Repository: line/line-bot-mcp-server
Fork Enhancement: Added SSE transport support for web-based integrations
Docker Image: Available on Docker Hub as
acquojp/line-bot-mcp-server-sse:latest
This repository is provided as a preview version. While we offer it for experimental purposes, please be aware that it may not include complete functionality or comprehensive support.
Related MCP server: LINE Bot MCP Server
Transport Support
This MCP server supports multiple transport protocols:
stdio (default): Standard input/output for local integrations
SSE: Server-Sent Events over HTTP for web-based integrations
Tools
push_text_message
Push a simple text message to a user via LINE.
Inputs:
user_id(string?): The user ID to receive a message. Defaults to DESTINATION_USER_ID. Eitheruser_idorDESTINATION_USER_IDmust be set.message.text(string): The plain text content to send to the user.
push_flex_message
Push a highly customizable flex message to a user via LINE.
Inputs:
user_id(string?): The user ID to receive a message. Defaults to DESTINATION_USER_ID. Eitheruser_idorDESTINATION_USER_IDmust be set.message.altText(string): Alternative text shown when flex message cannot be displayed.message.content(any): The content of the flex message. This is a JSON object that defines the layout and components of the message.message.contents.type(enum): Type of the container. 'bubble' for single container, 'carousel' for multiple swipeable bubbles.
broadcast_text_message
Broadcast a simple text message via LINE to all users who have followed your LINE Official Account.
Inputs:
message.text(string): The plain text content to send to the users.
broadcast_flex_message
Broadcast a highly customizable flex message via LINE to all users who have added your LINE Official Account.
Inputs:
message.altText(string): Alternative text shown when flex message cannot be displayed.message.content(any): The content of the flex message. This is a JSON object that defines the layout and components of the message.message.contents.type(enum): Type of the container. 'bubble' for single container, 'carousel' for multiple swipeable bubbles.
get_profile
Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.
Inputs:
user_id(string?): The ID of the user whose profile you want to retrieve. Defaults to DESTINATION_USER_ID.
get_message_quota
Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage.
Inputs:
None
get_rich_menu_list
Get the list of rich menus associated with your LINE Official Account.
Inputs:
None
delete_rich_menu
Delete a rich menu from your LINE Official Account.
Inputs:
richMenuId(string): The ID of the rich menu to delete.
set_rich_menu_default
Set a rich menu as the default rich menu.
Inputs:
richMenuId(string): The ID of the rich menu to set as default.
cancel_rich_menu_default
Cancel the default rich menu.
Inputs:
None
Installation (Using npx)
requirements:
Node.js v20 or later
Step 1: Create LINE Official Account
This MCP server utilizes a LINE Official Account. If you do not have one, please create it by following this instructions.
If you have a LINE Official Account, enable the Messaging API for your LINE Official Account by following this instructions.
Step 2: Configure AI Agent
Please add the following configuration for an AI Agent like Claude Desktop or Cline.
Set the environment variables or arguments as follows:
CHANNEL_ACCESS_TOKEN: (required) Channel Access Token. You can confirm this by following this instructions.DESTINATION_USER_ID: (optional) The default user ID of the recipient. If the Tool's input does not includeuser_id,DESTINATION_USER_IDis required. You can confirm this by following this instructions.MCP_TRANSPORT: (optional) Transport protocol to use. Options:stdio(default),sseMCP_PORT: (optional) Port for SSE transport. Default:3000
Using stdio transport (default)
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
"DESTINATION_USER_ID" : "FILL_HERE"
}
}
}
}Using SSE transport
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
"DESTINATION_USER_ID" : "FILL_HERE",
"MCP_TRANSPORT" : "sse",
"MCP_PORT" : "3000"
}
}
}
}For SSE transport, the server will start an HTTP server with the following endpoints:
GET /sse- Establish SSE connectionPOST /messages- Send messages to the serverGET /health- Health check endpoint
Installation (Using Docker)
Option A: Use Pre-built Docker Image (Recommended)
You can use the pre-built Docker image from Docker Hub without building locally:
# Pull the latest image
docker pull acquojp/line-bot-mcp-server-sse:latest
# Run directly
docker run --rm -p 3000:3000 \
-e CHANNEL_ACCESS_TOKEN="your_token" \
-e DESTINATION_USER_ID="your_user_id" \
acquojp/line-bot-mcp-server-sse:latestOption B: Build from Source
Step 1: Create LINE Official Account
This MCP server utilizes a LINE Official Account. If you do not have one, please create it by following this instructions.
If you have a LINE Official Account, enable the Messaging API for your LINE Official Account by following this instructions.
Step 2: Build line-bot-mcp-server image
Clone this repository:
git clone https://github.com/your-username/line-bot-mcp-server.gitBuild the Docker image:
docker build -t line-bot-mcp-server-sse .Step 3: Configure AI Agent
Please add the following configuration for an AI Agent like Claude Desktop or Cline.
Set the environment variables or arguments as follows:
mcpServers.args: (required) The path toline-bot-mcp-server.CHANNEL_ACCESS_TOKEN: (required) Channel Access Token. You can confirm this by following this instructions.DESTINATION_USER_ID: (optional) The default user ID of the recipient. If the Tool's input does not includeuser_id,DESTINATION_USER_IDis required. You can confirm this by following this instructions.MCP_TRANSPORT: (optional) Transport protocol to use. Options:stdio(default),sseMCP_PORT: (optional) Port for SSE transport. Default:3000
Using SSE transport (default) - Docker Hub Image
{
"mcpServers": {
"line-bot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-p",
"3000:3000",
"-e",
"CHANNEL_ACCESS_TOKEN",
"-e",
"DESTINATION_USER_ID",
"acquojp/line-bot-mcp-server-sse:latest"
],
"env": {
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
"DESTINATION_USER_ID" : "FILL_HERE"
}
}
}
}Using stdio transport - Docker Hub Image
{
"mcpServers": {
"line-bot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CHANNEL_ACCESS_TOKEN",
"-e",
"DESTINATION_USER_ID",
"-e",
"MCP_TRANSPORT",
"acquojp/line-bot-mcp-server-sse:latest"
],
"env": {
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
"DESTINATION_USER_ID" : "FILL_HERE",
"MCP_TRANSPORT" : "stdio"
}
}
}
}Versioning
This project respects semantic versioning
Fork Information & Differences
This repository is a fork of the official LINE Bot MCP Server with the following enhancements:
✨ Added Features
SSE (Server-Sent Events) Transport Support: Enables web-based integrations and HTTP connections
Multi-Transport Architecture: Supports both stdio (original) and SSE transports
Docker Hub Distribution: Pre-built Docker images available for easy deployment
Production-Ready Configuration: Optimized for both development and production environments
🔄 Transport Comparison
Feature | stdio (Original) | SSE (Added) |
Use Case | Local CLI tools, direct process communication | Web applications, HTTP-based integrations |
Connection | Standard input/output streams | HTTP + Server-Sent Events |
Deployment | Process-based | Server-based (HTTP) |
Port | Not required | Requires port (default: 3000) |
Scalability | Single process | Multiple concurrent connections |
🐳 Docker Hub
Repository:
acquojp/line-bot-mcp-server-sseArchitecture: AMD64 (x86_64) - optimized for most cloud platforms
Tags:
latest,v1.0.0,amd64,arm64
Contributing
Please check CONTRIBUTING before making a contribution.
Contributing to This Fork
If you'd like to contribute to the SSE transport features or other enhancements in this fork, please:
Fork this repository
Create a feature branch
Make your changes
Submit a pull request
For contributions to the original LINE Bot MCP Server, please visit the official repository.
Available Tools
10 toolsbroadcast_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.
Inputs: message (required).
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.
Inputs: message (required).
get_message_quotaA
Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage.
Inputs: no named parameters.
get_profileB
Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.
Inputs: userId.
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.
Inputs: message (required), userId.
push_text_messageB
Push a simple text message to a user via LINE. Use this for sending plain text messages without formatting.
Inputs: message (required), userId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceModel Context Protocol server implementation that integrates the LINE Messaging API to connect AI agents with LINE Official Accounts, enabling agents to send messages to users.Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI agents to send messages, manage rich menus, and interact with users through LINE Official Accounts via the LINE Messaging API. Supports both individual messaging and broadcasting to all followers with text and customizable flex messages.18Apache 2.0
- AlicenseAqualityNot gradedmaintenanceConnects an AI agent to a LINE Official Account through the LINE Messaging API, enabling it to push and broadcast text or flex messages to users. It also supports retrieving user profiles, message quotas, follower IDs, and group summaries, plus creating and managing rich menus.13Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to operate one or many LINE Official Accounts through natural language — broadcasts, Flex and tappable Rich Messages with zero-setup image hosting, rich menus, coupons, audiences, insights, webhooks, and LINE Shopping — with pre-flight quota and quiet-hour guardrails. It ships 51 tools (37 messaging + 14 shopping) plus resources and guided prompts, and runs over stdio or token-authenticated HTTP with any MCP-compatible host.200 npmMIT