MCP server for LINE Messaging API — send messages, manage groups, rich menus, webhooks, and more. ## Features - Push, reply, multicast, and broadcast messages - User profiles, follower lists, and bot info - Group chat management (summary, members, profiles) - Rich menu CRUD, default setting, and per-user linking - Message quota monitoring and follower insights - Webhook URL configuration and connectivity testing ## 25 Tools **Messages**: push, reply, multicast, broadcast, validate **User & Bot**: get profile, get follower IDs, get bot info, display loading **Group Chat**: get summary, get members count, get member IDs, get member profile **Rich Menu**: create, list, get, delete, set default, link to user **Quota & Insights**: get quota, get consumption, get followers count **Webhook**: set URL, get info, test endpoint ## Configuration - LINE_CHANNEL_ACCESS_TOKEN — Channel Access Token from LINE Developers Console (Messaging API channel settings)
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2786 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 25 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 38% of peers
- This listing 434 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/node2flow/line-bot/mcpcurl -X POST https://server.smithery.ai/node2flow/line-bot/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'