M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAtomic-Mail MCPProgrammable email inbox for AI agentsTelegram MCP ServerTelegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.
FMRS56 / 100 · C70 / 100 · B
Reliability8 / 209 / 20
Security and permissions13 / 2016 / 20
Maintenance12 / 2014 / 20
Documentation13 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • Workflows where AI agents need their own email inbox for autonomous operation.
  • Automated email handling without human intervention, especially with Claude, Codex, Cursor, etc.
  • Developers who prefer standard protocols (JMAP) to avoid vendor lock-in.
  • Developers who want to integrate Telegram into MCP clients like Claude
  • Automation scenarios that need to manage multiple Telegram accounts
  • Building custom Telegram bots or workflows
  • Scenarios that require secure file operation path restrictions
Not for
  • Scenarios requiring human review of every email, since agents can autonomously send and receive.
  • Mission-critical email for enterprises that cannot rely on third-party deliverability guarantees.
  • Organizations that need full control over their email infrastructure or offline operation.
  • Use cases requiring official Bot API features (this server uses a user client)
  • Non-technical users who want a fully managed solution
  • Multiple processes using the same session without lock management
Required permissions
  • Read and write local credential files (default at `~/.atomicmail/credentials.json`).
  • Network access: communicate with Atomic Mail's auth service and JMAP API.
  • Environment variables: may require `ATOMIC_MAIL_API_KEY` to skip registration.
  • Requires Telegram API ID and API Hash
  • Requires the user's Telegram session string (equivalent to account access)
  • Can send messages, media, contacts, and settings to any allowed chat
  • Can create or modify groups, channels, and chat settings
  • Can access and operate on the user's media files and contacts
Risks and side effects
  • API keys stored locally could be misused if leaked.
  • Email content is untrusted; agents might be tricked into executing malicious instructions (e.g., phishing).
  • Service is in alpha with storage quotas and rate limits; may be unstable.
  • Dependency on external service; if Atomic Mail is down, agent email functionality is affected.
  • Session string leakage could lead to account compromise
  • Sending messages may raise privacy or security concerns
  • Prompt injection: Telegram content may be maliciously crafted, so precautions are needed
  • Risk of using unofficial PyPI package name; avoid pip install telegram-mcp
  • Concurrent clients using the same session may cause AuthKeyDuplicatedError
Supported clientsClaude Desktop, Claude Code, Codex, GitHub Copilot, Cursor, Kilo CodeClaude Desktop, Cursor, Claude Code, Codex
Tools376