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.

DimensionBeever AtlasOpen-source LLM knowledge base that turns team chats into a typed knowledge graph and auto-generated wiki.Telegram MCP ServerTelegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.
FMRS47 / 100 · D70 / 100 · B
Reliability5 / 209 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2014 / 20
Documentation14 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Teams that need to distill large volumes of chat into searchable, citable knowledge.
  • RAG applications that want to improve answer consistency and reduce hallucinations.
  • Developers who want MCP integration to let AI coding assistants access team knowledge.
  • 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
  • Lightweight use cases that just need a simple chat log search.
  • Users who cannot self-host Docker-based infrastructure or prefer serverless options.
  • Those needing deep integration with proprietary knowledge management products without self-hosting.
  • 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
  • Requires read access to Slack, Discord, Teams, or Mattermost channels (bot tokens configured via UI).
  • Access to external APIs: Gemini, Jina Embeddings (required); optional Tavily/Olostep web search.
  • Runtime requires Docker, network ports (3000, 8000, 3001, 8080, 7474, 7687, 27017, 6380).
  • For MCP clients, requires BEEVER_MCP_API_KEYS authentication.
  • 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
  • Indexed chat data may contain sensitive information; ensure data security in deployment.
  • API keys (e.g., Gemini, Jina) if exposed can lead to misuse or data breaches.
  • Auto-generated wiki may contain errors or inaccurate info; human review may be needed.
  • Early-stage version (0.3.0) with unstable API; may break on updates.
  • 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, CursorClaude Desktop, Cursor, Claude Code, Codex
Tools1576