LINE Bot MCP Server

MCP server that connects AI agents to LINE's Messaging API through a LINE Official Account, enabling push/broadcast messages, rich menu management, user profile retrieval, and message quota monitoring via 11 tools.

Evaluated Mar 06, 2026 (0d ago) v0.4.2
Homepage ↗ Repo ↗ Communication line messaging chatbot mcp rich-menu broadcast push-message japan asia
⚙ Agent Friendliness
73
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
80
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
75
Error Messages
0
Auth Simplicity
78
Rate Limits
68

🔒 Security

TLS Enforcement
100
Auth Strength
80
Scope Granularity
75
Dep. Hygiene
78
Secret Handling
78

LINE messaging platform MCP. Channel access token + channel secret. Webhook signature validation required. User messaging data is private. Popular in Asia-Pacific markets.

⚡ Reliability

Uptime/SLA
82
Version Stability
80
Breaking Changes
78
Error Recovery
78
AF Security Reliability

Best When

You need an AI agent to send messages and manage rich menus on a LINE Official Account, particularly for Japanese or Southeast Asian user bases.

Avoid When

You need to handle incoming messages, target non-LINE platforms, or operate outside LINE's primary markets. Use Twilio or platform-specific SDKs instead.

Use Cases

  • Sending personalized LINE messages to users via AI agent
  • Broadcasting announcements to all LINE Official Account followers
  • Managing rich menus with interactive buttons programmatically
  • Monitoring message quota usage and limits
  • Building AI-powered LINE chatbot workflows

Not For

  • Non-LINE messaging platforms (WhatsApp, Telegram, Slack)
  • Receiving and processing incoming LINE messages (send-only)
  • High-volume transactional messaging requiring guaranteed delivery
  • Markets where LINE is not a primary messaging platform

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Requires a long-lived CHANNEL_ACCESS_TOKEN from the LINE Developers console. Also requires DESTINATION_USER_ID for default message recipients. Token is passed as an environment variable to the MCP server.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Apache 2.0 licensed. The MCP server is free but LINE's Messaging API has its own pricing tiers based on message volume.

Agent Metadata

Pagination
unknown
Idempotent
No
Retry Guidance
Not documented

Known Gotchas

  • Messages are not idempotent - retrying a failed push_text_message may send duplicate messages
  • broadcast_text_message goes to ALL followers - agent must be careful not to trigger unintended broadcasts
  • CHANNEL_ACCESS_TOKEN is long-lived and provides full account access - must be secured
  • Preview/experimental status means API may change without notice
  • Requires LINE Official Account setup through LINE Developers console before MCP server works
  • Rich menu creation supports 1-6 buttons with specific size constraints that agents must understand
  • Node.js v20+ required for npx installation

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for LINE Bot MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered