Telegram MCP Server (chaindead)

Community MCP server for Telegram enabling AI agents to send messages, create polls, manage bot interactions, and access Telegram Bot API functionality for messaging automation.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Communication telegram messaging bots mcp-server community chat notifications

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

100

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

No scope granularity is the main security gap. Single token = full bot access. HTTPS enforced. Community MCP — verify code and dependencies.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

An agent needs to send notifications, alerts, or reports to Telegram users or groups — especially in technical/developer communities.

Avoid When

You need enterprise messaging with audit logs, GDPR compliance controls, or access to user (non-bot) message history.

Use Cases

• Sending alerts and notifications to Telegram chats from agents
• Delivering agent reports and summaries via Telegram
• Managing Telegram group messages in agent workflows
• Creating Telegram polls and surveys programmatically
• Reading incoming messages for trigger-based agent workflows

Not For

• Enterprise communication with compliance requirements
• High-throughput messaging at scale (Telegram Bot API has limits)
• Accessing private account messages (Bot API only, not user API)

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Yes

Webhooks

Yes

Authentication

Methods: bot_token

OAuth: No Scopes: No

Single bot token grants full access to bot functionality. No scope granularity — token is all-or-nothing. Obtain from BotFather on Telegram.

Pricing

Model: free

Free tier: Yes

Requires CC: No

Completely free for bot API usage. No rate-based pricing.

Agent Metadata

Pagination

cursor

Idempotent

Retry Guidance

Not documented

Known Gotchas

⚠ Bot can only send to chats it has been added to — cannot initiate conversations with new users
⚠ 30 messages/second global limit shared across all your bots with same token
⚠ Group messages limited to 20/minute — notify user if flooding needs to be prevented
⚠ No scope granularity — token grants full bot access; no way to restrict to send-only
⚠ Community MCP server — may not cover all Telegram Bot API methods
⚠ No idempotency — network retry can send duplicate messages

Alternatives

discord-mcp slack-mcp mcp-notify

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Telegram MCP Server (chaindead).

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.