← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionDeepChatLocal-first open-source AI agent desktop client unifying LLM providers, MCP, Skills, and ACP agentsTelegram MCP ServerTelegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.
FMRS52 / 100 · D70 / 100 · B
Reliability7 / 209 / 20
Security and permissions6 / 2016 / 20
Maintenance15 / 2014 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Users who want a single desktop app that unifies many cloud LLM providers (OpenAI, Anthropic, Gemini, DeepSeek, etc.) and local Ollama models
  • Users who need to connect to multiple external MCP tool services with local-first storage and inspectable session history (Tape/Trace)
  • Users who want to reuse Agent Skills built for Claude Code, Cursor, Windsurf, and similar tools
  • Developers who want coding-focused ACP agents integrated into the same chat-style model selector
  • 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
  • Users looking for an MCP server to add into Claude Desktop or another AI client's config (DeepChat is an MCP client/host, not a server to be added elsewhere)
  • Users who want a lightweight CLI-only tool rather than a full Electron desktop application
  • Users needing a native mobile app (currently Windows/macOS/Linux desktop only; mobile access is indirect, via remote control)
  • 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
  • Local file system read/write access for session Tape storage, Skills files (imported from folders/ZIP/URL), and app configuration
  • Ability to spawn local subprocesses, used to run stdio-based MCP services and the bundled Node.js runtime
  • Network access to call cloud LLM APIs, search services (e.g. Brave Search), and SSE/StreamableHTTP MCP services
  • Remote-control bot credentials (Telegram/Feishu/QQBot/Discord/WeChat iLink tokens) used to bind and remotely operate desktop sessions
  • Local Ollama management access to download, deploy, and run local models
  • 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
  • Third-party MCP services connected via stdio run as local processes under the user's permissions — only install MCP services from trusted sources
  • Imported Skills may include optional scripts that execute with the app's permissions once enabled — vet the source before enabling
  • If a remote-control bot token is leaked, an attacker could remotely control the local session, switch models, or read pending interactions via the messaging app
  • Some search functionality works by simulating user browsing of search engines, which may raise terms-of-service considerations for target sites
  • The README describes encryption/obfuscation interfaces as "reserved" capabilities — verify what is actually enabled in a given release before relying on it
  • 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, Cursor, Claude Code, Codex
Tools076