LINE Bot MCP Server
Official LINE MCP server: an agent sends messages through the Messaging API from your LINE Official Account
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Sends messages to real users from your account
- Broadcasts to all followers of an official account
- Handles a channel access token and manages rich menus
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/line-bot-mcp-serverDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio --env NPM_CONFIG_IGNORE_SCRIPTS=true --env 'CHANNEL_ACCESS_TOKEN=<your CHANNEL_ACCESS_TOKEN>' line-bot -- npx @line/line-bot-mcp-serverOr add to the file .mcp.json, in the project
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
code --add-mcp '{"name":"line-bot","type":"stdio","command":"npx","args":["@line/line-bot-mcp-server"],"env":{"NPM_CONFIG_IGNORE_SCRIPTS":"true","CHANNEL_ACCESS_TOKEN":"<your CHANNEL_ACCESS_TOKEN>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"line-bot": {
"type": "stdio",
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add line-bot --env NPM_CONFIG_IGNORE_SCRIPTS=true --env 'CHANNEL_ACCESS_TOKEN=<your CHANNEL_ACCESS_TOKEN>' -- npx @line/line-bot-mcp-serverOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.line-bot]
command = "npx"
args = ["@line/line-bot-mcp-server"]
env = { NPM_CONFIG_IGNORE_SCRIPTS = "true", CHANNEL_ACCESS_TOKEN = "<your CHANNEL_ACCESS_TOKEN>" }If the file already exists, append the block to the end.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
gemini mcp add -s user -e NPM_CONFIG_IGNORE_SCRIPTS=true -e 'CHANNEL_ACCESS_TOKEN=<your CHANNEL_ACCESS_TOKEN>' line-bot npx @line/line-bot-mcp-serverOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"line-bot": {
"type": "local",
"command": [
"npx",
"@line/line-bot-mcp-server"
],
"environment": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "<your CHANNEL_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
CHANNEL_ACCESS_TOKENsecret, requiredDESTINATION_USER_IDoptional
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add the line-bot server to your MCP client config: command npx, args @line/line-bot-mcp-server, and set CHANNEL_ACCESS_TOKEN and optionally DESTINATION_USER_ID in env. Node.js 22 or newer is required.
Other ways from the author
{
"mcpServers": {
"line-bot": {
"command": "npx",
"args": ["@line/line-bot-mcp-server"],
"env": {
"NPM_CONFIG_IGNORE_SCRIPTS": "true",
"CHANNEL_ACCESS_TOKEN": "FILL_HERE",
"DESTINATION_USER_ID": "FILL_HERE"
}
}
}
}Node.js 22 or newer is required. DESTINATION_USER_ID is optional if userId is passed in the call.
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to the LINE Messaging API. It sends plain text and styled flex messages to a specific user, broadcasts them to all followers of an official account, and reads a user profile and the remaining message quota. It manages rich menus separately: create, delete and set as default, and it returns the follower list and a group chat summary. It is built by LINE itself and the repository is marked as a preview version.
Who it is for. For marketers, support and business owners who talk to customers through a LINE Official Account.
Good fit when
- You need to send LINE messages to customers from agent workflows
- You need a broadcast to all followers of an official account
- You need to manage rich menus and check profiles and quota
Not a fit when
- You have no LINE Official Account with the Messaging API enabled
- You need guaranteed completeness and support; this is a preview version
Example request
Send a welcome message to a follower and show how many messages are left in the quotaLimitations
You need a LINE Official Account with the Messaging API enabled and a long-lived channel access token. Some tools require a recipient id, so either pass userId or set DESTINATION_USER_ID. The repository is marked as a preview version, so features and support may be incomplete. The npx launch needs Node.js 22 or newer; a Docker option is also available.
How to disable. Remove the line-bot block from your MCP client config and restart it. If you used Docker, remove the built image.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| CHANNEL_ACCESS_TOKEN required, secret | Long-lived channel access token of the LINE official account |
| DESTINATION_USER_ID | Default recipient id used when a call omits userId |
Security check
- Sends messages to real users from your account
- Broadcasts to all followers of an official account
- Handles a channel access token and manages rich menus
README in short
The README lists tools for sending text and flex messages, broadcasts, reading profiles and quota, managing rich menus, and getting the follower list and a group chat summary. Installation is shown via npx with Node.js 22 and via building a Docker image. Setup sets CHANNEL_ACCESS_TOKEN and the optional DESTINATION_USER_ID, with configs for Claude Desktop and Cline. It also shows running the MCP Inspector for local debugging. The project is a preview version, licensed under Apache 2.0.
FAQ
Where do I get a channel access token?
In the LINE developer console after enabling the Messaging API for an official account you use a long-lived channel access token.
Why is DESTINATION_USER_ID needed?
It is the default recipient id. If a tool call omits userId, the value from DESTINATION_USER_ID is used.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail