Telegram MCP vs Stumpy

A side-by-side look at the Telegram MCP and Stumpy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Telegram MCP logoTelegram MCPCommunication · Local subprocess (stdio)Telegram API integration for accessing user data, managing dialogs (chats, channels, groups), retrieving messages, and handling read status57GoodAuth: api key required
S
StumpyCommunication
Persistent AI agents that run 24/7 in your Slack, Telegram, SMS, or email.37FairAuth: not declared

Verdict: choose Telegram MCP for communication work as a local process; choose Stumpy for communication. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Telegram MCP logoChoose 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.
Explore Telegram MCP

S
Choose Stumpy when

  • You need dedicated capabilities in the Communication domain.
Explore Stumpy

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTelegram MCP logoTelegram MCP
S
Stumpy
CategoryCommunicationCommunication
Quality signal57/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsTG_APP_IDTG_API_HASHNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars349—
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Telegram MCP tools

No tool names declared yet. Check the project README from the listing page.

Stumpy 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 (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Stumpy

No confirmed install command for Stumpy yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Telegram MCP is categorized under Communication and uses a local stdio subprocess. Stumpy belongs to Communication and uses an install path we have not confirmed yet. Pick Telegram MCP for communication work and Stumpy 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. Stumpy has no confirmed install command yet — follow its own setup instructions.

Telegram MCP is listed as free. Auth: api key required. Stumpy 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 chaindead-telegram-mcp and stumpy 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 57/100 (Good) with 4 views, 0 installs and 349 GitHub stars. Stumpy has 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.