Line Bot MCP Server vs Tower
A side-by-side look at the Line Bot MCP Server and Tower MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TowerCommunication · Local subprocess (stdio)Multiplayer for AI coding agents: collision detection before the edit, messaging, delegation.41FairAuth: not declaredVerdict: choose Line Bot MCP Server for communication work as a local process; choose Tower for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Line Bot MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CHANNEL_ACCESS_TOKEN, DESTINATION_USER_ID. - You want tools like
postback, message, uri.
TChoose Tower when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tower | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 84/100 · Excellent | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CHANNEL_ACCESS_TOKENDESTINATION_USER_ID |
Tools & capabilities
Line Bot MCP Server tools 9
postbackFor sending a postback actionmessageFor sending a text messageuriFor opening a URLdatetimepickerFor opening a date/time pickercameraFor opening the cameracameraRollFor opening the camera rolllocationFor sending the current locationrichmenuswitchFor switching to another rich menuclipboardFor copying text to clipboard
Tower tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Line Bot MCP Server
{
"mcpServers": {
"line-line-bot-mcp-server": {
"command": "npx",
"args": [
"@line/line-bot-mcp-server"
],
"env": {
"CHANNEL_ACCESS_TOKEN": "YOUR_CHANNEL_ACCESS_TOKEN_HERE",
"DESTINATION_USER_ID": "YOUR_DESTINATION_USER_ID_HERE"
}
}
}
}
Tower
{
"mcpServers": {
"tower": {
"command": "npx",
"args": [
"-y",
"tower-mcp"
]
}
}
}
Frequently asked questions
Line Bot MCP Server is categorized under Communication and uses a local stdio subprocess. Tower belongs to Communication and uses a local stdio subprocess. Pick Line Bot MCP Server for communication work and Tower for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Line Bot MCP Server is listed as free. Auth: api key required. Tower has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add line-line-bot-mcp-server and tower as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Line Bot MCP Server has a quality signal of 84/100 (Excellent) with 40 views, 0 installs and 789 GitHub stars. Tower has 41/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.
