Skip to content
Back to search

line-bot-mcp-server

MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/line/line-bot-mcp-server with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/line/line-bot-mcp-server'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/line--line-bot-mcp-server/badge.svg)](/listings/line--line-bot-mcp-server)

HTML

<a href="/listings/line--line-bot-mcp-server"><img src="/api/listings/line--line-bot-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

requirements: - Node.js v22 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](https://developers.line.biz/en/docs/messaging-api/getting-started/#create-oa).

If you have a LINE Official Account, enable the Messaging API for your LINE Official Account by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager).

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](https://developers.line.biz/en/docs/basics/channel-access-token/#long-lived-channel-access-token). - `DESTINATION_USER_ID`: (optional) The default user ID of the recipient. If the Tool's input does not include `userId`, `DESTINATION_USER_ID` is required. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-user-ids/#get-own-user-id).

{
  "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"
      }
    }
  }
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 226 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [日本語版 READMEはこちら](README.ja.md)
  2. # LINE Bot MCP Server
  3. [![npmjs](https://badge.fury.io/js/%40line%2Fline-bot-mcp-server.svg)](https://www.npmjs.com/package/@line/line-bot-mcp-server)
  4. [Model Context Protocol (MCP)](https://github.com/modelcontextprotocol) server implementation that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
  5. ![](/assets/demo.png)
  6. > [!NOTE]
  7. > 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.
  8. ## Tools
  9. 1. **push_text_message**
  10. - Push a simple text message to a user via LINE.
  11. - **Inputs:**
  12. - `userId` (string?): The user ID to receive a message. Defaults to DESTINATION_USER_ID. Either `userId` or `DESTINATION_USER_ID` must be set.
  13. - `message.text` (string): The plain text content to send to the user.
  14. 2. **push_flex_message**
  15. - Push a highly customizable flex message to a user via LINE.
  16. - **Inputs:**
  17. - `userId` (string?): The user ID to receive a message. Defaults to DESTINATION_USER_ID. Either `userId` or `DESTINATION_USER_ID` must be set.
  18. - `message.altText` (string): Alternative text shown when flex message cannot be displayed.
  19. - `message.contents` (any): The contents of the flex message. This is a JSON object that defines the layout and components of the message.
  20. - `message.contents.type` (enum): Type of the container. 'bubble' for single container, 'carousel' for multiple swipeable bubbles.
  21. 3. **broadcast_text_message**
  22. - Broadcast a simple text message via LINE to all users who have followed your LINE Official Account.
  23. - **Inputs:**
  24. - `message.text` (string): The plain text content to send to the users.
  25. 4. **broadcast_flex_message**
  26. - Broadcast a highly customizable flex message via LINE to all users who have added your LINE Official Account.
  27. - **Inputs:**
  28. - `message.altText` (string): Alternative text shown when flex message cannot be displayed.
  29. - `message.contents` (any): The contents of the flex message. This is a JSON object that defines the layout and components of the message.
  30. - `message.contents.type` (enum): Type of the container. 'bubble' for single container, 'carousel' for multiple swipeable bubbles.
  31. 5. **get_profile**
  32. - Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.
  33. - **Inputs:**
  34. - `userId` (string?): The ID of the user whose profile you want to retrieve. Defaults to DESTINATION_USER_ID.
  35. 6. **get_message_quota**
  36. - Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage.
  37. - **Inputs:**
  38. - None
  39. 7. **get_rich_menu_list**
  40. - Get the list of rich menus associated with your LINE Official Account.
  41. - **Inputs:**
  42. - None
  43. 8. **delete_rich_menu**
  44. - Delete a rich menu from your LINE Official Account.
  45. - **Inputs:**
  46. - `richMenuId` (string): The ID of the rich menu to delete.
  47. 9. **set_rich_menu_default**
  48. - Set a rich menu as the default rich menu.
  49. - **Inputs:**
  50. - `richMenuId` (string): The ID of the rich menu to set as default.
  51. 10. **cancel_rich_menu_default**
  52. - Cancel the default rich menu.
  53. - **Inputs:**
  54. - None
  55. 11. **create_rich_menu**
  56. - Create a rich menu based on the given actions. Generate and upload an image. Set as default.
  57. - **Inputs:**
  58. - `chatBarText` (string): Text displayed in chat bar, also used as rich menu name.
  59. - `actions` (array): The actions of the rich menu. You can specify minimum 1 to maximum 6 actions. Each action can be one of the following types:
  60. - `postback`: For sending a postback action
  61. - `message`: For sending a text message
  62. - `uri`: For opening a URL
  63. - `datetimepicker`: For opening a date/time picker
  64. - `camera`: For opening the camera
  65. - `cameraRoll`: For opening the camera roll
  66. - `location`: For sending the current location
  67. - `richmenuswitch`: For switching to another rich menu
  68. - `clipboard`: For copying text to clipboard
  69. 12. **get_follower_ids**
  70. - Get a list of user IDs of users who have added the LINE Official Account as a friend. This allows you to obtain user IDs for sending messages without manually preparing them.
  71. - **Inputs:**
  72. - `start` (string?): Continuation token to get the next array of user IDs. Returned in the `next` property of a previous response.
  73. - `limit` (number?): The maximum number of user IDs to retrieve in a single request.
  74. 13. **get_group_summary**
  75. - Get the group chat summary including group ID, group name, and group icon URL, using the group ID.
  76. - **Inputs:**
  77. - `groupId` (string): The group ID of the target group chat.
  78. ## Installation (Using npx)
  79. requirements:
  80. - Node.js v22 or later
  81. ### Step 1: Create LINE Official Account
  82. This MCP server utilizes a LINE Official Account. If you do not have one, please create it by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-started/#create-oa).
  83. If you have a LINE Official Account, enable the Messaging API for your LINE Official Account by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager).
  84. ### Step 2: Configure AI Agent
  85. Please add the following configuration for an AI Agent like Claude Desktop or Cline.
  86. Set the environment variables or arguments as follows:
  87. - `CHANNEL_ACCESS_TOKEN`: (required) Channel Access Token. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/basics/channel-access-token/#long-lived-channel-access-token).
  88. - `DESTINATION_USER_ID`: (optional) The default user ID of the recipient. If the Tool's input does not include `userId`, `DESTINATION_USER_ID` is required. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-user-ids/#get-own-user-id).
  89. ```json
  90. {
  91. "mcpServers": {
  92. "line-bot": {
  93. "command": "npx",
  94. "args": [
  95. "@line/line-bot-mcp-server"
  96. ],
  97. "env": {
  98. "NPM_CONFIG_IGNORE_SCRIPTS": "true",
  99. "CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
  100. "DESTINATION_USER_ID" : "FILL_HERE"
  101. }
  102. }
  103. }
  104. }
  105. ```
  106. ## Installation (Using Docker)
  107. ### Step 1: Create LINE Official Account
  108. This MCP server utilizes a LINE Official Account. If you do not have one, please create it by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-started/#create-oa).
  109. If you have a LINE Official Account, enable the Messaging API for your LINE Official Account by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager).
  110. ### Step 2: Build line-bot-mcp-server image
  111. Clone this repository:
  112. ```
  113. git clone git@github.com:line/line-bot-mcp-server.git
  114. ```
  115. Build the Docker image:
  116. ```
  117. docker build -t line/line-bot-mcp-server .
  118. ```
  119. ### Step 3: Configure AI Agent
  120. Please add the following configuration for an AI Agent like Claude Desktop or Cline.
  121. Set the environment variables or arguments as follows:
  122. - `mcpServers.args`: (required) The path to `line-bot-mcp-server`.
  123. - `CHANNEL_ACCESS_TOKEN`: (required) Channel Access Token. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/basics/channel-access-token/#long-lived-channel-access-token).
  124. - `DESTINATION_USER_ID`: (optional) The default user ID of the recipient. If the Tool's input does not include `userId`, `DESTINATION_USER_ID` is required.
  125. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-user-ids/#get-own-user-id).
  126. ```json
  127. {
  128. "mcpServers": {
  129. "line-bot": {
  130. "command": "docker",
  131. "args": [
  132. "run",
  133. "-i",
  134. "--rm",
  135. "-e",
  136. "CHANNEL_ACCESS_TOKEN",
  137. "-e",
  138. "DESTINATION_USER_ID",
  139. "line/line-bot-mcp-server"
  140. ],
  141. "env": {
  142. "CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
  143. "DESTINATION_USER_ID" : "FILL_HERE"
  144. }
  145. }
  146. }
  147. }
  148. ```
  149. ## Local Development with Inspector
  150. You can use the MCP Inspector to test and debug the server locally.
  151. ### Prerequisites
  152. 1. Clone the repository:
  153. ```bash
  154. git clone git@github.com:line/line-bot-mcp-server.git
  155. cd line-bot-mcp-server
  156. ```
  157. 2. Install dependencies:
  158. ```bash
  159. npm install
  160. ```
  161. 3. Build the project:
  162. ```bash
  163. npm run build
  164. ```
  165. ### Run the Inspector
  166. After building the project, you can start the MCP Inspector:
  167. ```bash
  168. npx @modelcontextprotocol/inspector node dist/index.js \
  169. -e CHANNEL_ACCESS_TOKEN="YOUR_CHANNEL_ACCESS_TOKEN" \
  170. -e DESTINATION_USER_ID="YOUR_DESTINATION_USER_ID"
  171. ```
  172. This will start the MCP Inspector interface where you can interact with the LINE Bot MCP Server tools and test their functionality.
  173. ## Versioning
  174. This project respects semantic versioning
  175. See http://semver.org/
  176. ## Contributing
  177. Please check [CONTRIBUTING](./CONTRIBUTING.md) before making a contribution.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.