line-oa-mcp-ultimate
Related Servers
Alternatives to line-oa-mcp-ultimate
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to control a LINE Official Account via the Messaging API, including sending text and flex messages, broadcasting, retrieving user profiles and follower IDs, and managing rich menus.12883 npmApache 2.0
- AlicenseBqualityDmaintenanceEnables AI agents to send messages, manage rich menus, and interact with users through LINE Official Accounts via the LINE Messaging API. Supports both individual messaging and broadcasting to all followers with text and customizable flex messages.18883 npmApache 2.0
- AlicenseAqualityDmaintenanceAI-powered MCP server for managing LINE Official Accounts. Send broadcasts, push messages, check analytics, manage rich menus — all through natural language via Claude, ChatGPT, or Cursor. 10 tools included: * Account info, friend count, message quota * Broadcast, push message, multicast * Delivery stats, user profiles, follower list * Rich menu management Supports 95M+ LINE users across Jap10MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read, reply, send images, and search LINE messages by logging in as a secondary device, without official API or browser.4120 npm3MIT
- AlicenseAqualityDmaintenanceIntegrates the LINE Messaging API with AI agents via the Model Context Protocol, supporting both stdio and SSE transport protocols. It allows agents to send messages, manage rich menus, and retrieve user profile information for LINE Official Accounts.10883 npmApache 2.0

LINE Bot MCP Serverofficial
AlicenseAqualityAmaintenanceMCP server that integrates the LINE Messaging API to enable AI agents to send messages and manage LINE Official Accounts.12883 npm783Apache 2.0
TDQS
Scored across 37 tools
Most tools are clearly organized by resource and action, and the descriptions are detailed enough to guide selection. A few pairs overlap in purpose—line_estimate_send_cost vs. line_send_message's dry_run, and line_get_coupon_stats vs. line_manage_coupon get—and the three rich-menu creation/update tools require close reading to choose correctly.
The set follows a strong line_<verb>_<noun> convention with consistent clusters like list_*, get_*, delete_*, build_*, design_*, and manage_*. Minor deviations such as line_image_host_status (missing the get_ prefix) and the build vs. design distinction for rich menus keep it from being perfectly uniform.
37 tools is well into the 'too many' range and would be heavy for an agent to navigate in a single context. While the breadth is understandable for an 'ultimate' LINE OA server, several helpers (image_host_status, find_sticker, design_*, estimate_send_cost) could plausibly be consolidated or surfaced as sub-modes.
The tool surface covers the major LINE OA lifecycles—messaging, rich menus, audiences, coupons, LIFF, webhooks, analytics, and multi-OA operation—with very few dead ends. Minor gaps like missing audio/file message types, no coupon update path, and reliance on list endpoints for some single-resource lookups keep it from a perfect score.