Stumpy vs Telegram MCP
A side-by-side look at the Stumpy and Telegram MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Stumpy for communication work; choose Telegram 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 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Stumpy | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 37/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | TG_APP_IDTG_API_HASH |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 349 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Stumpy | View Telegram MCP |
Tools & capabilities
Stumpy tools
No tool names declared yet. Check the project README from the listing page.
Telegram 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.
Stumpy
No confirmed install command for Stumpy yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}