LINE Bot

Provides LINE Messaging API integration for pushing and broadcasting messages, managing rich menus, and retrieving user profiles via MCP.
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "tndfame-mcp_management": {
      "command": "npx",
      "args": [
        "@line/line-bot-mcp-server"
      ],
      "env": {
        "DESTINATION_USER_ID": "FILL_HERE",
        "CHANNEL_ACCESS_TOKEN": "FILL_HERE"
      }
    }
  }
}

You connect an AI agent to LINE via a dedicated MCP server that interacts with the LINE Messaging API. This server lets your agent push messages to LINE users, manage rich menus, retrieve profiles, and monitor quotas, all through a clear MCP interface.

How to use

You run the LINE Bot MCP Server as a local or containerized service and connect it to your MCP client. The server provides tools to push text and flex messages, broadcast messages to followers, fetch user profiles, manage rich menus, and check quotas. You can operate it with a simple MCP command configuration, and you supply your LINE Channel Access Token and a destination user ID to route messages.

How to install

Prerequisites: Node.js v20 or later. A LINE Official Account with Messaging API enabled. An MCP client that can invoke the LINE Bot MCP Server tools.

Configuration and usage notes

Configure your AI agent to run the LINE Bot MCP Server with the required environment variables. You must provide a Channel Access Token and, optionally, a default destination user ID. The following configuration examples show the MCP server entries you can use.

{
  "mcpServers": {
    "line-bot": {
      "command": "npx",
      "args": [
        "@line/line-bot-mcp-server"
      ],
      "env": {
        "CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
        "DESTINATION_USER_ID" : "FILL_HERE"
      }
    }
  }
}

Environment variables

Two key environment variables control operation. CHANNEL_ACCESS_TOKEN is required and DESTINATION_USER_ID is optional but required if your MCP Tool input does not include user_id.

{
  "mcpServers": {
    "line-bot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CHANNEL_ACCESS_TOKEN",
        "-e",
        "DESTINATION_USER_ID",
        "line/line-bot-mcp-server"
      ],
      "env": {
        "CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
        "DESTINATION_USER_ID" : "FILL_HERE"
      }
    }
  }
}

Tools and actions available

The server exposes several actions you can invoke through your MCP client. Each action corresponds to a LINE Messaging API operation and is described below.

Available tools

  • push_text_message: Pushes a simple text message to a user via LINE. Requires a user_id or DESTINATION_USER_ID and a message.text.

  • push_flex_message: Pushes a customizable flex message to a user via LINE. Requires a user_id or DESTINATION_USER_ID and a message with altText and content.

  • broadcast_text_message: Broadcasts a simple text message to all followers. Requires message.text.

  • broadcast_flex_message: Broadcasts a flexible message to all followers. Requires message.altText and message.content.

  • get_profile: Retrieves detailed LINE user profile information like display name, picture URL, status message, and language. Optional user_id to target a specific user.

  • get_message_quota: Returns the current message quota and usage for the LINE Official Account. No inputs.

  • get_rich_menu_list: Lists rich menus linked to your LINE Official Account. No inputs.

  • delete_rich_menu: Deletes a specified rich menu by its richMenuId.

  • set_rich_menu_default: Sets a rich menu as the default for your account. Requires richMenuId.

  • cancel_rich_menu_default: Clears the default rich menu. No inputs.

Security considerations

Securely store and rotate CHANNEL_ACCESS_TOKEN. Do not expose your destination user ID or tokens in client logs or repositories.

Troubleshooting tips

If messages fail to send, verify the Channel Access Token and that the LINE Official Account is correctly configured with the Messaging API. Check your MCP client configuration to confirm the correct environment variables are passed to the LINE Bot MCP Server.

Available tools

push_text_message

Push a simple text message to a LINE user by supplying the user_id (or DESTINATION_USER_ID) and the message text.

push_flex_message

Push a highly customizable flex message to a LINE user with altText and content, supporting bubble or carousel types.

broadcast_text_message

Broadcast a plain text message to all users who follow your LINE Official Account.

broadcast_flex_message

Broadcast a customizable flex message to all followers with altText and content.

get_profile

Retrieve detailed profile information for a LINE user, including display name, profile picture, status message, and language.

get_message_quota

Query the monthly message quota and current usage for your LINE Official Account.

get_rich_menu_list

Fetch the list of rich menus associated with your LINE Official Account.

delete_rich_menu

Delete a rich menu by its ID from your LINE Official Account.

set_rich_menu_default

Set a specific rich menu as the default for the account.

cancel_rich_menu_default

Cancel the default rich menu setting.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational