LINE Bot MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track LINE API versions and messaging scopes as the platform changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Operating a LINE Official Account from an MCP client

What we know

Official LINE MCP server for messaging and group/user operations through a LINE Official Account and Messaging API.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)Lock file maintenance ( 630)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Messaging API scopes of the configured Official Account. Writes: Send external messages; Other account/group actions exposed by tools.
LINE channel access token.
Sensitive access: User IDs, Group metadata, Message content

The server acts as a real LINE Official Account; protect the token and require confirmation for outbound communications.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

783 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Which LINE bot actions and credentials are supported by the current package?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The server acts as a real LINE Official Account; protect the token and require confirmation for outbound communications.
Messaging API scopes of the configured Official Account.
LINE channel access token.
LINE user/group/message metadata flows through the Messaging API and MCP client.
Reviewed write actions: Send external messages; Other account/group actions exposed by tools
Sensitive access: User IDs, Group metadata, Message content
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Requires a LINE Official Account and Messaging API access.
External messaging actions affect real users.

Original activity observations

2026-10-05T16:43:03Z: Lock file maintenance ( 630)

Technical identity

github.com/line/line-bot-mcp-server

Exact implementation source: https://github.com/line/line-bot-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: line/line-bot-mcp-server
Package identity: npm:@line/line-bot-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
line/line-bot-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

claude-desktop

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

May send real messages; treat outbound tools as write-capable.
Purpose detail: server_launch
Publisher README first-party npx JSON; DESTINATION_USER_ID optional if each tool call supplies userId. Requires LINE Official Account Messaging API. DESTINATION_USER_ID intentionally omitted: optional when passing userId per call; configure a real value only when needed. Publisher-supported parameters assembled into a machine-readable JSON example; placeholders are user-specific and no real credentials are included. Treat as reviewed composed example rather than a verbatim executable test. Replace the supplied credential/path placeholders privately; use the named host's configuration schema.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.

Install / connect
Publisher instructions
LINE official Bot MCP connects an AI client to a LINE Official Account using a Channel Access Token.
mcp stdio launcher or diagnostic · Publisher instructions
npx @line/line-bot-mcp-server
Configure / authenticate
MCP100 setup guide
Set LINE CHANNEL_ACCESS_TOKEN from LINE Developers and launch via publisher npx configuration. Prefer restricted account; messaging tools can send outbound messages.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "line-bot": { "args": [ "@line/line-bot-mcp-server" ], "command": "npx", "env": { "CHANNEL_ACCESS_TOKEN": "YOUR_LINE_CHANNEL_ACCESS_TOKEN", "NPM_CONFIG_IGNORE_SCRIPTS": "true" } } } }
Check connection
Suggested check
Check tool visibility or read-only profile availability; do not send test messages.
Remove / uninstall / revoke
MCP100 setup guide
For Claude Code registration named line-bot; Docker host must separately stop container if deployed persistently.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove line-bot

Official Documentation & Sources

What it does

Official LINE MCP server for messaging and group/user operations through a LINE Official Account and Messaging API.

Capability: Communication
Resource type: MCP Server
Best fit: Operating a LINE Official Account from an MCP client

Representative uses

Send messages
Retrieve user/group information
Operate group-chat related tools
Use a default destination user

Limitations

Requires a LINE Official Account and Messaging API access.
External messaging actions affect real users.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: LINE channel access token.
Permissions: Messaging API scopes of the configured Official Account.
Data handling: LINE user/group/message metadata flows through the Messaging API and MCP client.
Cost: unknown
Risk and cautions: The server acts as a real LINE Official Account; protect the token and require confirmation for outbound communications.

Access scope and cautions

Write actions: Send external messages Other account/group actions exposed by tools
Sensitive access: User IDs Group metadata Message content
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Send messages; Retrieve user/group information; Operate group-chat related tools; Use a default destination user.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx @line/line-bot-mcp-server. Recorded transport: stdio. Recorded environment-variable notes: CHANNEL_ACCESS_TOKEN; DESTINATION_USER_ID. No configuration values are supplied here. Prerequisites: Node.js 22+; LINE Official Account. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: LINE channel access token.

Can it modify data or perform write operations?

Documented write actions include: Send external messages; Other account/group actions exposed by tools. Recorded permission boundary: Messaging API scopes of the configured Official Account.

What data-handling boundary should I consider?

LINE user/group/message metadata flows through the Messaging API and MCP client. Recorded sensitive-access context: User IDs; Group metadata; Message content.

What limitations and risks should I check before use?

The server acts as a real LINE Official Account; protect the token and require confirmation for outbound communications. Requires a LINE Official Account and Messaging API access. External messaging actions affect real users. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

LINE is listed as First-party MCP in MCP100’s current evidence.