A side-by-side look at the Line Bot MCP Server and PlaceCall MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Line Bot MCP Server for communication work as a local process; choose PlaceCall for communication over a hosted endpoint. 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.
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 is categorized under Communication and uses a local stdio subprocess. PlaceCall belongs to Communication and uses a remote HTTP/SSE transport. Pick Line Bot MCP Server for communication work and PlaceCall 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. PlaceCall is listed as freemium — a free tier with paid plans. 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 placecall 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. PlaceCall has 44/100 (Fair) with 0 views, 0 installs and 39 GitHub stars.