Labsco
acquo logo

LINE Bot MCP Server

from acquo

Connects an AI agent to a LINE Official Account using the LINE Messaging API.

πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedAccount requiredAdvanced setup
#devops#git

ζ—₯本θͺžη‰ˆ READMEはこけら

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.

[!NOTE] This repository is a fork of the official LINE Bot MCP Server with additional SSE (Server-Sent Events) transport support. The original repository only supports stdio transport.

πŸ”„ Fork Information

[!NOTE] 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.

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

  1. 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. Either user_id or DESTINATION_USER_ID must be set.
      • message.text (string): The plain text content to send to the user.
  2. 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. Either user_id or DESTINATION_USER_ID must 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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
  7. get_rich_menu_list
    • Get the list of rich menus associated with your LINE Official Account.
    • Inputs:
      • None
  8. delete_rich_menu
    • Delete a rich menu from your LINE Official Account.
    • Inputs:
      • richMenuId (string): The ID of the rich menu to delete.
  9. 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.
  10. cancel_rich_menu_default
    • Cancel the default rich menu.
    • Inputs:
      • None

Versioning

This project respects semantic versioning

See http://semver.org/

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

Featurestdio (Original)SSE (Added)
Use CaseLocal CLI tools, direct process communicationWeb applications, HTTP-based integrations
ConnectionStandard input/output streamsHTTP + Server-Sent Events
DeploymentProcess-basedServer-based (HTTP)
PortNot requiredRequires port (default: 3000)
ScalabilitySingle processMultiple concurrent connections

🐳 Docker Hub