Workstream vs Line Bot MCP Server
A side-by-side look at the Workstream and Line Bot MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Workstream for communication work over a hosted endpoint; choose Line Bot MCP Server 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 Workstream when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 36/100 · Fair | 84/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed |
Tools & capabilities
Workstream tools
No tool names declared yet. Check the project README from the listing page.
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
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.
Workstream
{
"mcpServers": {
"workstream": {
"url": "http://localhost:8080/demo-insecure-token/mcp"
}
}
}
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"
}
}
}
}
Frequently asked questions
Workstream is categorized under Communication and uses a remote HTTP/SSE transport. Line Bot MCP Server belongs to Communication and uses a local stdio subprocess. Pick Workstream for communication work and Line Bot MCP Server 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.
Workstream has no declared pricing — check the project's own site. Line Bot MCP Server is listed as free. Auth: api key required. 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 workstream and line-line-bot-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Workstream has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Line Bot MCP Server has 84/100 (Excellent) with 40 views, 0 installs and 789 GitHub stars.