Telegram MCP vs Cue
A side-by-side look at the Telegram MCP and Cue MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Telegram MCP for communication work as a local process; choose Cue 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 Telegram MCP 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:
TG_APP_ID, TG_API_HASH.
Choose Cue 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:
CUE_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 56/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | TG_APP_IDTG_API_HASH | CUE_API_KEY |
Tools & capabilities
Telegram MCP tools
No tool names declared yet. Check the project README from the listing page.
Cue 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.
Telegram MCP
{
"mcpServers": {
"chaindead-telegram-mcp": {
"command": "npx",
"args": [
"-y",
"@chaindead/telegram-mcp"
],
"env": {
"TG_APP_ID": "YOUR_TG_APP_ID_HERE",
"TG_API_HASH": "YOUR_TG_API_HASH_HERE"
}
}
}
}
Cue
{
"mcpServers": {
"cue-3": {
"command": "uvx",
"args": [
"cue-notify"
],
"env": {
"CUE_API_KEY": "YOUR_CUE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Telegram MCP is categorized under Communication and uses a local stdio subprocess. Cue belongs to Communication and uses a local stdio subprocess. Pick Telegram MCP for communication work and Cue 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.
Telegram MCP is listed as free. Auth: api key required. Cue 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 chaindead-telegram-mcp and cue-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Telegram MCP has a quality signal of 56/100 (Good) with 3 views, 0 installs and 348 GitHub stars. Cue has 37/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.