Workstream vs Telegram Slack MCP
A side-by-side look at the Workstream and Telegram Slack MCP 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 Telegram Slack MCP 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 Telegram Slack MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TELEGRAM_API_ID, TELEGRAM_API_HASH, TELEGRAM_ALLOW_SEND, SLACK_USER_TOKENS, SLACK_ALLOW_SEND, CHAT_MCP_DATA_DIR.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 36/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TELEGRAM_API_IDTELEGRAM_API_HASH |
Tools & capabilities
Workstream tools
No tool names declared yet. Check the project README from the listing page.
Telegram Slack MCP 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.
Workstream
{
"mcpServers": {
"workstream": {
"url": "http://localhost:8080/demo-insecure-token/mcp"
}
}
}
Telegram Slack MCP
{
"mcpServers": {
"telegram-slack-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-slack-mcp"
],
"env": {
"TELEGRAM_API_ID": "YOUR_TELEGRAM_API_ID_HERE",
"TELEGRAM_API_HASH": "YOUR_TELEGRAM_API_HASH_HERE",
"TELEGRAM_ALLOW_SEND": "YOUR_TELEGRAM_ALLOW_SEND_HERE",
"SLACK_USER_TOKENS": "YOUR_SLACK_USER_TOKENS_HERE",
"SLACK_ALLOW_SEND": "YOUR_SLACK_ALLOW_SEND_HERE",
"CHAT_MCP_DATA_DIR": "YOUR_CHAT_MCP_DATA_DIR_HERE"
}
}
}
}
Frequently asked questions
Workstream is categorized under Communication and uses a remote HTTP/SSE transport. Telegram Slack MCP belongs to Communication and uses a local stdio subprocess. Pick Workstream for communication work and Telegram Slack MCP 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. Telegram Slack MCP 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 workstream and telegram-slack-mcp 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. Telegram Slack MCP has 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.